Avatar
j
2590201e2919a8aa6568c88900192aa54ef00e6c0974a5b0432f52614a841ec8
keep nostr weird

Lmao, does anyone have a recording of this?

You have to check if a Maybe is a Some or a None in every language. Go is no different from rust here.

The point about about multiple mutable references is good though, I like that about rust I guess. But it's better to just use channels send immutable values.

The best go slogan is: don't communicate by sharing memory; share memory by communicating!

That's just factually wrong.

Go ahead and search on github for go repos that use the unsafe package. Very rare.

Basically same as Maybe in Haskell. You can unwrap a maniac or check if it's nil first. There is no issue. Nil pointers are only bad when a language is not memory safe, go is.

Replying to Avatar Dan Gould

go to https://bitgould.com/.well-known/nostr.json and tell me why my NIP 5 is broken 😅

It's broken because you used a bech32 encoded public key "npub1..."

That's good for humans but for protocol stuff on nostr you have to decode it then encode it to hex.

🤯

TIL openbsd devs have an independent implementation of git with a minimalist interface and no feature bloat

gameoftrees.org

Nostr, the web 2.0

- the antihashed podcast

Lol savage

If you don't trust the miners then bip300 should be the least of your worries

The hashrate escrow is the best possible federation: custodians are the miners which can be anon without having to worry about Sybil attacks and are dynamically rotated so only the members most aligned with the network at any time are in charge of the funds