You found my personal account! If you know me from formal or irl spaces, you probably shouldn't look in here. Proceed at your own risk.
26 Clichéd transfem. Poly cuddle slut. Nonsexual little. Frequent meower. Kinky pervert. I pee myself a lot.
I contribute code somewhere, but I forgot where.
I like to be referred to as "kitten" or "little one". You can do that if you want and it'll make me happy but it's not a requirement (also don't use the latter in adult contexts)
formerly @me@elizabeth.cat
"a pervert who lost control over their life"
Location
Europe
Birthday
1999-03-02
Pronouns
they/them (EN)
Pronounsthey/them, although she/her when I don't feel like explaining
tbh the only option to save a hotel night and arrive on the day at a reasonable time kinda sucks. night train from Toulouse (and getting there at a reasonable time would be kind of a mess). it would go through lines I've never been to the next day though
I think I'll buy some more trackers for future tinkering/potential replacement. they're cheap af, 6€, and I don't want to risk the manufacturer changing the spec like they usually do, or stopping producing them
kitten playing with trackersokay, conclusions after some analysis between yesterday and today: - this must be a bug, and in L191 the inputData should be just symmetricKey, not self.symmetricKey - OpenHaystack built firmware with key derivation implemented, however: - it's located here - it's only for nrf52xxx devices (???) - it's a precompiled binary, with the source code not available in the repo's root firmwares folder (what the hell??) - the last point means, I'll need to write my own software modifying the one without key derivation. at least I can see how do they do the key derivation in the Swift code. or try to decompile the nrf52xxx binaries??
@blue1337blood@agowa338@binary_kitchen if anything, it would have been the other way around, considering I'm just casually tinkering around, and not like, assembling a whole talk about the topic
re: seems somewhat kinky@nekorvidae I'm afraid I seem to lack context for @SillyDemon's initial reference, but I'm happy that my post enabled this conversation
