A lot of people have talked about the possibility of forking Mastodon to get the many improvements their communities need. Making such an effort successful is another discussion entirely.
Most of the backlash pertains to the board members appointed to the new nonprofit. One of the members is a lawyer that has defended crypto and AI companies, another is ex-Twitter angel investor Biz Stone.
Mastodon’s community usually has some kind of vague beef about one thing or another when it comes to Eugen and the decisions he makes for the project, whether it’s a new feature or a design change or that he didn’t do something that other projects wanted to do.
@deadsuperhero There are several forks of Mastodon that have been around for years and work well (not only #Hometown) like #Ecko, #Glitchsoc, etc. for years.
They have many more functions such as editable character limit,
editable poll options, local posts, changeable favicon, markdown formatting - and if that's not enough, there is plenty of other software in the Fediverse for micro- and macroblogging
Yeah, if you read the article, Hometown and Glitch actually get mentioned. The criticism is not about making a fork to do your own thing… but, instead, about trying to compete with Mastodon directly.
Doing that kind of fork (which is what people are calling for) requires a tremendous amount of coordination, effort, and commitment that cannot be done casually.
Akkoma and Pleroma are two popular "Mastodon style" Fediverse apps, I think born out of exactly this type of complaint about Mastodon, which you could get involved with if you wanted to be involved with better software without it being a one-man show.
I think it's made needlessly difficult by how sloppy a protocol ActivityPub is, such that different Fediverse apps can't really interoperate with each other except at a pretty rudimentary level, so you kind of have to pick one of the leading ones and imitate it, in order to be a citizen in its community and not have to build your own little community from scratch. But that's a problem without a real easy solution, I think.
This is a situation that I think will get better in time. There’s some really promising efforts involving Fediverse Enhancement Proposals, where multiple projects collaborate on shared ways of doing things. Some of these behaviors are getting studied and standardized by the larger SocialCG entity, as well.
There’s also a lot of promising development behind a Fediverse Testing Suite. If we can develop a platform-agnostic testing system for people to build against, it will potentially become the new development standard, rather than optimizing for Mastodon and nothing else.
If we can develop a platform-agnostic testing system for people to build against, it will potentially become the new development standard, rather than optimizing for Mastodon and nothing else
Well, unless interoperating exclusively/mostly with mastodon is still substantially incentivised because of its size. Hopefully mastodon comply with the testing suite’s standard, but I can see that being a slow process, and I can also see grey areas persisting.
I don’t really see the point in forking a project like Mastodon unless you are already deeply involved with its development. It doesn’t do enough that you couldn’t rewrite it better (as in in a way you understand better and with lessons from the original taken into account) in the time it would take you to fully understand all the details of the existing code base.
It actually does have that nowadays, it’s just that the feature requires Elasticsearch to work, which is one extra piece of infra for admins to worry about.
It absolutely is. Yet, as Sean said, it’s also yet another bit of software to run and maintain, and ES is known to be a bit of an effort to keep going well.
Admins having only finite amounts of time and/or resources, might make the very understandable decision to leave it out.
Add comment