@Moss Regardless of whatever transpired, I spent a good chunk of last summer doing fedi dev myself and kaniini's assistance was very helpful. Having more types of servers at much smaller scales is, imo, healthier than having just giant mastodon instances, and pleroma helps with that.

I do wish they'd curate the list of pleroma instances just a touch, and remove some obvious bad actors, though.

@gdorn understandable, just don't take issue with those that are wary or defederated from that lot because most of the good ones are for decent reason.

@Moss Yeah, I take no issue with anybody who chooses to block or silence any user or instance, for any reason.

I take issue with the way in which social.coop silenced those instances at the behest of users not even on this server, without polling the userbase about it, or even notifying us (as far as I saw). I'm also unsure how anybody would find out about said silencing except by accident (the way I found out).

@gdorn thats def does not sounds co operational in nature. Fair warning, don't go to sbc it's the other co-op instance and it has its own problems. Let me know ifnyou'd like a short list of recommendations and what you're looking for.
May you Migrate into Comfort.

@mewmew Yeah, it's on my to-do list. I was building a mastodon-compatible server in Django (thus my frustration in trying to communicate with kaniini in the first place) but I might just set up a pleroma instance on my VPS.

@mewmew my project partner had one set up on a raspberry-pi-esque single-board computer and it was pretty easy. Far easier than mastodon is to install.

@FloatingGhost Yeah, it's rough. But where I stalled out was getting the masto front-end to play nice with the server. Federation was next on the list.

I'm not much of a react dev, and masto's react is extra spicy. Much like the rails code, which is why we tended to rely on pleroma for reverse-engineering instead.