Gregory's Server@atomicpoet @maegul that's only if both sides agree on at least a minimum of sensible information to exchange so that there is something to show for it. Can Mastodon do anything with a Place object? An Event? A Tombstone? Heck, Mastodon doesn't even go out of its way to support Article objects sensibly. We can argue that this isn't AP's fault, like it's not HTTP's fault that not all UAs support all image formats, but it is a limitation.
|
14 comments
 @atomicpoet @maegul again, this might not be considered an AP limitation, but in this sense, Mastodon's dominance is actually destroying that same flexibility of the protocol.  @oblomov @atomicpoet yep, it’s an interesting question to consider … at some point, will Mastodon need to die or diminish for the fediverse to thrive? @atomicpoet @maegul by the time Mastodon dominance will have waned, the damage to the Fediverse diversity will already have been done.  @atomicpoet @maegul IE “validated” the web, but also set back its development for over a decade, wasting inordinate amounts of developer time trying to work around its limitations and preventing some useful ideas from reaching any kind of popularity. @atomicpoet @maegul I should be able to read an Article from my Fediverse client regardless of what my server platform thinks about it. I should likewise be able to receive (and see) any kind of object sent by people I subscribe to regardless of my server platform capability to handle it. AP servers shouldn't be the ones responsible for deciding which object types and attributes the user has access to. That should be the client's responsibility.  @atomicpoet@mastodon.social @oblomov@sociale.network @maegul@hachyderm.io mastodon right now is used both a server-only for separate (mostly mobile) clients, and a server+client web app. Historically it has mostly been the second. The growth right now is in the first. It will have to decide which one it wants to be growing up, because I don’t think it can excel at both. @atomicpoet @maegul @oblomov @atomicpoet @maegul Naturally, said the architect. And then we have software in the real world :-) Mastodon was written as a plain normal rails web app, and that, I believe, was the right and perhaps only way that could have gotten us to the good place where we all find ourselves today. The question is where it wants to go. (I’m going to take the liberty of cc’ing @Gargron just in case…) @J12t @oblomov @maegul @Gargron People have been trying to make decentralized social media happen for nearly 20 years now. We can all talk about how Mastodon could be better till we're blue in the face. The fact is that Mastodon has created a halo effect on other server software too. In other words, Mastodon's growth is Friendica's growth too. For real. Look at this chart. In September, Friendica was little more than 250 nodes. Now it's nearing 400. @J12t @oblomov @maegul @Gargron For the sake of comparison, let's look at diaspora's growth. It went from 115 nodes in September to 117 nodes in September. Now imagine how much more growth it could have if it simply integrated ActivityPub. So again, while diaspora's devs bemoaned lack of uniformity and usability, few people are using it -- and it can't speak to the rest of the Fediverse. There's a reason why we're here and not there. |
@atomicpoet @maegul and ultimately, this is a limitation that makes the platform more important than the protocol, because the platform is responsible for actually accepting the objects: you can't write a separate client that knows what to do with a Tombstone and have it display those objects that were sent to your Mastodon account. So platforms that want those Tombstones to be shown on Mastodon will end up sending Notes instead.