226 Followers
168 Following
4.3K Posts

Little goblin with catears.

Unfinished projects, complaining about computers, reinventing the wheel (badly), has not fully read any docs since 2015.

Proud bot parent to two failsons:
https://infosec.exchange/@enojifier_bot (WIP)
https://infosec.exchange/@dreizehnzwoelf_bot

All my opinions are that of my employer but they don't know it yet & I am not telling you were I work. Apropos: If you need some idiot to kick computers for purposes of making them secure hmu, this job fucking sucks (vulnerability management, automation/engineering for your soc/isrt, ...).

PFP by a lizard that I am pretty sure transitioned at some point but I kinda lost contact with around the same time so I might only know their deadname & at this point it's too awkward to seek them out & ask. So instead I am going to credit them by their last discord handle I am aware of: fuck, md

LanguagesGerman, English
Pronomen (πŸ‡©πŸ‡ͺ)egal
Pronouns (πŸ‡¬πŸ‡§/πŸ‡ΊπŸ‡Έ)name reference > they/it > whatever
Your password must contain at least one character flaw that you have long recognized within yourself, but that you would never admit to anyone--not your therapist, your spouse, nor your most trusted friend. It is the dark secret shame that you must bear alone.
Come on FBI! Seriously? Me?
I know that the linkedin thing is philosophically bad or whatever, but I also cannot imagine the level of rock bottom I would have to hit to feel strongly about LinkedIn's browser extensions policy.
New #artemis II moon pic just came in
Oh, also still taking recommendation/proposals for the pfp of @enojifier_bot
Okkeeeeeh, taking @enojifier_bot live now. Lets see when the mods add a new emoji so we can see in in effect 

From the perspective of the sending instance:

[user@machine ~]$ curl -s -H "Authorization: Bearer [removed]" https://mastodon.social/api/v1/statuses/116375447592202847 | jq ".id, .url, .uri, .in_reply_to_id"
"116375447592202847"
"https://mastodon.social/@nyanbinary_alt/116375447592202847"
"https://mastodon.social/ap/users/116365607147038888/statuses/116375447592202847"
"116375447572552853"

From the perspective of the receiving instance:

[user@machine ~]$ curl -s -H "Authorization: Bearer [removed]" https://infosec.exchange/api/v1/statuses/116375447686132383 | jq ".id, .url, .uri, .in_reply_to_id"
"116375447686132383"
"https://mastodon.social/@nyanbinary_alt/116375447592202847"
"https://mastodon.social/ap/users/116365607147038888/statuses/116375447592202847"
null

(delete & redraft because jfc, I forgot to redact a token [already rotated] and user/machine name...)

RE: https://infosec.exchange/@nyanbinary/116367575892180483

Looks like I am breaking things accidentally now?  

Quick-firing the posts seems to have broken threading in one test? Showing up correctly threaded on the sending instance but unthreaded here 

Huh, I didnt except that "tmux inside tmux" works that smoothly