Show newer

On the Fediverse there are a ton of people who read your posts and don't interact with them

Potentially NSFW 

From their standpoint it makes you feel maximum pain from multiple long-time fans of the alt-right.

Death... I'm so distressed about this!

— Litast Kadolgúr, sheriff

@realcaseyrollins McDonald's needs it - they're the ones who oppose paid sick leave, so their staff is likely to spread it to customers.

@shampoobottle @realcaseyrollins Ahh I think I understand now. Pleroma supports additional threading features not found in Mastodon. However, it is also completely backwards-compatible with Mastodon.

Apps like Tusky will work fine with a Pleroma server, they will just show threads in the Mastodon style instead of how Pleroma users are used to.

Pleroma also has a Mastodon UI with the same status here (gotta login again): gleasonator.dev/web/statuses/9

It works as expected. The API endpoints are the same in both cases. They are:

gleasonator.dev/api/v1/statuse
gleasonator.dev/api/v1/statuse

Compare to:

gleasonator.com/api/v1/statuse
gleasonator.com/api/v1/statuse

They are the same, except the Pleroma one has an extra "pleroma" tree with additional data.

This shouldn't be a setback to Soapbox at all. If anything it adds more data rather than taking anything away.

@shampoobottle @realcaseyrollins If it's an issue I can always edit the endpoint or transform the output within the frontend. Ultimately I want Facebook-style threading. This will definitely be an undertaking with a big learning curve, but it will be less difficult than writing an entire new backend from the ground up as I was planning to do a few days ago.

Just got an "RPC scale dropped at the server" message from . Anybody know what that means?

Show older