Really feel this. Along with group chat (irc), GitHub is the best form of social networking I’ve ever experienced. It’s how my co-founder and I first connected some 6-7 years ago. It’s the real LinkedIn for devs, where the posting activity is the work itself, rather than posting about the work. A truly magical place, while it lasted.
Bluetooth works most reliably across all devices (within its limited range), but all these p2p apps are indeed moving towards multi-transport support to diversify and widen the connectivity grid: https://hackmd.io/@grjte/bitchat-wifi-aware
I use Voyager, a client for Lemmy, on a daily basis and it’s my favorite mobile (iPad) app. Voyager is the spiritual successor to the Apollo client for Reddit.
The app uses Ionic’s Capacitor, which to my rudimentary understanding is the webview-based upgrade of Cordova. I’ve had far fewer issues with this app than the likes of Bluesky (react native) and Discord (I think also react native but not sure).
The webview approach seems to be the only way for a one-person team to feasible provide a cross-platform app with an app-store presence. Another promising alternative to Capacitor is Tauri Mobile which does essentially the same thing, but mobile doesn’t seem to be a high priority for them.
> The moment you create/share data with a site, what's to prevent them from reselling it?
If I can clearly assert origin and personal ownership of my data, I can forbid further reselling of it.
EU legislation shows that we can actually have the right to demand that a company forgets about us. Asserting such rights become easier the more accurately we define what data is ours.
This is demonstrably not fantasy as the example case is a fully productionized network (Bluesky and the rest of AT-net) that’s having real-world impact to the point where it’s under threat from several authoritarian states.
It doesn’t really rely absolutely on domain names; at the very root there’s just a DID. DNS happens to be the best we’ve got right now as a human-readable username and address in-one goes.
We’re evaluating Keyhive for use in our distributed chat application and my colleague wrote an in-depth explainer on Keyhive’s underlying Key Encapsulation Mechanism BeeKEM, which is a decentralized offshoot of TreeKEM used in MLS: http://meri.garden/a-deep-dive-explainer-on-beekem-protocol/
That one line on its own should be enough put the illegitimacy of this proposal on clear display. Privacy for me (the surveillance state) but not for thee (the populace).