+1

I don't really see much benefit in keeping the MD5 as a filename considering it doesn't hold any information to the image itself. The only case I found it useful is when the image is corrupted, meaning, only once.

i dont see much benefit in filenames like :

moe%2027551%20tagme.jpg

or

moe%2025466%20chen%20cirno%20ellen%20elly%20gengetu%20genjii%20koakuma%20kurumi%20luize%20mai%20meira%20mima%20mugetu%20orange%20rika%20rumia%20ruukoto%20sara%20shinki%20tokiko%20touhou%20yuki%20yumeko.jpg

either.

* You cant sort them

(moe 1234 x
moe 2234 x and houndreds of moe 1235 - moe 2233 in between, great)

* You get dupes way more easily

(moe 12345 x tagme.jpg gets moe 12345 x y.jpg then moe 12345 y x.jpg and so on)

* Only the id/md5 helps you to find the pic fast

* Loss of integrety check (well its harder as you only get the md5 by complicately looking at the link)

and other reasons im too lazy to list right now.

its still easier to download pics into folders

there it doesnt matter how the pic is called...

(long filenames can cause stupid shit on win systems btw)

I too am against it. I use the MD5 hash name as a way to check for dupes locally. Often times I'll go to save a picture and I'll get the "this file already exists" message. Which is great. Because I could have saved it off any one of the boorus.

I sort by date modified anyway so it doesn't bother me that way.

And as MDGeist mentioned, it's easier to search by hash. I'm sure you can still do this, but I wont know what the hash is as easily. I find it useful when trying to tag pictures on my personal 'booru, as well as when trying to refind a picture to link to a friend.

That said, I do remember and still have files from when moe.imouto named them moe_imouto_org-p-118529650583164.png (Which feels like so long ago, but I guess it's not?)

+1

Isn't this going to screw up the MD5 searches on the site?

You're contriving a bunch of make-up reasons. You aren't making any kind of a "case" by making the filenames look worse than they are (pasting URL-encoded text instead of the actual filenames to make it look ugly; using obviously contrived examples like a tagme and a rare tag-heavy post). A typical filename is "moe 27550 blanc_neige elwing shining_tears tony_taka.jpg", which is nice and clean.

Download filenames are for humans, and MD5s as filenames are opaque and useless to humans. I can't find anything in a directory full of them. It's interesting that you mention sorting, since these filenames usefully sort by post number, where MD5s sort statistically randomly.

Long filenames are cut down to 150 characters or less.

If you want to have MD5 filenames, you can write a GM script to rewrite "http://moe.imouto.org/image/MD5/text.jpg" URLs to "http://moe.imouto.org/image/MD5.jpg".

It doesnt help anything if they are sorted by post number if you look for all pics of a certain series/artist/genre/whatever...

Still easier to go to the section and download them there, in another folder.

Well mayor reason for md5s is the nondupe stuff.

Thanks god I dont rely on moe-online-browsing nor on browsing via filenames on hdd ...

as for the GM script
its not that easy
(hello .png -.-)

Another +1

Personally, I do my downloads with DTA and having the hash as the filename means less dupes for me when somebody decides to change tags, and less of moe's bandwidth used as a direct result.

Is there any way to make this some sort of user preference, rather than telling users to go code up something on their own?

EDIT: Erm, yes, I've had this username for a while, it's just a coincidence...

url = url.replace(/(.*\/image\/)([0-9a-f]{32})\/.*(\.[^. ]+)/, "$1$2$3")

(A lot easier than the script I've been using to get sensible filenames for the last few months, which involved rewriting URLs to a PHP script on another machine, which set Content-Disposition headers and proxied the file...)

So we are going to have to use 'Image Search' instead of checking the MD5 hash now?

I don't know what you're asking. You can still do md5: searches.