shork @noiob@awoo.space

purism's mastodon fork completely removing the ability to report users is an extremely bad look on both the part of purism themselves, but even moreso on the part of eugen for being the one to actually implement that change for them, which is a great way to seriously undermine your own credibility w/r/t the community management features in your own project that people actually expect you to give a shit about

Admins: perhaps you should consider blocking social.librem.one. This instance’s policies could affect the safety of many of us on the fediverse. The instance automatically rejects both local and remote reports, meaning there is no way to bring bad users and content to the attention of their moderators. See here: https://source.puri.sm/liberty/smilodon/commit/9cae431902a2c0ce6438c6722a3a901e279c78fc

In discussion within their chatrooms, I received this response:

quick note about reporting (copied from other chat room): this is correct, after deep deliberation we have concluded that no company should control speech - we have a “stay safe” guide in the pipeline, but briefly, block bad users and report illegal content - in the long-term federated, community-managed blocklists are likely the answer

This does not seem right to me - if we’re subjected to their users, the only action admins can take is to block their server rather than have our issues addressed. This makes for a poor member of the fediverse.

What features, you ask?
- polls! polls!
- profiles now look the same in the webapp and on the public page
- you can now pin hashtags on your profile, and those will show up in the directory if you're opted into that (https://awoo.space/explore)
- new landing page (work in progress)
- new UI for managing your network at https://awoo.space/relationships
- you now have to opt into disclosing what app you use to toot
- probably more

Awoo! ​

We updated! Please reload the site to enjoy all the Mastodon 2.8+glitch features