It is true that user interfaces are just as important, but half-baked solutions might do more harm, than good, resulting in disappointment in those who'd be willing to try them out.
As much as most people on HN would like to have these protocols specified ‘correctly’, this feels like a situation where the perfect is the enemy of the good.
What do we want the system to do?
And how can we control our privacy?
Let's answer these questions first.
EDIT: https://www.w3.org/2005/Incubator/federatedsocialweb/wiki/SW... might be a better source.
Defining a minimum set of features for what a social network (media? web? system?) is is certainly a required step, and any suggestions are welcome.
In your example, users can be tagged in a photo. That's nice. But let's say that in the future we want to share who's attending what events. Perhaps we can use the same kind of constructs in the protocol for both uses.
Of course, an implementation does not need to support all features from the start.
https://indieweb.org/Facebook#Features
https://indieweb.org/Twitter#Features
However, I don't think there's any kind of standard-ish list for what's a minimum feature set for a social network. Please feel free to add one to the indieweb wiki, as any help is welcome.
And you can get all of that machine readable too: http://pin13.net/mf2/?url=https%3A%2F%2Fjeena.net%2Fevents%2...
Ideally I'd be happy with something like that, where a single geek can provide a secure and federated social hub to his circle of friends/family.
Friendica supports a ton of protocols, see the "Interoperability" section on the front page.
Regarding ActivityPub, it is good to keep in mind the reality: https://github.com/friendica/friendica/issues/4688
Quoting MrPetovan:
> ActivityPub is a "loose standard", meaning that it doesn't define precisely each interaction. "Supporting ActivityPub" doesn't make any sense, because, per the standard, implementers are forced to make local decisions about how to convey specific features via ActivityPub because of an intended lack of description.
> In this context, you can claim "supporting ActivityPub" and not being able to interact with any other service also claiming "supporting ActivityPub" just because you made different implementation decisions.
> Another angle: Mastodon implemented ActivityPub for internal communication between Mastodon instances. So they designed their usage of ActivityPub according to their specific usage and features since the standard actually encourages you to do so by leaving parts intentionally vague. However, if any other project wants to communicate with Mastodon instances, they will have to know which specific decisions were made for the intentionally vague parts of the standard because you can't just guess.
> It is different from OStatus where interactions were much more precisely defined, so you actually could rely on the standard definition to implement a single connector that would mostly work with most OStatus services because the vague parts were reduced to a minimum.
Decentralized systems can only take off if they are built around standardized protocols - this is why email works. The choice of smtp servers to run, email clients to choose from, that's what's making it resilient.
Ideas like ActivityPub, webmentions, microsub, micropub, while not strictly protocols - all on top of HTTP - could allow us to build real decentralisation, with the weapon of choice on platform, language, client - this is what's truly needed.
Most of the platforms like Diaspora, Friendica, Mastodon, can, could, or already have adopted some of these, thus making a good step towards true federation, when anything can talk to anything.
EDIT ... but the emphasis right now should be on the glue, the protocols connecting them, not just only the software implementing it.