Recent searches
Search options
In addition to turning off their API, #Twitter has also inexplicably turned off access for users to sign in to Flipboard and other platforms with Twitter SSO.
This is an unacceptable breach of trust between Twitter and their developers and users. Twitter must be held to account here.
As you know, this goes on, and on, and on with platforms that assume they control a monopoly.
The only way to avert these disasters is via proper exploitation of loose-coupling that's been delivered on a platter by the #Web.
Right now, I am a little concerned about #Mastodon #API overshadowing the #ActivityPub protocol re loose-coupling of clients and severs across the #Fediverse.
Most think this is okay, but we've seen this movie before++
Yep.
Open protocols are the ultimate protection against inevitable compromise.
Only implementing a part of the #ActivityPub protocol weakens the #Fediverse as an open #SocialMedia collective comprising loosely-coupled clients and servers.
/cc @Mastodon
@kidehen I agree with you. [edited]
It's not sustainable to build a new social graph around every type of experience.
We should have apps that create activities that go into one social graph, and that draw on that one social graph.
@mike you should keep building on the API. I think it's the right move.
Eventually we'll have a more standard API, the ActivityPub client API, and you can use that standard one or the Mastodon one or both.
@evan @kidehen @mike Credit where credit is due as well - making ActivityStreams an RDF vocabulary was a really great idea that allows the social graph to represent objects/concepts/etc. which nobody contemplated when it was made.
The trouble is, as with all great RDF things, getting people to parse it as RDF and not its serialization format (JSON-LD here) so they aren’t broken by novel but conformant uses of ActivityPub/ActivityStreams.
@ZiggyTheHamster@ruby.social@evan @kidehen @mike (also I realize you don’t need your own thing explained, but I didn’t want to leave context out for anyone browsing the thread who might not know what “creator of GNU Social” means, and “RDF was an excellent choice” on its own is confusing to anyone who isn’t familiar with the underpinnings :))
I don't know whose idea it was to make AS2 based on JSON-LD. Definitely not mine; I assume James Snell's.
If I remember correctly, it was already assumed by the time we started the WG. We may have had some conversation about it during the group meetings.
I think @jasnell had done a draft of AS2 previously as an RFC for IETF maybe? It may have been JSON-LD back then.
@evan @ZiggyTheHamster yeah that was me. The original ietf version was not JSON-LD, but it was switched quickly after a few discussions around it. It adds complexity, yes, but also a great deal of processing flexibility. It was critical that we also maintained that "It's just json" feel to it tho, which is why we constrained the serialization.