3 ms·

Fair and important questions. The closest immediate answer I have is https://indieweb.org/SWAT0 https://indieweb.org/SWAT0 but the page is quite dense with indi

• amelius 9y ago
  That's a start, but I suspect we're better off thinking about all possible features, because this allows us to define a protocol that generalizes better. 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.
  • pmlnr 9y ago
    There's a list of features documented for : https://indieweb.org/Facebook#Features https://indieweb.org/Facebook#Features https://indieweb.org/Twitter#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.
  • jeena 9y ago
    Your example works with those protocolls already too and I implemented it on my website, here is a example: https://jeena.net/events/11 https://jeena.net/events/11 And you can get all of that machine readable too: http://pin13.net/mf2/?url=https%3A%2F%2Fjeena.net%2Fevents%2F11 http://pin13.net/mf2/?url=https%3A%2F%2Fjeena.net%2Fevents%2...