sup cutie

people have pointed out before that zuko probably didn't actually know any of the gaang's names before joining their group. according to the data i've collected, it is unclear as to whether zuko knew any of their names before "the boiling rock," in which he addresses sokka by name multiple times. at no point in the show does he refer to toph, suki, or momo by name.

i find it particularly funny that zuko only seems to refer to katara by name after sokka says her name during their conversation in his tent; the transcript for "the southern raiders" reads as follows:

Sokka: So what's on your mind?

Zuko: Your sister. She hates me! And I don't know why, but I do care what she thinks of me.

Sokka: Nah, she doesn't hate you. Katara doesn't hate anyone. Except maybe some people in the Fire Nation. No, I mean, uh, not people who are good, but used to be bad. I mean, bad people. Fire Nation people who are still bad, who've never been good and probably won't be, ever!

Zuko: Stop. Okay, listen. I know this may seem out of nowhere, but I want you to tell me what happened to your mother.

Sokka: What? Why would you want to know that?

Zuko: Katara mentioned it before when we were imprisoned together in Ba Sing Se, and again just now when she was yelling at me.

we can thus assume that zuko went into this conversation knowing katara only as "[sokka's] sister," heard sokka refer to someone named "katara," and finally connected the dots.

Thank you to @fancycake for their hilarious idea that I had to draw

Source

oh this is so peak... gracerocky inspiring a whole renaissance is crazy... they've introduced the concept of soulmates to eridian society and the romance scene will never be the same.

your eridian situationship can't text you back, but savior grace kept tracking the location of savior rocky's ship long after they parted and it's the only reason they managed to find each other again in the big nothing... okay...

it installs a user-login-time "startup" executable that ignores any windows directives to disable it on startup. doing so only removes the even-more-malicious taskbar-icon-creating advertisement-notification-creating process. no matter what you do, the sleeper "updater" process starts when you log in, and runs perpetually

it sends & receives encrypted network traffic both periodically and non-periodically. both are bad, both are suspicious, and a program doing both is more suspicious than the sum of their parts. and to boot: acrobat will polymorphically edit its code after such network activity

this isn't new: it has always done this. now, it does not even do the thing it is meant to: provide a way to interact with documents, which is amongst the very first features computers were built to provide. you can merely open PDFs and read some of their content in the narrow space between the requests for adobe to give them your money, and interface for features you cannot use (because you don't) or do not, have not, and will not ever need

adobe and microsoft would very much like the user's cultural norms around computers to allow for advertisement built into the local software and even operating system itself. the web being 100% advertisements was not enough! sure enough, acrobat will hijack the windows notifications system thing to give you the 2026 equivalent of pop-ups

i don't really know enough about windows software equivalents, so i'll paypal $20 to the first person that reblogs this with a list of 3-5 PDF reader/editor/etc acrobat equivalents that meet the following criteria:

open source, locally-built executables must match checksum of prebuilt distributed executable

no paid features/premium version/subscription/whatever

not a toy hobby project thing, must be windows-users-proof

KDE Okular: is a decent viewer and can also do basic annotations, and is so not-a-toy that you can even download it on the Windows app store.