New #pyramid release with absolutely earth-shattering new features: - ephemeral events don't get accepted from anyone by default anymore (you have to explicitly allow them and whitelist the kinds now) so your relay won't overheat from bitchat DDoS (plus other fixes that bring CPU usage lower) - NIP-29 has per-group NIP-50-powered fulltext search now, with automatic language detection based on the first messages sent to the group - built-in video livestreaming server compatible with OBS and zapstream/shosho/etc (and all the other clients that display such streams of course): - a nicer way of defining the list of kinds you accept, by making it a list of deltas from the default kinds (instead of having to list everything by hand): - more stats added to the system view: - online count on the landing page, highlighting who is online (for now this is based on public information only, i.e. only people who published events in the past 10 minutes, same as how Wisp does it): Available for download at

GitHub

Releases · fiatjaf/pyramid

a wondrous furnace of communityzenship backed by a dynamic ladder of socialhood - fiatjaf/pyramid

(or do the easy cheap-VPS setup:

GitHub

GitHub - fiatjaf/pyramid: a wondrous furnace of communityzenship backed by a dynamic ladder of socialhood

a wondrous furnace of communityzenship backed by a dynamic ladder of socialhood - fiatjaf/pyramid

Please report bugs here in the comments or in our NIP-29 group. View quoted note →

What if we had a relay where new people could manually submit content to and pay a "curation fee", then some smart humans would pocket the fee and manually vet each submission and only allow in those that were deemed high-signal? Would you browse that relay in order to discover new high-signal content and new people to follow? Would you put it in your default relay feeds list or somewhere like that? @Cody @utxo the webmaster 🧑‍💻 @Vitor Pamplona @Fabian @YakiHonne Please let me know if you have a better idea. View quoted note →

I got my first feature implemented: https://github.com/CodyTseng/jumble-ouro/issues/10 View quoted note →

How is Nostr today? Did we get any new users? The last to join I think was @Havok two months ago.

This is a huge attack on your privacy, beware. View quoted note → Probably run by the Mossad.

Go on wss://subnet.relays.land/. What number do you get? Mine is 177.

Seeing how people add all sorts of URLs to their Damus relay lists I wonder if the best Nostr app UX isn't just a single big list of stuff. Do you want to write to a relay? Add it to your list. You want to read from a relay? Add it to your list. Do you want to browse a niche relay every now and them? Add it to your list. Want to upload stuff to a Blossom server? Add it to your list. Wanna bookmark a note? Add it to your list. Wanna join a NIP-29 group? Add it to your list. You're interested a hashtag? Add it to your list. Follow someone? Add to your list. Do you want to run custom spell or scroll? Add it to your list. Then the app understands everything you want from that and displays all the UI views you need.

Fevela

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

now has per-relay reply and reaction fetching: Can you think of a concrete use case for this that doesn't involve Marlon Brando?

I like that these guys are holding a sign that says "this is not AT". A clear message that they have evaluated the Bluesky protocol and decided, correctly, that Nostr is the real deal. View quoted note →

Thank you for coming to my stream:

Has every client stopped offering an option to use imgproxy for autoresizing images? I remember users could configure their own imgproxy on Snort, Iris and Coracle. Was that a bad idea because no one was using the option and if anyone used they would have a sitting duck imgproxy that anyone else could abuse? View quoted note → We could think of some solutions for community-hosted imgproxy servers that can be secure by having the client compute the required HMACs locally, or is this too ambitious? @hodlbod @utxo the webmaster 🧑‍💻 @Kieran @Vitor Pamplona @Sirius @Cody

Every part of Nostr that relies on hardcoded "big relays" is a bug and a gate to spamland waiting to be used. Spam gets to everything, whether it's malicious, automated spam or just someone handwriting something in the wrong place because they were confused. Even the relay reviews section isn't exempt:

I did an Android local relay app, it is called Topaz and you can download it here:

GitHub

Release v0.0.1 · fiatjaf/topaz

a nostr relay for android. Contribute to fiatjaf/topaz development by creating an account on GitHub.

Citrine is great, but we needed at least one other implementation, and Topaz is running Khatru underneath, which is cool.

The NIP-29 groups ecosystem is getting pretty good. View quoted note →

If we had infrastructure for curating entries, allowing groups to vote on proposed additions and deletions and simple UIs for viewing the list of all items in a list then it would be easy to get rid of the NIPs repository. It's sad that after so many years all we have are "feed" views. And GitHub continues to be a better platform for browsing and updating text lists of things. Notice that I'm not asking for much. We would also have to get rid of the NIP numbers, but we could just say "the longform NIP", "the badges NIP" etc and it wouldn't be hard to know what were people talking about. But if you're reading this and thinking about a complicated system with events being published with votes, proposals, lists of replaceable events with other lists inside or whatever absurdity, please stop. Just use a relay and normal events inside, add and delete. Custom write policies, standard Nostr read API. #pyramid has a moderated subrelay that is probably 25% there already. If you disagree please let me know. View quoted note →