Ok, I'd call it progress.

nostr:nevent1qqsq07wutczxa9hnypqx2ap42xay2pq4tqew0zwprs6j7wtc3ppe2mspz00ct

Sitting here with a once-a-year bad sniffles I wonder if people who disinfect and wear masks actually manage to make a dent in their life expectancy or quality of life. For the latter it looks like a big negative.

"disinfect" with a spatula.

After that guy with leprosy hands it back to me maybe.

yes, makes more sense.

Of course, on nip04 I can also reference all other nostr resources in a decentralized way, without picking a client.

Problems are:

* Identity: We need to make it easy to find the right fiatjaf on that other chat app

* Privacy: Many chat apps require phone number

* Inertia: nip04 is expected to be a way to chat with people, so people default to it. You would have to run a reply-bot to push people to whatever other channel you prefer and you have to get all clients on board to retire nip04. I know you try but it's impossible. Even you as our CEO can't do that.

* Integration: I can beautifully mention nostr:npub1504jj42t6flu5l6n7e389e9mt8gxduhnzuyv7dq4gr95w20mmpqscx0cg0 in nip04 but not on Telegram

I think we would need first a plan and then a shame campaign to kill nip04 but I don't see what that plan could look like. It would have to be something better than nip04 and quite frankly I don't see Telegram and Signal as better. By knowing that who chats with whom when being public knowledge, people don't fall for the illusion of this being private as they do with TG and Signal, while there it's just some privileged people that still know all that meta data.

Consider each user who does display badges as a no-vote, please.

No. Why?

I was like "where is Antarctica?" but you have a point. :D

For my described use case of retiring an account, back-dating would be a problem, so yes, ots would be good. How available is ots? Are there relays that ots everything yet?

Idea: NIP-Infinity

Problem: If my keys get compromised, whoever has them, can delete all or some of my messages.

Solution: Exempt one (non-replaceable) kind from deletion.

"Delete" is a poorly supported feature so far and there is much confusion about how deleting an event ID for a replaceable event would even work. Would it revert the changes, reviving the old version? Anyway, relays are certainly ahead of clients in this field and exempting one kind, maybe kind 800 like 8∞ would be rather trivial.

Clients could treat it like a kind-1 and later mark it as special.

As many users right now are determined to never delete their messages anyway, people would probably jump at this extra visibility if it had no downside to using it. Should it be a signalling mechanism for account termination or are there other use cases, too? Certainly accounts should be able to author more than one of these, as hackers could, too.

Well, you certainly did not miss Ledger committing suicide.

This foto looks like a drone picture. Or you were up some really steep mountain.

I use Snort.social and if there's issues, iris.to or coracle.social.

In my rotation, too.

I meant the browser on the PC as the browser on mobile does not support nip07

nostrgram is stuck in the past for me :( and nostr:npub1t9a59hjk48svr8hz6rx727ta6kx53n5d6fw8x26vsua0zytpl87sa6h4uw disappeared without a trace.

gossip is not for the browser. Switching between them, I opt for using nip7 extension and browser clients, only.

That's my take, too but which one is your preferred one?

Which nostr client is everyone using these days on PC/Browser?