Avatar
Carlito
000000001c5c45196786e79f83d21fe801549fdc98e2c26f96dcef068a5dbcd7
#Bitcoin freak. Anarchist without adjectives. Freedom maximalist. Bitcoin events in Brighton UK

Rumour had it that the reason my English teacher suddenly left was because he got sacked for being one!

Bija, the client I've been working on, allows you to set PoW limitations for notes and encrypted messages coming from anyone you don't follow. You can also configure PoW for notes and messages you create yourself.

Not sure TBH, just know it was common slang. Most often heard it referred to WRT a 'ten bob note' (no s, bob was both singular and plural.)

Craziest thing is to think there was a note worth 50p in todays money (1/20 of a £ but there were 12 pennies to a shilling) that you could buy a shit ton of groceries with!

👀

#[4] on #pyblock coming soon

#bija #nostr client

I see both as useful.

The way #[10] is doing it where it limits who can post to his relay makes sense to me, it's expensive for someone to keep spinning up new pow32 accounts everytime they're blocked for spamming so it means I can place a bit more trust on that relay not to have spammers on it.

People that don't have PoW keys can still use other relays and retrieve posts from that relay.

Was just thinking that detecting the pow for a vanity key is only equivalent to searching for the same of zeros if you know in advance which string was being searched for. Otherwise someone could search for many different words simultaneously and considerably increase their chances of hitting one.

Hex to bech32 is essentially base 16 to base 32, you just need to convert to the bech32 encoding (I think, I'm definitely not a cryptography expert though)

Ah, I see what you mean. I'm thinking there's as much chance of hitting any other character as there is a zero so to get a specific string of x chars would be the same work as getting x zeros. I might be wrong though.

You should be able to count the number of q's after npub1 to get an approximation I think

Problem with nostr clients using markdown for kind 1 events is that it can look quite ugly in clients that don't support it. Other clients automatically detect hyperlinks, images, etc. and render them in their own way.

Perhaps there should be some way to signal what kind of formatting is required, a 'formatting' tag for example.

In NIP01 it says that kind 1 events is only for plain text, whether markdown qualifies is debatable, I guess.