Avatar
fiatjaf
3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d
~

Blue Ridge Youth Soccer Association.

https://www.brysa.org/

They'll have this logo: https://cryptologos.cc/logos/versions/bitcoin-btc-logo-full.svg?v=024 on their jerseys.

Idk about tournament, but all the teams will just be rocking the Bitcoin logo on their jerseys.

Waiting for confirmation that my sponsorship is accepted.

Players born in 2019? What!

Where? What do you mean? They will have "Bitcoin" on their shirts? If we sponsor more that will make it so the tournament will be all Bitcoin?

In my experience the web clients all more-or-less suck. I don't know how people are able to use them every day.

Try https://github.com/mikedilger/gossip

What PC client?

By the way, I don't think NIP-65 is a solution to anything or even required to solve anything. It is just one nice addition to the model. It worked already before without that, relying on NIP-05 relay hints, nprofile codes, relay hints in events and keeping track of things.

Watch this relatively old video, it is very enlightening: https://mikedilger.com/gossip-relay-model.mp4

Many years ago Jeff Atwood wrote an article about how phones and tablets' big innovation was that they were "instant-on" devices that you could just tap and do something with at anytime.

Today my phone takes at least 60 seconds to be fully operational if it is turned off. My desktop just went from turned off from having a web browser operational in 20 seconds. But even if you count the phone in standby mode as "off" and you can turn it on by just unlocking it, it still takes 10+ seconds just to open the browser, then the time it takes for you to type something and the relative slownless of opening any webpage makes it worse than the desktop.

This is the terrible Nostr experience that is fixed by the Gossip model. Listen to the Mike Dilger episode at https://nostrovia.org/.

What do you do with the sheep? How many do you have, counting the 45 lost ones?

Última flor do Lácio, inculta e bela

The problem is that you can issue a key, do nasty things with it yourself, then later claim it was revoked so it wasn't you and others shouldn't have believed in it -- but they did believe because they didn't see the revocation -- and there is no way to solve this ambiguity.

It makes no sense because 2FA is just a second password you give to a centralized entity.

But it is an interesting idea if you think you could have a key that is split in two and a server keeps half and only signs your events once you provide 2FA auth to it.