so i spent far too long on this.

for those unaware, the spaghetti wall of letters and numbers is a base64-encoded JPEG image (and not a URL as some guessed). in certain cases when you tried to insert/paste an image into what’s ostensibly a text-only box, this could happen.

the thing that’s bugging me however is that there’s image data there. we have fairly a clear (albeit with JPEG artifacts) screenshot of text that, thanks to how Windows ClearType renders text, each character is identical to each other, that is to say, an uppercase Q will always look more or less pixel-perfect each time, meaning we don’t have to guess what a Q looks like, we simply have to pixel-accurate match it.

as an aside, this is why regular OCR struggles so much with this kind of data retrieval, such as code even when it’s clearer than a physical paper scan. ordinarily, OCR will try to best-guess every single letter because it expects each letter to be slightly different from each other (as would be the unpredictable nature in a scanned document), and on top of that most OCR today will try to autocorrect because it expects the scanned text to contain words in some human written language.

so, all we have to do is make a program to recognize each character and piece back together the whole base64 string, right? well…

first i stitched all 7 images back into a single block of text, observing the consistency of the line spacing. some of the screenshots have little bits of the previous one sticking out of it, which helps with alignment and to make sure they’re in the right order.

after that i had to sample every single letter off this file. this means going around the file and finding one example of each different character we’re trying to identify, saving it as its own separate file so that the program can load them as references to compare against in the full image. for base64, the alphabet consists of a-z, A-Z, 0-9, +, / and =. once i had the initial code in place…

…close! but oh so far. if any one single character in a base64 string is wrong or missing, the resulting decode will be wrong. the issues i was having were mostly with the lowercase r and j because of how the kerning affected the pixels around those letters. i was also getting false matches for r where there should be an m. what followed was grueling hours of tweaking the matching code and my known font set to better fit the original image and get as close as possible to a 100% match. here is the resulting code, maybe it’ll be useful for someone and this won’t have been a complete waste of time.

once i was confident through the verification image that i had all characters recognized, i put it through a base64 to JPEG decoder. i actually did this several times as i improved the recognition and what follows is the best result that came out of it yet. i suspect some of the data might be missing (perhaps a line or block of text got lost in between screenshots), or i have a wrong character somewhere resulting in a wrong value. this is the image extracted from OP’s base64 string:

we can finally know what they meant when they said “me in a relationship” and i can finally go the fuck to sleep.

update: i found that the string that i used to decode the image in the previous reblog actually had one letter wrong.

with this it still doesn’t parse as fully valid base64 in strict mode so i think there’s still another letter in there that’s wrong, but i couldn’t find it. however this gives us a better look:

and this is finally enough to do a reverse image search. i present to you, the HD version of our intrepid massive backpacker:

still have no idea what they mean by “me in a relationship” with that, though.

#they have baggage

Alright, to ao3's soon to be arriving Wattpad Refugees, a basic guide to general user culture:

1.) Unlike Wattpads vote system that let's you like each chapter, the ao3 equivalent kudos only allows one per work. Everyone is generally quietly annoyed about this. To engage with each chapter, you're heavily encouraged to comment. Trust me, it makes people's day.

2.) Ao3 has no algorithm. By default it's latest updated work first. You can find things to your taste through searches, filters and tags.

3.) 'No archive warnings apply' and 'user has chosen not to use archive warnings' mean two very different things. No archives warnings means the work is free from any content that could require a warning tag (character death, graphic depictions of violence, non-con, etc). User has chosen not to use archive warnings means it could contain any of the warning content, be it hasn't been explicitly tagged. Treat it like an allergen. No archive warnings apply is allergen free. User has chosen not to use archive warnings, may contain traces or whole chunks of the allergen. If you're likely to have a bad reaction, maybe don't take the risk.

4.) Speaking of warnings, ao3 has very few restrictions on the type of work that's allowed. Whatever your personal thoughts or feelings on that are, thats how the site is. You're likely to run across some dark subject matters and a lot of people are uncomfortable with reading that. You're well within your rights not like these works and have your opinion on whether they should be allowed, but harassing the authors of such works (or any works) is more likely to come back on you than them. Ao3 operates on a strong policy of 'don't like, don't read'. Use the tagging system to your full advantage to only engage with the kind of works you want to see.

We look forward to welcoming you all and seeing the fantastic works you create. Happy writing!

I misread this poll, and now I'm curious

When you imagine fanfic scenarios in your head/fantasize about existing fictional characters,

NEW VERSION. :)

Oh, it's a very important day today then.

Me on a Saturday afternoon.

[ID: A photograph of a Pallas Cat in a pile of sand, presumably in the middle of a dust bath; the cat is lying on its back, all four feet in the air, looking like a real Unit with a thick body and fluffy long hair, and an expression of bliss on his face that I'm probably imagining.]

✍️ more fic writer asks!

lucy gray🍂🎤

sometimes it hurts me to remember that's s2 of s&b completely disregarded inej’s arc. because her biggest fear wasn’t that kaz and her couldn’t fall in love or touch - it was that she was afraid to become useless to him, afraid of what her parents would think of her, of what she though of herself, of what she wanted. and then they just wrote her off on somebody else’s ship when kaz was the one who bought that ship for her, the ship that she was captain off, that she used to hunt slavers so nobody would be hurt like she was right after kaz reunited her with her parents.

for real! as much as i love the hallucination scene, it's honestly more something kaz would've thought about than inej. the ship thing pissed me off so much, i swear the writers thought "i will have you without armor" was just some kind of rejection instead of her accepting that neither of them are ready to be in a relationship.

i just need to know if anyone else read kos and totally shipped isaak and ehri cause i never see anyone talking about them and because of that i usually just forget they exist but i totally shipped them while i was reading it and i'm honestly really curious if i'm the only one

Oh yes! For the half of it, though, i was like "oh no no no, Isaak, darling, don't fall, it can't end good for you. But then they both seemed so earnest, and i was lowkey rooting for them 😭💔

I realised I've never posted this so here's a sketch from last month of helnik cuddling🌸

saw a poll about dry/humid heat and like OBVIOUSLY everyone preferred dry heat but. would love to know what everyone considers to be “too hot”

me personally it’s a hard cutoff at 75°F. don’t need anything more than that thank you 🫶🫶🫶

HELLO???