Serious question, no offense or provocation intended: With this stuff being baked into Hubzilla and, apparently, also design-wise into Bluesky / AT, can anyone out here involved with the #ActivityPub outline why nomadic / easily portable identity isn't built-in here by design? Looking at the (to-be-expected) dynamics of instances going up and down, blocking each other or moving to newer, different pieces of software, this seems an absolutely obvious requirement, so I wonder why this has been left out of the standard / spec?
Follow

@z428 I'm very critical of ActivityPub for not having such features, and I have two thoughts about it.

Firstly, as far as I can tell there was a conscious decision to focus on instances. Many people very strongly embrace the patterns that arise out of the instance focus, the moderation, community, and inter-instance blocking stuff.

This human organization side of things is so obvious that I can't believe it wouldn't have been considered during standardization.

Secondly, when you look at the parts of the ActivityPub standard, things like use of http and certificates, it shows developers with a certain background grabbing certain pieces off the shelf that may not have been the most innovative parts to bring together.

Nomadic identity would have required a bit more thought than what ended up in ActivityPub. It raised some harder questions.

AP itself is inefficient and lacks anything groundbreaking. It's composed of off-the-shelf pieces that were cobbled together.

Frankly, AP seems to have been put together lazily, and the lack of portable identity reflects that.

Sign in to participate in the conversation
CleverLibre Social

CleverLibre Social is an inclusive social instance for open discussion, learning, and community.
All cultures welcome.
Hate speech and harassment strictly forbidden.