I’ve drafted some notes around limitations and missing Nostr REQ query features as defined in NIP-01. Goal is to collect thoughts, but perhaps help understand what a more flexible approach could look to support.

I think the areas I’d like to consider are

* relay performance

* data usage / bandwidth

* sane flexibility (not looking for direct SQL support)

* aggregated stats (clients don’t need 1,000 follower events, just give a summation)

Ideas and thoughts welcome. Other use cases and limitations also welcome to add.

https://gist.github.com/blakejakopovic/a5f46cb42eb7da2c22c8af620ac37bb7

Do you support a pre-paid credits style drawn down accounting system?

Basically users prepay for N credits and then when they trigger paid actions, it checks if they have M credit remaining (pending hold), then performs action and then finalises deduction. Should support refunds perhaps, or at least cancel pending hold.

Yep. I’ve seen this in my data as well. Consolidation around stable daily active pubkeys, which is still double what it was a couple months ago, but perhaps fewer new faces.

I don’t know if it is content related, not understanding relays, global spam issues, not understanding keys or how to use browser extensions, unable to find people to follow, maybe country app bans played a part, etc. Unable to find trends or news content easily. Maybe slow apps.

Collectively I think we need to try understand first experiences better. Maybe clients can ask in-app? At the same time, growth comes in spurts too.

Breaking: AI to replace stagnant, money hungry, self-serving, useless, sustainability front-organisations.

I think we’ve just replaced Greenpeace with something actually valuable with 100 words or less.

GPT4, create an honest greenpeace replacement website where the content can actually help improve Earth’s health and educate people in sustainability.

Any Nostr devs and users around the Balkans?

Does it come with a lifetime of free coffee?

Don’t forget the chillies 🌶️

Greenpeace and a few other orgs are effectively shock-media companies. They make outrageous claims for attention, largely misrepresentation targeted for a money grab for them.

Having independent watchdog organisations to call out bad practices and environmental impact is great and needed - but their values are like PETA which is “our way or go fuck yourself” and “let’s fund ourselves with a new twisted media story every six months”.

And maybe option for auto-play media. I don’t get motion sickness, but for some reason the demo video made me nauseous.

I find it disorientating. I like the idea, but I always tend toward the more compact themes. It works nice for images, the mix with text makes it hard to follow.

Hopefully Damus and mobile apps can support selection between view modes.

GM ☀️

Here is a post about the beta version, since this earlier post is pretty active too. #[2]

#[3]

I have full text search setup in Postgres, so I kind of left ES behind. I have a stream worker that can populate it easy enough. It’s just not running.

I search a lot, but mostly SQL ops to detect and filter/purge spam. Last two weeks I’ve had near zero spam or bloat issues.. glad to not be wasting my time on that.

This is freedom and Nostr winning. The more specialist content we bring to the platform, the more valuable.

Custom relay and aggregator/indexer. All in rust. Web stuff is Ruby. With Prometheus and grafana. Postgres and Redis. Experimenting with Cassandra, rabbit, elastic search at times.

I’ve built an event based infrastructure with streams and effectively micro services - largely NIP specific or focused, and for delayed/deferred processing to support mass scaling.

Cool. The more utilities and tooling we build, the more devs learn and the more we can refine Nostr client products and user experiences.

Also, likely worth adding your thoughts here. On Nostr I’d had more positive support, but on GitHub it’s less encouraging. https://github.com/nostr-protocol/nips/issues/340