Why haven't you invited your friends and family to Nostr? I'm not saying you should do that at all, just curious about the reasons. Especially if you think there is possibly anything that we could do in order for you to do that.

Today I saw a comment from @𝐃𝐚𝐧𝐢𝐬𝐡 on

Zapstore

topaz — Zapstore

a very simple nostr relay for android

and I wanted to reply to it. The Zapstore website wanted me to sign in with an extension to do that, but I only have a bunker, so thought I would open the comment on

Fevela

A Nostr social client that give you back full control of your attention and time with an innovative interface

and reply from there. But the Zapstore website doesn't tell me the note id nor it gives me an nevent code, but it does gives me the author npub, so I tried to just visit that profile and wait for the note to be fetched, but I waited and it wasn't. Turns out the note wasn't in any of the (many) relays of @𝐃𝐚𝐧𝐢𝐬𝐡, as the command ~> nak req -k 1111 -a c45041618951bb6012ac23f5cdf3d740465f2d640be841fd9bb1d0733370cd3c --outbox --since yesterday --outbox didn't give me any results. So I guessed that it was only on wss://relay.zapstore.dev. So I ran this command: ~> nak req -k 1111 -a c45041618951bb6012ac23f5cdf3d740465f2d640be841fd9bb1d0733370cd3c --outbox --since yesterday relay.zapstore.dev | nak event --outbox And the note was automatically published to a bunch of places: publishing to nostr.hifish.org... failed: publish: context deadline exceeded publishing to nostr.wine... success. publishing to wot.nostr.net... success. publishing to purplepag.es... failed: msg: blocked: kind 1111 is not allowed publishing to inbox.relays.land... failed: msg: blocked: this event doesn't target any real users publishing to 0xprivacy.nostr1.com... failed: msg: auth-required: you must auth publishing to xmr.usenostr.org... failed: msg: blocked: you must pay admission fee. visit relay url on browser. publishing to relay.nostr.wf... success. publishing to relay.nostr.com.au... success. publishing to auth.nostr1.com... failed: msg: auth-required: you must auth publishing to jskitty.cat/nostr... success. publishing to relay.0xchat.com... success. publishing to premium.primal.net... success. publishing to relay.primal.net... success. publishing to relay.0xprivacy.online... failed: msg: auth-required: authenticate to publish events publishing to pyramid.fiatjaf.com/inbox... success. publishing to spatia-arcana.com/inbox... success. publishing to lightning.red/inbox... success. (Notice that it was also published to my inbox relays because it had a p-tag to me and nak detected it automatically.) This is a success story. Now I can finally respond.

tired of having to create a giant boilerplate with 42 javascript files and fight for hours against buggy build tools, unhappy linters and unresolved type-checkers, I started a collection of nostr web components that hopefully can be imported with just a script tag and used directly: <nostr-name pubkey="npub1..." />, for example, just displays the name of the referred pubkey.

gitworkshop - Decentralized Git

Decentralized GitHub alternative over Nostr for browsing repositories, managing issues, and collaborating on pull requests.

I'm not sure this will work or if they will be very useful. let me know if you have suggestions of other components to create.

Is there some organization keeping track of all the events in which people with many followers got banned from Twitter, YouTube etc?

I feel sad for all the people who recommend Bitcoin wallets and Nostr clients to friends and family very enthusiastically over the years only to have these things blow up in their faces every single time.