Post #2358054

2022-11-23 04:11 UTC

@Tinu@mastodon.social @haven4books@disabled.social The upside to Mastodon is that the code is publicly available, unlike the closed systems of proprietary platforms. It’s not your responsibility to check for problems, but as a developer I could, and I’m sure many others already are - I’d expect anything problematic at the software level to be called out pretty quickly.

Replies (3)

@jcc@mastodonapp.uk 2022-11-23 04:11

@Tinu@mastodon.social @haven4books@disabled.social Federated instances are great, but any response (no matter whether intentions were good or not) to your concerns that goes along the lines of “you can set up your own server!” is absolutely the wrong take in this case, when we’re discussing the policies of what’s probably going to be the “default” community.

Open ##2358055
@Tinu@mastodon.social 2022-11-23 16:26

@jcc@mastodonapp.uk @haven4books@disabled.social Yeah from my IT troubleshooting days, step 2 is gathering data to see if there actually IS a problem or if you are experiencing a feature as a problem. Which is why I wondered allowed. I wasn’t being snide or snarky. I literally don’t know.

Open ##2358070
@jdp23@indieweb.social 2022-11-23 17:52

@jcc@mastodonapp.uk @Tinu@mastodon.social @haven4books@disabled.social Called out, but not necessarily fixed. Case in point: "Local-only posts", that don't get shared to other instances, are very helpful at reducing abuse for people who are on well-moderated instances (and good from a privacy perspective, too). The glitch fork implemented these in 2017, and the Hometown fork also has them. But Mastodon's BDFL Eugen has rejected them from the mainline code, so they're not available on most sites.

Open ##2358162