@NonPlayableClown@dcc@threat blanket censorship is blanket censorship. All our NSFW media is marked as such so the only reason you have for blocking our media is because you just want to make it harder for people on your server to see our media. Just like how it's hard for people on poast to see your posts.
I don't care if you want to be a censorship heavy dictator but claiming, "but it's different when I do it," is pretty fagpilled m8.
it does not appear he is blanket censoring. he chooses to block your instance's media. it's a choice/preference just as you choose to post, yes?
> "but it's different when I do it,"
i didn't interpret it like that. he makes a choice to block media for his instance. that's materially no different than you deciding to post the stuff you post.
@threat@dcc@NonPlayableClown you seem to be missing the point of the conversation. We're specifically discussing his decision to censor my media on his instance. Yes people can switch instances and get around the censorship easily enough but that's irrelevant to the discussion at hand.
> you seem to be missing the point of the conversation.
i am not. i can read and interpret english just fine
> We're specifically discussing his decision to censor my media on his instance. Yes people can switch instances and get around the censorship easily enough but that's irrelevant to the discussion at hand.
sure is relevant. if he chooses to block your media, that's his choice. is life constructed in a binary tree of 0 and 1? maybe so, but humans introduce a grey area. if he decides your media is not to his liking, and he's paying the server bill, it's his choice to do so.
@threat@dcc@NonPlayableClown@sjw sjw unfollowed me because my client doesn't use image filenames, it just sets them all to "blob", triggering a bug in pleroma that makes the image not check MIME type and set an appropriate URL.
The images still render fine in basically every browser.
I use thedesk.top, which is written for mastodon and misskey - so although it avoids most of the annoying mastodong things like image limits (still applies on mastodong instances, but not on pleroma even though it uses mastodong's API code), it still has some quirks. For example, if you choose to load media from remote source instead of from local instance proxy (generally irrelevant since most instances disable it, and of the handful that don't, I've seen one that overwrites remote_url with the proxy as well wtf), gifs will no longer play because they try to render as a video (because mastodong media mangling). In fixing that I introduced a bug with videos on pleroma instances viewed from mastodong accounts which I "fixed" by checking the file's extension.
And now cutls has gone and converted the whole thing to typescript (it's an electron lmao), so I can't be fucked adjusting my patches. I'd rather be writing my own client.
@sjw@threat@dcc@NonPlayableClown My point is that the client doesn't impose these restrictions; since cutls also uses misskey, and is thus not a true mastodonger.
Add comment