[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/h/ - Hentai


Thread archived.
You cannot reply anymore.


[Advertise on 4chan]


File: 1753068850672840.png (1 KB, 101x62)
1 KB PNG
What's up with pixiv filenames seemingly randomly changing from the original 145954923_p0 (random front page pic) format to a way longer hash? Via google I found someone say that it's mostly loli and other r18 content getting hit with the change, which seems to be true. Clicking a bit through the sfw section which I normally never use and all I can find is the old format. Should I be concerned about pixiv somehow fucking with r18 pics to fingerprint you or something? It feels pretty weird.
>>
I very much doubt it's fingerprinting, too easy to change the filename and usually it gets changed when uploading elsewhere anyway.

Could be related to image revisions, or some A-B testing that needs to affect how things are getting cached. I haven't seen any evidence that the files themselves are getting tampered with so I doubt it's anything malicious.
>>
>>8898485
The fact that it disproportionally affects possibly questionable r18 content and that it retroactively changed the filenames of old pictures (this fucked my flow of trying to download a pic to check if I had it already saved, and also rules out the change being related to image revisions) makes me think there's something weird going on here. I was just surprised to find no discussion about this anyhwere outside of 1 dead reddit thread.
>>
Yeah I've actually tried and every single Tanya pic I try to download has the new file format, while before when I was just checking bookmarked artists every few days it was 50:50. It seems like it either applies to loli content specifically or has some other weird criteria, but in any case, I don't think this is going to be anything benign..
>>
I don't know, it's happened to me twice for a few days and then weeks of not happening in between, loli or not. A similar thing with something switching back and forth a few times happened years back when they were A-B testing their current site design.

Might have to do with a move to content-addressable distributed storage, for which they can't use the current filenames, because those don't change when a pic is updated. Or maybe servers are getting moved to a new system one by one and during the move they need to disambiguate the filenames.
>>
it's a small consolation but at least possible to reverse the embedded hash so the filename is just the artwork id by removing everything between the - and _
eg:
>picrel's filename is 141863128-1c5293133b8225465a2e60891a874b4c_p0.jpg
>"short" filename should be 141863128_p0.jpg
>>
It's 100% targeting loli for sure.
But the weird thing is it also randomly applies to a lot of stuff that isn't even remotely loli or even adjacent.
>>
>>8903903
Way to contradict yourself there.
>>
>>8903936
>Some retard on /h/ lacks reading comprehension, what a surprise
Look idiot, almost all (but not 100%) of works tagged with both R18 and loli will get hit with the weird hash-filename format change within about 24 hours of being posted.
Oddly nothing seems to have the hash-filename format when initially posted, implying Pixiv is doing some kind of scanning after the fact.
Moreover, as far as I can tell 100% of works that are region-locked also have the hash-filename format.
But some works that aren't remotely loli also get hit (including works form years ago) and there doesn't seem to be any obvious pattern, no rhyme or reason to it, except that I think all of them are tagged R18.
>>
For example, look at this post, it's not hit by the hash-filename thing: https://www.pixiv.net/en/artworks/130876961
But from a quick scan it appears all (?) of their posts prior to that one did.
Posts after that one are largely not hit, but a few are, and a few of their newest posts are as well.
This post https://www.pixiv.net/en/artworks/146007475 had been hit, but now it just has the regular old filename again as of a few days ago.
Very strange behavior on Pixiv's end and it's all extremely sus.
I don't know when this started exactly but it was for sure happening by the end of Febuary because I have files saved in this sussy name format since 2/28.
>>
japs are becoming such fucking faggot cucks man
>>
>>8898474
>fucking with r18 pics to fingerprint you
all images already have hashes, what do you mean
>>
>>8904155
>no rhyme or reason to it, except that I think all of them are tagged R18.
might be on an account basis? I haven't checked it out yet. If someone uploads targeted content they might trigger a flag and subsequent uploads get the "new" format
>>
>>8905373
In the filename? No.
>>
>>8905374
Yes, the evidence is all very circumstantial but I'm fairly sure that that's likely a factor for whatever algorithm/AI they're using to flag stuff for this filename change.
Still can't imagine why that affected the account I linked; everything they posted now and in the past is incredibly tame. Probably just false positives.
>>
>>8905170
There is a reason they mostly moved to misskey and made misskey detect and reject users outside of Japan.
>>
>>8905865
...Unless you happened registered an account before august 2023 :^)
>>
>>8905865
You can still follow and see their posts on the non-japanese misskeys though.
>>
>>8906193
there's also this
https://sleazyfork.org/scripts/584516-misskey-io-uncensor-nsfw-18-images-without-login-other-tweaks
>>
>>8906194
that way you only get the previews though
>>
>>8898474
Use
https://github.com/xuejianxianzun/PixivBatchDownloader
you fucking retard
>>
>>8906304
Hows this compare to pixivutil2?



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.