Pleroma has rich text support, emoji reacts, polls with more than 4 answers... It never struck me as having less features than Mastodon, except maybe when it hadn't gotten polls yet at all some months back.
I was thinking of using a fediverse instance for my blog but I am unsure whether it's a good idea.
I think federated blogs are the answer to google killing rss.
Even your own blog that you just linked publishes working RSS! https://wrt.nth.io/luke/feed/
The replacement for RSS is to stop inexplicably thinking RSS is somehow gone.
1) people stop inexplicably calling it "dead"
Being "dead" has its fringe benefits, at least, like no one proposing changes for the sake of change - it gets to be happily frozen and useful with no one trying to e.g. update it from the XML-everything mania of its time (embarassing in hindsight) to the JSON-everything mania of our time (I'm worried there won't even be a hindsight for it to be embarassing in).
Well, except when people propose to replace it with something else because it's "dead" (sorry, I have no interest in following anyone on activitypub - if I want updates from your blog, I will poll the RSS feed you have kindly provided).
As someone who has written a parser library and a RSS reader program, I can tell you that it is an endless battle of users always reporting yet another feed that is "breaking your RSS reader".
When investigating why the feed does not work well, you always end up finding yet another way how a site can implement RSS/Atom badly while still following the letter of the specification.
I love the idea of RSS/Atom and the possibilities they allow, but hate the actual specs.
So given that, any chance you could elucidate on fault you find with Atom?
Still, I vaguely recall that there was at least one vagueness in the Atom 1.0 spec that I found abused in a real world feed, but can't for the life of me remember it - it's been a while.
Now I can't remember the last time I saw a site promoting or even clearly mentioning above the fold that they publish an rss feed. I didn't know HN published one until now.
That's why I haven't argued with anyone claiming it's dead. It seems like it disappeared.
[0] https://feedly.com/i/subscription/feed%2Fhttps%3A%2F%2Fmicha...
Then you just expand on the options and uses to someone who's already favorable toward RSS because it was so painless to use they didn't even realize they used it to follow some of their favorite people.
https://wordpress.org/plugins/activitypub/
The ActivityPub ecosystem is pretty interesting. Look at it closely.
Regarding the backend. It does seem that Mastodon was the first one and has more functionality, but (1) Pleroma is catching up and (2) waaaaay lighter on resources. Mastodon is built on Rails, requires PostgreSQL, Redis, a task server (sidekiq) and optionally Elasticsearch. Pleroma goes by with just PostgreSQL and is built on Elixir.
Regardless of technology, what I'd really like to see in a future version of these AP-systems is the ability to manage multiple-domains with a single database / application server. Right now all implementations assume that the domain of the backend is the domain of every user in the instance. So this means that if I want to host Mastodon for a user with a custom domain, I'll have to spin a instance/database just for this user. If I could have a separate mapping between account / domain, one single instance could manage everyone.