silly[bad, don't do this] idea: tor hsdir block device

you're given around 50kb of data per descriptor, and the interior is encrypted so it can't be checked for validity. define some mapping from disk id, block id into a key then write the data there. you even have the ability to change a block

(side note: the design of "encrypt all the data with the public key" is really nice. doesn't hurt UX on lookup at all since you'd have the key anyways, and means no one can just discover .onion services that are uploaded to them.

"encrypt all data with a key determined by what a client would know anyways" is cool design (i.e. if you have a service that lets you look up user profiles from a username, instead of sending the username to the server, use hash1(username) as the lookup key, and hash2(username) as an encryption key. if username isn't high entropy that's not strong protection, but prevents just walking a whole ass user directory, at least.)

fun ultrakill movement tech quiz:

(first screenshot is to show the path better, second one (plus walls) is what i'd actually do in a level)

how do you get from one end to the other without getting hit by the lava

latest game changer (S08E01) is so fucking good holy shit

up there with 1 year later as an incredible intro to the season

it's really funny how many standards are informally just named after the body that standardised it

yeah give me an ISO film speed and an ISO file and an ISO container and a DIN connector and a DIN film speed

(AO3 tag search, count is the number of uses)

Freeform: Robot/Human Relationships ‎(9559)
Freeform: Robot/Robot Relationships ‎(20)

fucked up. granted a lot of this is just untagged stuff but still.

gotta do my part i guess

florp: a privacy preserving, offline first, powerful, easy to use, open source, customisable, material design, quick, ad-free.

i don't mean to be too mean about it but like. cmon. tell me the attributes of your program that can't be inferred from the fact that it's on a foss app repository