gravis called this an ISO standard shitpost once

fork() me

and then exec() me

until i get my

SAT-3 fact proof

Joy!peffpwpc

@mod tetris is so unrealistic

"alex what" alex what

ballistics dummy thick

schockingly, eyem quoi-yout

@multioculate tape head cleaners iykwim

@gabrilend you very nearly caught a block, please reconsider your approach

@gabrilend sighing very heavily as we have to explain that you're reading a fair bit of stuff we didnt say into what we did say

@ireneista we would say that is definitely... enciphered.

you can't have sexual reproduction without transness. sorry. we actually made that a rule last time we were out there mucking with the fabric of reality.

the reason we find so much power in things like NTSC artifact color is that these things simply arise as a consequence of their nature

the way we've made peace with the notion of people deadset on enacting a pogrom on us (our ancestral trauma says: "again?") is that even if they succeed, nature abhors a binary and we will inevitably re-emerge from first principles

the way we've made peace with the notion of people deadset on enacting a pogrom on us (our ancestral trauma says: "again?") is that even if they succeed, nature abhors a binary and we will inevitably re-emerge from first principles

@grumpybozo in our environment it's easy, the frontend passes the IP along out-of-band, but the target service fails to preserve the data

@munin yes, which is something we've been trying to correct, by wrapping the message itself with another layer of MIME, such that the sibling attachment contains the envelope data

@munin "there is, but they don't use it"

@munin because they do not store the envelope data, thus it evaporates once it leaves our system. we have been trying to get them to do "not that" since day 1

me @ coworkers: stop trying to parse headers to get info that comes from the envelope

coworker: i am parsing the Received header to find original source ip, is this ok?