Image filenames have become randomized

[ahobaka]

Don't know if this is a bug or a feature, but now file names have become completely random when I save them from mangadex

They used to be ordered correctly (1.jpg, 2.jpg) but now they are something like "1c06178ae7a3f35ff0a72a76d2b116b6591329389241f2fa0534cf44b2731366.jpg"'

Is there a way to revert to ordered numbers?

 

[BzzBzz]

Why don't you change filename before saving?

Edit: probably MD@H feature. In my case without MD@H it's good old 1.jpg 2.jpg etc.

 

[saktomo]

How did you get the numbers to revert? I've unchecked 'Turn on MDHome', logged off Mangadex, cleared cookies, and restarted the browser. I'm still getting the gibberish names. Does anyone knows how to get the new chapters to show with the old number scheme?

 

[BzzBzz]

Looks like it's new chapters only… most likely "working as intended"

 

[ahobaka]

Ah I see, yeah it's definitely MDhome peer-to-peer system that's renaming the images. Hentai @ home doesn't do this though -- the cache files on my hard drives are random but the images themselves on galleries preserve the original filenames that they were originally uploaded with

Maybe more work needs to be done so we can keep the original numbering system.

 

[Holo]

It was changed for corruption checking to be added to MD@H in the future.

I'll change it do it keeps the page number. "page-hash.ext", maybe

 

[BzzBzz]

> It was changed for corruption checking to be added to MD@H in the future.

Do you really need sha256? Why don't use sha1? Yes sha1 isn't safe for encryption but in case for simple corruption checking isn't it fine?

Especially considering that sha1 is much faster than sha256?

 

[Holo]

I think it's to make it harder for people to add extra bits to fake the hash? In any case, I was advised to go for SHA-256 by the devs.

 

[Sayo_Aisaka]

> I'll change it do it keeps the page number. "page-hash.ext", maybe

While you're at it, is there any chance you could change the numbering scheme to use leading zeros? My Edo period image browser doesn't recognise "natural" sort ordering.

Edit: Never mind, I see you've already changed it. Please ignore.

 

[BraveDude8]

@BzzBzz A typical CPU can compute hundreds of thousands of SHA256 hashes every second. It's such a microscopic amount of compute time versus actually sending or receiving the image that it's not worth being concerned about. SHA-1 hasn't been secure for about fifteen years, and there's no real reason to use it. If we wanted something faster we'd be better off with something like Murmur, but again, not an issue.