Gregory's Server@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.
|
4 comments
 @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
@J12t
This wouldn't even be a problem per se, if not for the fact that the two sides are very tightly coupled. Ideally, the two sides should be completely decoupled, and the server should —for the most part— only act as passthrough, with the objects getting passed to the client (and to other servers when posted) essentially unchanged. Also, ideally all information should be available through AP, rather than platform-specific APIs.