If you have good and strong headphones you can listen to all my criticisms of Lightning condensed in 1 hour:

This should work on any client, by the way, you can just type the command manually and if it starts with the correct "/trianglize@nostr:npub1..." syntax that should be enough. View quoted note →

Slash commands support is live at

Hallway

Based on this very simple and good spec:

GitHub

nips/CD.md at 68229740b91215bf76e74ebc916ff6c96cc7d231 · coracle-social/nips

Nostr Implementation Possibilities. Contribute to coracle-social/nips development by creating an account on GitHub.

there's an "orphan blobs" view on #pyramid now: So if you are, for example, publishing a bunch of nsites and you want to delete the old files not referenced by the latest version, that will let you do it.

On #pyramid you can import a NIP-29 group:

Many NIP-29 groups in the same stream of messages:

After 16 years I've decided that petnames are actually good.

I know everybody loves this topic, so I wrote a bunch of posts about the ATProto design in this thread: View quoted note →

I hadn't understood Bluesky enough when I wrote this: View article → My error (in the third point) was thinking that their goal was to make something actually decentralized like Nostr. For some reason I couldn't conceive the possibility that they were not trying to achieve this. But they were. They were never interested in actual decentralization, probably because the idea that it was possible had never occurred to them. They're stuck in thinking that you either have a flat p2p architecture (which leads to problems of incentives, spam, becoming a "nazi bar" and whatnot) or you have a system in which a platform controls everything and the best you can do is migrate. View quoted note →

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.