Show Navigation
Conversation
Notices
-
we need to start looking at the whole picture, holistically and start building more tools that are better suited to specific use cases.
in Pleroma or Mastodon we trust is the path to failure.
the other platform plays need their space in the puzzle, but indieweb also needs it's space in the puzzle.
and of course internet-wide roaming identity.
we can prevail but we need to stop putting our marbles in the AP box. AP has it's place, but AP isn't private. sharedInbox screwed us on that one. OCAP fixes the problem, but platforms are inherently less than optimal when it comes to privacy.
instead of plugging holes in AP we need to encourage adoption of technologies that are better suited when there are better fits. as long as it all securely works together in the end, it doesn't matter.
-
like the big deal about hubzilla actually isn't Zot. Zot actually doesn't do much. it's pretty comparable to AP, especially zot6.
the big deal is openwebauth. hubzilla doesn't have data retention problems because it doesn't retain problems. you can't leak what you don't retain.
AP on the other hand is designed to push data around to as many places as possible. Zot on the other hand just advertises *availability* of data. Hubzilla then goes and fetches this data on demand. But ultimately you click on content and it takes you away from your hubzilla to somebody else's, while keeping you logged in.
that's what we need to be building across platforms and across the entire open social web.
less is actually more.
-
@kaniini please fucking make openwebauth work with fediverse platforms. It's a great concept and doesn't rely on federating a million things everywhere.
The big aha moment for me was several years ago, when I switched from Diaspora. Diaspora as an app relies on federating everything, from status updates to photos to likes to profile data. This is all fine and dandy, except that the way it is implemented makes it very difficult for Diaspora to adequately approximate the feature set of Facebook.
Photo albums, for example, cannot exist with proper hierarchy. What are you going to do, federate every album and every photo in it? Embed reference data to point to a top level "photo album" object? Then send references to those albums to all of your contacts?
One thing that Hubzilla does super well is that it only sends just enough data to build a stream and accept interactions. All the fancier higher-order feature components and their data live on the remote instance you're looking at, instead of pulling those resources into your own instance.