Apparently .art has updated it's rules so that I have to cw nearly all my posts, not just blur the media.
-
Apparently .art has updated it's rules so that I have to cw nearly all my posts, not just blur the media. This means that for nearly all users have to click on the cw, then click on the blurred media, making it extremely unlikely anyone will bother. It also makes it much harder to crosspost, since I can't simply cut and paste the post.
Sigh... stacked on top of the way they soft-block all mastodon.social users, it's quite a burden. I wonder if I should move...
-
Apparently .art has updated it's rules so that I have to cw nearly all my posts, not just blur the media. This means that for nearly all users have to click on the cw, then click on the blurred media, making it extremely unlikely anyone will bother. It also makes it much harder to crosspost, since I can't simply cut and paste the post.
Sigh... stacked on top of the way they soft-block all mastodon.social users, it's quite a burden. I wonder if I should move...
@view Oh no, we've been soft blocked?
Everything seems to work on my end, though. -
@view Oh no, we've been soft blocked?
Everything seems to work on my end, though.@vadhakara you've been for a long time. I have to manually whitelist every .social user that shows up.
You weren't even allowed to follow me until I manually approved you. It's how .art has worked for at least a year.
-
@vadhakara you've been for a long time. I have to manually whitelist every .social user that shows up.
You weren't even allowed to follow me until I manually approved you. It's how .art has worked for at least a year.
@view Oh shit, so it places the burden on you, lame. To be fair though, .social has got more spam on the live timeline than any service I've ever been on. Companies and scammers just signing up left and right to shoot their digital diarrhea in to the void. The only reason I'm still on it is because I've been too lazy to find a new server. Maybe it is time.
-
undefined Oblomov ha condiviso questa discussione
-
Apparently .art has updated it's rules so that I have to cw nearly all my posts, not just blur the media. This means that for nearly all users have to click on the cw, then click on the blurred media, making it extremely unlikely anyone will bother. It also makes it much harder to crosspost, since I can't simply cut and paste the post.
Sigh... stacked on top of the way they soft-block all mastodon.social users, it's quite a burden. I wonder if I should move...
Yeah, the idea that every user has to click on my TPS report and then click on the still-blurred image after reading through my TPS report makes Mastodon... pretty unusable for adult content? It's painful both to post and view.
Any suggestions? Maybe a server that just lets me blur images without also layering a CW TPS report on top? I may limit my Mastodon posting pretty aggressively since this is a burden both on the poster and the viewer...
-
Yeah, the idea that every user has to click on my TPS report and then click on the still-blurred image after reading through my TPS report makes Mastodon... pretty unusable for adult content? It's painful both to post and view.
Any suggestions? Maybe a server that just lets me blur images without also layering a CW TPS report on top? I may limit my Mastodon posting pretty aggressively since this is a burden both on the poster and the viewer...
@view FWIW adding a CW will automatically blur the images, and the viewer can click on the image to unblur it even without opening the CW (it's still necessary to open the CW to read the text). The use of CW is also pretty standard for lewd content (you're basically the only NSFW artist that I follow that didn't use it, from any instance), which is useful because not all Fediverse software understands the per-image flag.
1/2
-
@view FWIW adding a CW will automatically blur the images, and the viewer can click on the image to unblur it even without opening the CW (it's still necessary to open the CW to read the text). The use of CW is also pretty standard for lewd content (you're basically the only NSFW artist that I follow that didn't use it, from any instance), which is useful because not all Fediverse software understands the per-image flag.
1/2
@view TBH I would have guessed that aggressive moderation would have been more impactful. I know of artists that have chosen to move to other instances because of it.
2/2
-
@view TBH I would have guessed that aggressive moderation would have been more impactful. I know of artists that have chosen to move to other instances because of it.
2/2
@oblomov I don't believe you can click the image without accepting the CW. Let's find out.
-
@oblomov I don't believe you can click the image without accepting the CW. Let's find out.
@oblomov Nope, image is hidden inside the CW.
-
Yeah, the idea that every user has to click on my TPS report and then click on the still-blurred image after reading through my TPS report makes Mastodon... pretty unusable for adult content? It's painful both to post and view.
Any suggestions? Maybe a server that just lets me blur images without also layering a CW TPS report on top? I may limit my Mastodon posting pretty aggressively since this is a burden both on the poster and the viewer...
It's become pretty clear CWs are the accepted norm on Mastodon, even though none of the unblurred content is objectionable.
Sigh, you can't fight the crowd, I guess. Even if you're all clearly doing SUB OPTIMAL CONTENT ACCEPTANCE PRACTICES.
-
@view well, this is weird. It works from my instance. Did they change the behavior in more recent versions of Mastodon maybe?
-
@view well, this is weird. It works from my instance. Did they change the behavior in more recent versions of Mastodon maybe?
@oblomov I don't know. Mastodon.art and mastodon.social both hide it.
-
@view ah so it's probably version-related, my instance is still on 4.2 and I can see the image and click on it to unblur
8-/
