Nostr Web Client

https://git.mleku.dev/mleku/next.orly.dev/src/branch/main/docs/NIP-XX-CASHU-ACCESS-TOKENS.md

a cashu cryptography access control system that preserves anonymity completely if combined with use of tor.

using this first to make nip-46 possible without implicitly whitelisting the whole internet.

i think next step will be making a full free tier access control, need to get a token bucket to have fair but limited access without being on the whitelist, and average bandwidth limiting. so it will be freedumb if you use the things that speak CAT.

next after that i can see this being usable as a means to allowing tor-like relay routing and who cares about stupid tor, when nostr can route like that itself

Reply to this note

Please Login to reply.

Discussion

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 6d ago

to get this to be qualified for nip ratification, i will obviously need to persuade another client dev to include this signer connection, and ideally, get nostr:npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5 to include support for this extension in the amber. it means PWA apps with secure isolation on mobile devices. the relay UI will also make it simple to show a token to use for any client to access the bunker, and with that, the client automatically manages the token rollover as well, which allows the relay to limit breaches of access tokens.

so, yes, soon, for clients adopting this, relay.orly.dev will become a freedumb relay as well as privileged access for my follows.

since i have got some fat storage sorted out i'm going to migrate my relay to the fat storage, and integrate also the blossom access control into the free tier to permit some limited storage on blossom for clients that use this to access the relay, the free tier with CAT.