>>3927098I couldn't care less if some antifur activist didn't get it, but this reply made me think that maybe the joke was completely lost. It's not that an artist titled his picture "Gayer," that would be pretty silly, I was talking about the Twitter filename.
https://pbs.twimg.com/media/GayerxRaAAA7a_S.jpg:origImages on Twitter have a filename formed by letters and numbers, and the uploader can't choose it. If you look at any other pic from Twitter in this thread (or on Twitter) you'll see that they're usually random gibberish. I think it was a funny coincidence that such a pic started with a legible word, but for the sake of it I'll add that it was a pretty unlikely coincidence.
You have an incomplete explanation here,
https://stackoverflow.com/questions/21919766/image-url-naming-scheme, but to summarize it, the first letters in the filename are the timestamp at which the image was uploaded.
If we convert GayerxRaAAA7a_S from base64 to binary we have 00011001 10101100 10011110 10101111 00010100 01011010 00000000 00000000 00111011 01101011 11110100. The first 42 bits are 441081052241 in decimal. Add the 1288834974657 from the Github link (the value is wrong in the Reddit explanation) and you get 1729916026898, a timestamp from the 26th of October, the day the image was uploaded. So far, so good.
Out of all the possible filenames that would start with "Gayer", the first one would start with "GayerAAA" and the last one would start with "Gayer___". The timestamp for the first possible file would be 1729916023745, and the last one would be 1729916027840. There are 4095 milliseconds between both timestamps. Out of all the files uploaded to Twitter ever, only those uploaded in a span of barely 4 seconds could have a filename that started with "Gayer."
If you were curious, there was a span of 63 milliseconds between 1660895072001 and 1660895072064, back on the 19th of August of 2022, when pics uploaded to Twitter would start with "Faggot." I didn't see any of those.
