In response to the NSFW ban being enacted by Tumblr Staff, on December 17th 2018 I propose that we all log off of our Tumblr accounts for 24 hours.
The lack of respect and communication between staff and users is stark. Users have been begging staff to delete the porn bot outbreak, which has plagued the website for well over a year. The porn bots oftentimes send people asks and messages, trying to get them to go to a website full of viruses. They also spam advertisements on others posts.
Users have also begged that Tumblr ban neo-nazis, child porn, and pedophiles, all which run rampant on the site. The site/app got so bad that it was taken off the app store.
However, instead of answering the users, Tumblr has instead taken the liberty to ban all NSFW content, regardless of age. But users have already run into issues of their SFW content being marked as sensitive and being flagged as NSFW, not allowing them to share their work.
Not only does this discriminate again content creators, but it also discriminates against sex workers. Disgustingly, the ban will be enacted on December 17 which is also International Day to End Violence Against Sex Workers.
This ban is disgusting, and while I (and plenty of others) welcome porn bots and child porn being banned, the Tumblr filtration system is broken. It tags artistic work’s nipples as NSFW (when it is art), it tags SFW art as NSFW (when it is not), and does not stop the porn bots, neo-nazis and dozens of other issues.
This ban is discriminatory. This ban is ineffective. This ban is unacceptable.
To protest, log off of your Tumblr account for the entirety of December 17th. Log off at 12 am EST or 9PM PST and stay off for 24 hours. Don’t post. Don’t log on. Don’t even visit the website. Don’t give them that sweet ad revenue.
Tumblr’s stock has already taken a hard hit. Let’s make it tank. Maybe then they will listen to the users.
Reblog to signal boost! We must force change.
If you don’t like what’s going on, this is an easy way to protest. Takes zero effort. They may not listen, but it’s fun to watch their stocks plummet.
Ok so the glitch that ive seen people talking about as muting people isn’t actually muting people. General premise
The glitch is “tacking” some of your recent posts (mine were from the past 2 days only) to the top of your blog
Reblogged posts that don’t get “tacked” show up after all the tacked posts, which could be a few pages back
Posts appear in the correct order in your archive and on the dashboard, so this glitcb seems to only affect actual blog page formatting.
Posts appear in the correct order to you when looking at your own blog on mobile or in the sidebar on desktop, but not on your actual blog page.
Posts appear with the wonky tacking order to anyone else looking at your blog. They still see your posts on their dashboards correctly tho.
what posts get “tacked” doesnt seem to be related to whats flagged as explicit as far as i can tell. only one of mine was actually flagged (that sand dune post) a bunch of them didnt even have pictures on them
so heres the temporary workaround i did that seems like itd be effective until tumblr actually fixes the issue
view your page when youre not logged in, so you can see the tacked posts and messed up order as other people do. on another device or another format, go to your blog while logged in (i veiwed mine logged out from a mobile browser and logged in on the app)
using the logged-out view, identify which posts are tacked to the top of your blog
in the logged in device/format, scroll until you find the tacked posts. click Edit and then click Save (if on desktop) or Post (if on mobile). you do not have to make any changes to the post itself.
refreshing the logged-out view, you should see that the post you edited is no longer tacked to the top of your blog
repeat with all tacked posts until the order you see when logged out matched what you see when logged in. its a kinda annoying process but since the glitch seems to have started yesterday-ish, there shouldnt be too many tacked posts. mine hadnt tacked anything that was posted before then
yeah hopefully this is somewhat helpful until the thing actually gets fixed