Misago VS Misskey

I would like to use this opportunity to also mention about a forum software I am building, Misago: https://misago-project.org/

Around year ago I've started to aggressively pursue improvements to it's UX and featureset which to my surprise resulted in project getting new (small) wave of attention and a lot of great feedback on what else is missing and what needs changed that I am working on at.

I've grown on old school forums, phpBB2, Invision Power Board 2.3, vBulletin 3 and I am trying to hit a sweet spot between old and new, taking inspiration from both other modern solutions like Discourse or Flarum, but also from latest versions of XenForo and Invision Community.

A shameless self promotion, but for last 10 years or so I've been developing and maintaining my own forum software, Misago:

https://misago-project.org/

It's build with Python and React, so obviously not so easy to setup like PHP solutions, but there's also a magic docker setup that you can just git clone to your server and get forum running in minutes.

But with Misago I am trying to find a sweet spot between "new wave" of forum software and old solutions. So there's plenty of interactivity in the UI that JS provides and there's markdown support, but there's also classic pagination instead of infinite scrolling.

Misago used to be nice. I see they haven't updated it in a while, though...

on Misskey: https://github.com/misskey-dev/misskey/issues/9504

There is a lot of resistance to the idea. The browser UX for registering protocols is not particularly intuitive. The protocol should not be named after Mastodon because they are defensive of their trademark, and it wouldn't be accurate since the user identifier could be followed from any ActivityPub compatible software.

If you look at the newer comments on the Mastodon github thread I posted you can see web+ap:// recommended, or apub://

I think there just needs to be enough collective will to make this happen. Likely another project will need to take the lead because Mastodon team has decided the browser UX is too much of a barrier. Maybe glitch-soc can do a proof of concept.