These days, everyone hates big tech, and that’s often for very good reasons. You shouldn’t trust giant centralized companies that have collected a ridiculous amount of data on you. There are few re…
I heard that interview and have been casually digging into ActivityPub.
BSKY does account for a few more situations that ActivityPub currently doesn’t.
One is pluggable algorithms. This way you’re not tied to one kind of ordering in your feed.
Another is layered moderation so you can adjust automated vs human moderation policies.
And the last one is how to transport all your stuff to a different server under several different lockout scenarios. I’m still not clear which one’s better if your server just disappears or gets locked out.
In the long run, though, there has to be just one service. You can’t have Mastodon, Bsky, and Threads each with different functionality and incompatible islands.
But is the first two ActivityPub’s fault or Lemmy/*bin’s? If it’s the former, then that’d imply a failure in the essence of the protocol. If it’s the latter, then it’s something that may be changed.
The account portability issue is being addressed in ActivityPub. Just saw some proposed extensions.
The layered/plugin approach, though, seems like it’s more of an implementation feature. The description of how it’s implemented in BSKY made it sound like you’re not locked into a single chronological way to show a home feed. That seemed like it had a lot of potential.
I heard that interview and have been casually digging into ActivityPub.
BSKY does account for a few more situations that ActivityPub currently doesn’t.
One is pluggable algorithms. This way you’re not tied to one kind of ordering in your feed.
Another is layered moderation so you can adjust automated vs human moderation policies.
And the last one is how to transport all your stuff to a different server under several different lockout scenarios. I’m still not clear which one’s better if your server just disappears or gets locked out.
In the long run, though, there has to be just one service. You can’t have Mastodon, Bsky, and Threads each with different functionality and incompatible islands.
But is the first two ActivityPub’s fault or Lemmy/*bin’s? If it’s the former, then that’d imply a failure in the essence of the protocol. If it’s the latter, then it’s something that may be changed.
The account portability issue is being addressed in ActivityPub. Just saw some proposed extensions.
The layered/plugin approach, though, seems like it’s more of an implementation feature. The description of how it’s implemented in BSKY made it sound like you’re not locked into a single chronological way to show a home feed. That seemed like it had a lot of potential.