it's pretty weird to take a break from scythe-mowing like i'm a 1600s peasant to check in on my fleet of futuristic AIs like its the 2100s (and post about it on a freedom comms protocol). the present is much stranger and more wonderful than i ever imagined the future being, in the past.

Do you wish your favorite open source nostr client had a certain feature or would fix a long-standing bug or UX issue? Let's discuss that here - submit your ideas or chime in on others - and let's create a

Grantless

Grantless — The Invisible Handout

Crowdfunded grants for open-source work, on Catallax. A permissionless, pleb-funded grant ecosystem on Nostr.

crowdfund for that work and "friendly pressure" the relevant devs to implement the change to claim the bounty! I'll start: I'd appreciate if @Jumble supported NIP-51 lists of all kinds :)

plausible deniability server/relay + client: - when you post to the server, you specify a symmetric encryption key, using that key to encrypt the content. but you don't tell the server the key - any client displaying the content should take a key as an argument (url param would make for easy sharing), and attempt to decrypt the cyphertext clientside using said key - if you provide the correct key, you can view the cleartext in the client. the server never knows what data it's storing - but for users, sharing the clear version is trivial: just share a url that includes the key. - extra protection: the server/relay doesn't accept any cleartext content, so there's no moderation burden. @SuiGenerisJohn does this get around the server owner's responsibilities re: content and liability?

This guy is a treasure View quoted note →