https://grimoire2.netlify.app/ will probably live for a long time, in case the original Grimoire dies.

I'm against zaps, I'm against extending, I'm against assets, I'm against sovereign, but I think you should be able to send tips in any way you want.

The most recent #pyramid version has things that you may have not heard about: - /database page for direct database querying for the admins, along with a button to delete events arbitrarily - same thing on the blossom side, admins can micromanage and delete things (previously users could already manage their own blobs) - I have probably mentioned this already, but we have tiered limits for blossom uploads, like you can say "1000/500/200" so people on tier 1 (right below the admins) get 1000MB, people on tier 2 get 500 and people on tier 4 get nothing - pomegranate operator service (be a partial key custodian for your community) - a way to request access -- this has to be enabled, but then anyone can request to be invited by anyone else that is already a member on the relay (and has invites available) from the home page, and people can accept or reject also from there - the relay itself publishes a kind 0 for its own key (I don't remember why this was necessary, but it will look nicer when browsing special relay-made events from other clients) - an nsite gateway for assets and manifests published on pyramid, see https://.nsite.pyramid.fiatjaf.com/ for example - I have probably mentioned this already, but there is a /clients page that lists all clients connected to the relay, for admins only Join us at https://web.nostrord.com/?relay=pyramid.fiatjaf.com&group=Tnq7x2ZTgrPZWFrC, get it from https://github.com/fiatjaf/pyramid and be forever happy

I think any format will go, including images. An nsite is fully published to Blossom already, that's how it works: publish all assets to blossom, then publish an event pointing paths to hashes so the site can be rendered by a gateway later.

The most recent #nak version has things that you may have not heard about: - "nak nsite" command for downloading and publishing nsites from a directory - most commands now take --sec, --auth, --force-pre-auth flags so you can AUTH when publishing an nsite, for example, and the syntax etc is all shared (please report bugs) - "nak nip" command for displaying NIP text, pretty printed - "nak kind" command for displaying information and schema about a kind, with data sourced from https://github.com/nostr-protocol/registry-of-kinds/ (please contribute) - when specifying a kind in any command you can pass a string and it will match a kind number, try for example "nak req -k 'fav relays' -a [email protected] --outbox" - a bunch of fixes, most by , and some minor flags added here and there Download at https://github.com/fiatjaf/nak/releases/tag/v0.19.13

Does it still happen if you restart Lantern? What if you use another bunker?

https://pomegranate-admin.netlify.app/

Writing specs with uppercase words SHOULD/MUST/MAY is stupid.

Doctored screenshot.

I still remember that day. I said to myself I had to release something, no matter how incomplete, before Christmas, because that would increase the odds of people being bored at their holidays and giving it a try, otherwise I would have probably delayed it for many more months like I had already been doing for a long time. The reception was much better than I expected, except for the fact that a bunch of French people said the name had bad connotations. This was sad because it was such a good name.

I just searched YouTube to see if there was a live stream of the event and the 3 first results were fake videos of Michael Saylor at the stage talking about a QR code that I had to scan now to learn more about some opportunity.

There should be a Nostr newsletter that only talked about the drama and fights happening here.

I've used 'nak key combine ' to confirm that is really the merge of and and you should do that too!

From a quick glance at the code you have a set of hardcoded relays that the app uses at all times and at no point you try to fetch outbox relays of users or their list of DM relays. There is another "pool" that the app maintains with other relays. I don't know where those come from, but apparently you blast every DM to all these relays too?

I think Nostr would be probably 200% better if we had someone to test apps reliably. I'm not talking about a "QA engineer" whatever, just someone that isn't a programmer but can install things, click buttons and report bugs. I have the impression that this is a role that died in the industry of software development, but it is much needed now, and much more in the age of AI code.

What Blossom server is that and how are you connecting? You probably have to tell them to update their NIP-46 implementation.

Just a clarification: what I meant was that OpenSats could be governed by futarchy, not that Nostr could be governed by OpenSats.