I think smarter clients one day that use a combo of standard and smart relays that can dedup events, cache and compress, download headers only, filter, etc. etc. but still auto switch to real relays for resilience.. maybe ‘smart relay’ features can all be done via optional NIPs.
Anyone is free to change my mind, but I strongly believe that nostrgram is by far the best nostr web client out there. I’m putting my sats where my mouth is and happily covering the first 210k sats donated to #[0]
It’s a huge amount for me, but it’s something I managed to gather through my https://bitcal.21ideas.org/about/ , https://nostr.21ideas.org/ , https://www.21ideas.org/ projects…
I’m using nostrgram daily and it’s been nothing but exceptional.. so here we go.
Hope this will bootstrap the the wave of appreciation towards the work behind the project.
P.S. it’s quite late here, so I might cover the invoices in a while. Also make sure to provide proof of support.
h/t #[1]
This is an awesome idea for a new crowd funding model. Person believes and something and funds it. Then others back fill that funding. Any overfill goes to the funding target. A great way to build initial momentum and awareness for a campaign. Should be relatively simple for someone to build an app for this on top of nostr. Couple of weeks work for something polished..
That’s awesome! You are a legend LL..
With Nostr we’re going to see an explosion of clients creating Bip340 addresses. There are some steps involved to creating technically valid ‘compressed’ public keys. What are the chances all clients will get this right..? Those that use public libs will probably be safe. We’ll all need to decide what to do with buggy clients that get their address gens wrong..
Yeah, will be a challenge with the relay architecture. Only solution will be big centralised harvesting servers (clients) to collate their ‘best picture’ for each user and then provide stats. And this will not solve ‘stealth followers’ when they get built into some clients.
These long form posts on Nostr are jarring… I think Damus and other clients will need to summarise posts in the timeline soon. Click to expand..
Hard to see how Nostr doesn’t become the biggest network in the next 3-5 years..
Nostr so easy to implement. Hats off to protocol simplicity.. But Schnorr signing in C# is a fucking nightmare…
I don’t think most realise how much better Nostr clients will be than TradSocial clients in a year or two. Deving them on an open protocol will far outpace proprietary development, which has constrained resources and political/commercial overrides. Only challenge, the app stores. But there are ways around that long term..
Motivated dev syndrome.. bet your brain even created a snippet of code while you slept..
Maybe a notification counter above to the right of the feed header eg. ‘posts’..? It can just increment as the come in. Tapping the header jumps to top and clears the counter..
build 3 is out!
- No more timeline jumping around!
- Improved scroll performance a bit
- Added Posts or Post & Replies selector to Profile
Full changelog:
https://github.com/damus-io/damus/blob/master/CHANGELOG.md#110-3---2023-02-20
Assume a few weeks for App Store updates? Does it have to go through their app approvals each time?
This.. Can’t say I’ve ever learnt anything in a space..
Always struggles with fingers..
