Let’s see Paul Allen’s Nostr

Too much ego today

Happy National Dollar Day! 🥳💸🔥

Governments can never be transparent, because if we all saw what the tax money is wasted on we’d rev… erm, do nothing. 😞 nostr:note10g4j2vv98v97vu8mj9942rrcgc6rer3h8xudz3gc3s0aj5mute6qn8e9yj

On my morning walk I had a realization. In a way we skipped over succeeding at the Turing test.

In the past attempts at the test could be spotted because if you asked the right question it was clear it was dumber than a person.

Today gpt-4 still fails if you are astute. The give away now is that it is too smart.

Here's my late night post becuz I can't sleep.

Guess my favourite computer game of all time and I'll Zap you! Go! One guess only! 🤪😄😏 Oh and I played it as the video game too.

You know very well that without a merge in the reference implementation the patch is not effective.

On the one hand, the developers who have the keys to the deposit have too much power, but on the other, I don't even dare to imagine what Bitcoin could look like if everyone could add code as they wish.

I just don't see how to decentralize Bitcoin development while maintaining a reference implementation. nostr:note1d2ngryu0n5du0mj7lg9ttrnpu9tmxl20rwra8dujvhwpyz0kk5qshf2m4f

I thought this is how standards are started and evolved? isn't that also how nostr does things?

Where do we not care about specs? I think we very much push for specs and interoperability in all that we do. We might make mistakes, like here. but please let us know where things can be done better.

And the URI had the problem, that an implementation was proposed, then in the NIP it was decided to change the URL, but Amethyst had implemented it so there was a grace period to change it.

How should we have handled it better?

please let us know where we do not care about specs and where we can do better. This is actually very important to me.

and where did we make a proprietary "login with alby" button?

Whomp whomp….

LK99 Not a superconductor…

#LearnFedimint

You can! :)

each data string of eCash is signed by the #fedimint. On your client, you'll have the pubkey of the fedimint. You can use the pubkey to validate the signed value, X, and other data (need to learn what is encoded!) of the ecash note. Then take the notes to the mint when you're online to redeem them for new ones of the same value X (aka reissue) so now only you know the secret ecash data string for value X.

Since it's just data that can be printed on paper, you only need to verify a signature, which can be done offline with minimal compute requirements (mobile phones).

This does create a race condition with the sender, because if they redeem it first, then the receiver can lose it. I think client reputation and federation moderation will help deter this attack since the tradeoffs for custody would be of proportionate to value transacted or phsyically close enough for "proof of punch".

I still won’t forgive y’all for when Lyn Alden came to Nostr and just said like “hello world” and everyone was like “YES LYN I WANT TO SAY HEY TO YOU FIRST WELCOME WELCOME” and I was like “we don’t know that’s Lyn, no npub cross post or NIP-05, proceed with caution” and then everyone was like on my dick beatin my ass and someone literally said “who cares, if they aren’t lyn and start abusing the namesake then we’ll know” FUCK Y’ALL. Yeah it ended up being Lyn but 🖕🖕🖕

DTVINO

That stands for “Don’t Trust Verify In Name Only”

🖕🖕🖕🖕🖕🖕🖕🖕🖕🖕