just because you can rationalize it doesnt mean its right

i think nostr needs multi author events. one event belonging to multiple authors. this also simplifies transition to a new pubkey. and also allows later quantum secure pubkey transitions as well. we need a "nostr event v2". v2 should be able to be represented by v1 events as well in an indexable way. but clients verify it. this way relays already have the data available and can switch to the v2 later when enough clients are using it. and they feel like it. when my client has enough users i will support this "soft fork", or "progressive enhancement", what ever you wanna call it. this doesnt try to link two pubkeys to eachother. it just makes the events owned by two different authors. people can migrate their replaceable events at once as well. im not gonna get into details rn, but i thought about this a lot, and all kinds of edge cases. i think its doable easily, without creating a "nostr 2"

hopefully my mining rig will pass customs. then if i can successfully get it, i will buy more.

X has more bots than nostr

is there a nip, that allows multiple authors to sign any event? not multisig. multiple authors.

who was that??? View quoted note →

future is

nstr.app — a nostr app

A nostr app.

can somebody send me some XBT on purpose? bc1qshz088gg8cd8nl5t0sp3svasvmd243h4sq4fud

me talking about my work friend/boss who killed himself with a shotgun

aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa a aa a a aa a a aaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa a a aa aaa aaa a a aa a a a a a aa a a a a a a aa a a a a a a a a a a a a a a a aa a aaa a aa a aaaa aaa aaa a a aa a a aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa a aa a aa a aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaa a a a a a a aaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaa a a a aaaaaaaaaaaaaa aa aaaaaaaaaaaaaaaa aa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aa a a a aaaaaaaaaaaaa a !

who is making the nostr browser?

should i sell my XBT to buy an XBT miner? i have to sell it because customs requires the card payment log. i wanna buy a miner.

look at this fucking shit View quoted note →

even if my client doesnt know about the event kind, it still renders it even understands its naddr and watches updates. look at this shit

i used to draw a little

this week until weekend, im rewriting my nostr client from scratch. since i know the final logic and shape i have now, im gonna impl it better, and fix some of the issues along the way.

nstr.app — a nostr app

A nostr app.

opening discord again years later feels weird

i have a clear picture now. for future of zaps. give me 2 weeks. i will be back.

ark with lightning can replace custodial lightning. it can be a nice way to let new users receive zaps without opening their own lightning channel yet.

fuck it we will test it live