Replying to Avatar Sir Brian of London

I use all sorts of systems, how on earth would I know about them if I didn't?

I sure as shit wouldn't run my mouth off about stuff I hadn't at least written a few lines of code for.

Right now I provided anyone on Hive an easy way to get a NIP-05 address by putting their Nostr npub in their Hive profile.

I facilitate dozens of Lightning <> Hive transactions per day (hundreds if someone listens to one of the 7000 podcasts I provide Lightning services for.

I'm looking at NIP-57 but I can't get the main python library to work with 3.11 and it's taking too much of my time, I'll wait for someone to fix python-nostr.
Avatar
symbsrcool 2y ago

#[2]​ could the person being censored write their new relay address as an inscription on the blockchain? While maybe expensive in the future, that will never be censored right?

Reply to this note

Please Login to reply.

Discussion

Avatar
fiatjaf 2y ago

The problem is not for the information to exist, it is for it to be found.

Avatar
Sir Brian of London 2y ago

This is precisely the problem we're solving with Hive: a truly decentralised repository of any information (though heavily optimised for text) which is permissionless and decentralised.

Avatar
symbsrcool 2y ago

The only solution I’m thinking is convoluted but I’ll mention it anyway.

Before being censored, a person publishes a btc layer 1 public key via Nostr, and then Nostr clients (or separate tools) could scan the btc chain for any inscriptions from that public key as kind of a “ground truth” announcement from that person. So everyone/client goes to the same place (btc layer 1) to check for messages. Also could be used to make an announcement in the case that your nostr key becomes comprised too.