Strongbird said:
Tumblr has started requiring accounts to view certain NSFW blogs. Since I'm not exactly keen on making another pointless account just to view adult content, I'm requesting that more users help working through the search string that I've been using and combing through leftover posts, notably madamsquiggles (Tumblr renamed to madammoo) and kingbeast.

If you happen upon a source link to a post that doesn't appear to be working, but you do have access to that artist's new Tumblr, add the full /post/ suffix to the new base URL. You'll often find that content has been ported to a new blog under the same name.

There's plenty left to do, but there's also a lot of content I'm just not interested in posting/looking at, so more help in finding and uploading better versions of posts would be appreciated in general.

It shouldn't be that way? Tumblr said that you can view the account if you have direct link, you just can't find it through searches and reblogs.

Dogenzaka
Privileged
2 months ago

Furrin_Gok said:
It shouldn't be that way? Tumblr said that you can view the account if you have direct link, you just can't find it through searches and reblogs.

Sometimes reblogs are all you have when the original source is gone though.

Strongbird
Contributor
2 months ago

Furrin_Gok said:
It shouldn't be that way? Tumblr said that you can view the account if you have direct link, you just can't find it through searches and reblogs.

Nope, using a direct link from a source field prevents me from looking at madammoo's or kingbeast's Tumblr pages without making an account. There are several others that require the same, too, but I don't recall them at this time.

leomole
Privileged
2 months ago
2014 anthro bottle bottomless cat chair clothed clothing computer desk feline fur girly headphones hoodie inside jailbird leaning leaning_back legwear liam looking_at_viewer looking_back male mammal reclining sitting smile socks solo tan_fur

Rating: Safe
Score: 117
User: Onii-chan
Date: May 09, 2014

I've noticed this as well recently. It's really annoying. I made an account just so I can browse properly.


Strongbird said:
Tumblr has started requiring accounts to view certain NSFW blogs...

Yep, that's because of the Safe Mode feature they implemented in June 2017. So now like other sites (FurAffinity, InkBunny etc) you need an account AND disable safe mode.

Also, NSFW blogs aren't indexed by Google or any other search engine, but I'm sure that's already been said.


BlackLicorice said:
Yep, that's because of the Safe Mode feature they implemented in June 2017. So now like other sites (FurAffinity, InkBunny etc) you need an account AND disable safe mode.

Also, NSFW blogs aren't indexed by Google or any other search engine, but I'm sure that's already been said.

I believe they aren't indexed because the search engines "Aren't logged in."


Strongbird said:
Tumblr has started requiring accounts to view certain NSFW blogs. Since I'm not exactly keen on making another pointless account just to view adult content, I'm requesting that more users help working through the search string that I've been using and combing through leftover posts, notably madamsquiggles (Tumblr renamed to madammoo) and kingbeast.

If you happen upon a source link to a post that doesn't appear to be working, but you do have access to that artist's new Tumblr, add the full /post/ suffix to the new base URL. You'll often find that content has been ported to a new blog under the same name.

There's plenty left to do, but there's also a lot of content I'm just not interested in posting/looking at, so more help in finding and uploading better versions of posts would be appreciated in general.

This is one of the reasons why I use password manager nowdays. Registering new accounts changed from pain in the ass to trivial thing as I can just autofill with preset information, generate strong password and save. I actually have seperate "furry" password folder because of the amount of sites I have registered account just to bypass filters and account requirements.

I'm not that hugely surprised for them going into this direction. I'm pretty sure that serving explicit content without any form of confirmations of age of visitor might bring problems to websites which is supposed to be about blogging. They have already had rules againts explicit videos.


So, is there a particular reason that anyone can glean why this doesn't work 100% of the time? I some times get 404 errors attempting it.


Nevan said:
So, is there a particular reason that anyone can glean why this doesn't work 100% of the time? I some times get 404 errors attempting it.

Are you getting rid of the first 2 numbers in the url? It should work if it was posted after 2012 and the url is media.tumblr.com/***/tumblr_***_raw.*** (*** stands for file-specific things like hash, file name, and file type).


plsignore said:
TL;DR if you're saving images from tumblr, change "1280" to "raw" in the url first!

If you're like me, you care about having the highest quality images (and if you're not like me, shame on you).

Tumblr is stupid and frustrating in that it resizes everything that's uploaded to it. If the filename ends in _540.png or _1280.png then you've saved a smaller, resized version instead of the original image, and that's bad. Most image downloaders are going to grab the 1280 version, because that was thought to be the biggest one available. But it turns out you can obtain the raw, unresized image by replacing the 1280 with "raw" in the filename.

Unfortunately, the 1280 version has been the 'standard' for a long time. I have a hunch most images uploaded here which come from tumblr are shrunken.

What do you do when the change from "1280" to "raw" change lead you to a 404 page?

Edit:Forgot the first rule: Try reading as many of the post before asking stupid questions...


Grimlock13 said:
What do you do when the change from "1280" to "raw" change lead you to a 404 page?

Make sure you remove the numbers sub-domain. Anything prior to a certain date will 404.

Strongbird
Contributor
1 month ago

Lance_Armstrong said:
Should I put the raw_tumblr_same_dimensions tag on post #1237204 or just change the source from https://68.media.tumblr.com/34bce34909b690d24458d6cbf7f16852/tumblr_oj1ejcffXD1ug7s2eo3_1280.jpg to https://media.tumblr.com/34bce34909b690d24458d6cbf7f16852/tumblr_oj1ejcffXD1ug7s2eo3_raw.jpg so that it doesn't show up in source: searches?

I don't think that tag is necessary. When searching posts to replace, it's fairly easy to take a glance at source lists with the _raw URL in them, click it once, and see if the source matches with the post. Given how many posts (worth reuploading) remain compared to when this project began, the inconvenience incurred is much less arduous now than it was before.

Moreover, the tag could arguably be used maliciously to hide posts by users who don't want to lose what they perceive as their upload 'score'. I prefer the clear, objective nature of just using source:tumblr and width:1280/height:1920 over potentially skipping over valid posts to replace.


rysyN said:
Make sure you remove the numbers sub-domain. Anything prior to a certain date will 404.

that would explain why that fails when i sometimes visit a tumblr pic.


Now here's an interesting situation. I uploaded from the artist's Tumblr, on which the raw version is 1280 pixels wide. But afterwards, when I was checking other sites to list as sources, I noticed that the artist uploaded a much larger version there, 2200 pixels wide.
The thing is, the image itself was heavily upscaled by the artist either when he colored it or when he edited the text- compare it to , an earlier version of the image. The smaller resolution version, post 1337978, appears upscaled as well. Should it still be deleted and replaced with the larger version from IB?


Penguinempire-Dennis said:
Now here's an interesting situation. I uploaded post #1337978 from the artist's Tumblr, on which the raw version is 1280 pixels wide. But afterwards, when I was checking other sites to list as sources, I noticed that the artist uploaded a much larger version there, 2200 pixels wide.
The thing is, the image itself was heavily upscaled by the artist either when he colored it or when he edited the text- compare it to post #1337999, an earlier version of the image. The smaller resolution version, post 1337978, appears upscaled as well. Should it still be deleted and replaced with the larger version from IB?

Using thumbnails in the middle of the text makes your message much less readable. Also this isn't exactly the fault of tumblr raw stuff.

There have been couple similar cases I have seen where artist themselves for whatever reason upscales the content themselves. Other one was luckily exact multiplier nearest neighbor so it could still be fixed easily. But just like with massive compression, it can get deleted even if it was done by artist.

I can see actual additional detail in stuff added into the image after the original version, so even if the base content is upscaled, the coloring and text are actually proper resolution. I would almost like to say this is almost acceptable because of that fact and because it's still artist doing it. In this case the tumblr raw is downscale of that upscale, so inkbunny version is preferred. Just tag it with upscale and put original as parent post.


Munkelzahn said:
Direct image link:
https://68.media.tumblr.com/8ad1cd85f5095d31600eabccd23e1a30/tumblr_oclfqmSkxu1vbxsy5o1_500h.jpg

That's strange, it seems as though the 'h' signifies that only height is restricted to 500 pixels, while the width can be whatever (presumably up to maximum).

While that is an interesting observation, it is still clear that the raw version (1920 x 623) is higher quality. All this changes, as you say, is the raw version redirection plugins that people use, as the extra character ('h') must be removed. I'll see if I can edit the current script to address this issue myself.

EDIT: I made a hotfix for the script, it's pretty simple, you can grab it here. I'll also let the original author know so they can make a proper update.


To-mos said:
This trick doesn't work at

Both those links work for me, and the userscript I have turned the former into the latter just fine.

Someone else reported similiar problems: https://e926.net/forum/show/243758

I had problems with raw links a while back that turned out to be a browser extension. Might be worth checking for you.


To-mos said:
This trick doesn't work at

I've had that problem as well, a workaround that's worked for me is using a proxy. I'm not sure why, but if I get a 404 error attempting to load a raw url, going through a proxy lets me load it fine.


The link that isn't working for To-mos is also not working for me and I'm the one who made the other topic. Seems like we're having the same problem.


Ok this is interesting. I tried it with a proxy server as JAKXXX3 suggested and got different results. The EU server still got 404 but the US server finally loaded it.

Results
https://image.prntscr.com/image/yudYMB-PQUK0rivND7upcA.png

Now the below image, I can't seem to get working after disabling everything and using multiple proxy sites. While the above one finally worked. This is strange.

Orig
https://78.media.tumblr.com/fd6a66aeebfe4fc0e0b88ebe57dea239/tumblr_oxqaf3rIKr1rsowjpo1_1280.png

RAW
https://media.tumblr.com/fd6a66aeebfe4fc0e0b88ebe57dea239/tumblr_oxqaf3rIKr1rsowjpo1_raw.png

Results
https://image.prntscr.com/image/pSlAk4RmTBKZSByF604e2g.png

EDIT: After I looked around I came across https://e926.net/forum/show/243758?page=1

where a user states

plsignore said:
The new workaround appears to be changing 'media' to 'data'
e.g.

https://media.tumblr.com/229d86359d9e7da34196e9939b270e48/tumblr_oxhlpu0dFA1vjc3oio1_raw.png

gives me a 404, but

https://data.tumblr.com/229d86359d9e7da34196e9939b270e48/tumblr_oxhlpu0dFA1vjc3oio1_raw.png

works.

Fucking tumblr I swear...

This fixed it for me. Until next time keep those paws movin'!

PS: I wrote a regular expression with two capture groups for any scripters out there who want to use this to quick replace the "78.media" and "_[numbers].jpeg" parts

/http(?:s)://(\d*.media).tumblr.com/[a-z0-9]*/tumblr_[A-z0-9]*_([0-9]*).jpg/g


Here's a greasemonkey script to always load the raw image

https://greasyfork.org/en/scripts/31873-use-tumblr-raw-image

Munkelzahn
Privileged
7 days ago

KiraNoot said:
data.tumblr.com throws certificate errors. The canonical url for that is https://s3.amazonaws.com/data.tumblr.com/ which means that https://media.tumblr.com/607edc95dc02a676405d66e3f82fe746/tumblr_oxoxuvLXbc1tv4a0ho1_raw.png becomes https://s3.amazonaws.com/data.tumblr.com/607edc95dc02a676405d66e3f82fe746/tumblr_oxoxuvLXbc1tv4a0ho1_raw.png

How do you _raw'ify this Tumblr post?
forum #243192

I keep getting errors when I try.


Thanks for this thread, I uploaded my first image with data.tumblr and raw file! (Added tons of tags, too) Let me know if I did ok.
Question, what's the first source I should list? The raw file, or the tumblr post itself?
EDIT: Actually, since the canonical URL is s3.amazonaws.data.tumblr, should I redo my upload???