Right now it only supports labels by the feed author. Hashtag filtering is built into Nostr. This thing could benefit from wider range of curation options, like curation by several people etc, if only anyone cared to use these and demand new features.
I don't think it uses your relays, which is a shame.
But also - IIRC the /used-apps section only shows apps remembered in this particular browser. I've stumbled upon this myself recently, will be fixing it all soon.
I don't think it uses your relays, which is a shame.
But also - IIRC the /used-apps section only shows apps remembered in this particular browser. I've stumbled upon this myself recently, will be fixing it all soon.
Introducing local event database in Spring browser v0.8.0!
So basically, Spring will now download all your and your followers' stuff and store it locally. On app restart it will sync and download only new events. The UI, feeds etc are mostly built using events from the local database.
https://void.cat/d/2XSotQbSzY7pXLtB1GtKKR.webp
Immediate benefits of this are:
- feeds load faster on app start
- less network traffic consumed
- less CPU wasted on signature verification
But the biggest wins that a local db enables will come later:
- offline mode
- fast search among local events
- local trust rank calculation
- local algorithms
- data backups and exports
- local relay for p2p? local AI models? who knows...
Also, imagine every app running inside Spring could have access to these local events... Apps would magically start working much faster, hopefully even offline.
Right now the database is very slow and inefficient and implemented in JS and occupies the UI thread, as soon as we figure out all the interfaces and features it needs to support we'll move it to the native code - nostrdb or strfry or maybe something homegrown.
Play Store: https://play.google.com/store/apps/details?id=com.nostr.universe
APK: https://github.com/nostrband/nostr-universe/releases/download/v0.8.0/spring-nostr-browser-v0.8.0.apk
Slowly moving there with Spring nostr:nevent1qqs2j3a77w97tm8tyk4jye6yuut9l0gf6peqsh5zfxku7d6n258n0lqpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygpn2m0xrvukg7f3e69jzs9jh2ur0cypps8029dmayk7qfyqgzutm5psgqqqqqqs64ycar
Labels are more scalable - you can have unlimited number of them, while list size is limited in practice to something like 2k values (that order of magnitude).
For curation labels are def better. You can even create a custom relay using your labels at feeds.nostr.band
Followers are your pubkey mentioned in their contact lists, you can have as many followers as there are pubkeys.
Your contact list is limited in size though, just like every other event kind, strfry has 128Kb max event size IIRC, others' may vary but there will be some limit no matter which relay. And the bigger the list, the more expensive it is to edit it, which makes increasing this limit not practical anyway.
Well that honor could be diluted by their ability to include you in other profile lists and switch btw them :)
Limited CL size also helps with requests to relays, when you know you won't have to ask about 100k pubkeys to build the home feed. It probably helps in many other places. But then it's a less 'general' solution than unlimited list, might limit some use cases. But then 'follows-based' home feed might just be a legacy twitter-like approach and we might end up with a very different set of "filters" to build one's main feed. Just rambling
How about we collectively figure out what turns off the IT crowd when they hear about Nostr, so that we could create a resource that addresses these concerns properly?
Here is how we could do it.
There is a public Google Sheet (link at the end).
Anyone can go to HN, PH, Reddit etc, find mentions of Nostr, find meaningful criticism/concerns expressed, "parse" them, and add a row to the table - one per comment/reply/note. And don't forget to leave your npub in each row.
I will pay 500 sats per row to the npubs of contributors, if anyone wants to join me and sponsor this - just reply to this note.
Lmk if you have a better idea of how to do this.
#grownostr
https://docs.google.com/spreadsheets/d/1QnCfuFytLPLMF03EVKjnHugQe4SHZtcBUk1doJ4YTis/edit?usp=sharing
Someone looking at nostr as Twitter alternative has to check out the content etc and doesn't care about internals.
Some IT person looking at nostr as a new tech cares about internals much more than short note topics. IMO
@Karnage started filling the table, thank you!
I was thinking we'd do a row per reply - this would help find the source complaint to dive deeper, and also pay the bounty properly. You've covered the whole thread in a single row, that's amazing, but you'll only get 500 :)
"Our own" sounds amazing, but we can't wait until someone ships it 😉
Other centralized tables that allow for collaboration don't seem to be much better than google
Just a reminder
nostr:nevent1qqsp7gz3mkqgxgjw4hpwpwhu0zdt9r0x7nlwmh06djrwemea2wcsz5gpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygqmcu9qzj9n7vtd5vl78jyly037wxkyl7vcqflvwy4eqhxjfa4yzypsgqqqqqqss7t420
Great talk!
nostr:nevent1qqsrqg9tlnhnee7hnjlddxggjeyux9rs40sgsctyfpqv5usgvmhmr7cpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygq0ytqxatqsqf5yalxx3atg2s8gxsk3vzw4pz7dgvfvqw8xr98ckcpsgqqqqqqszwhl6x
Marking this with an 'App ideas' label
nostr:nevent1qqsvnkuafyz25md5aqqg85g8rzlna226hppz63qdt4msvagnhkkwajsprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hsygpm7rrrljungc6q0tuh5hj7ue863q73qlheu4vywtzwhx42a7j9n5psgqqqqqqsj2sz7s
Another promising tool!
nostr:nevent1qqstnlqg7cnn736d0r2f8kaja42unsldzpwjjm6zyfzyf3jftqd3egcppemhxue69uhkummn9ekx7mp0qgsvxhlccdqyf8cddzh34mzggja5f2wqhrqa6n6dfmauvhsjqwdrfzsrqsqqqqqpassere
Spring was developed in parallel with Amber, and Spring is for web apps, while Amber is for native apps. We will probably add support for Amber down the line to let you use keys stored in Amber with web apps launched inside Spring.
Looks like it's around 160: {"kinds":[1], "#p":["84dee6e676e5bb67b4ad4e042cf70cbd8681155db535942fcc6a0533858a7240"], "search":"🫂", "since":1698909000}
Searching "Edward Snowden 🫂" doesn't work bcs we don't index mentioned user names inside notes :(
Looks like it's around 160: {"kinds":[1], "#p":["84dee6e676e5bb67b4ad4e042cf70cbd8681155db535942fcc6a0533858a7240"], "search":"🫂", "since":1698909000}
Searching "Edward Snowden 🫂" doesn't work bcs we don't index mentioned user names inside notes :(
Very interesting!
nostr:nevent1qqspg4xdwq8s6xllheumsnj6trq827acd58qzg2ktcdnvfmmcvwzzfqprpmhxue69uhhyetvv9ujucm4wfex2mn59en8j6f0qgsvxhlccdqyf8cddzh34mzggja5f2wqhrqa6n6dfmauvhsjqwdrfzsrqsqqqqqphdhl28
If you click on magic menu in Spring the naddr should appear, or in address bar in the browser on Snort. I don't know how you would categorize them though
In my mind Apply for a bounty was something much more significant than a 'like'. And I wonder if you would eventually introduce some attributes of an 'Apply' - like estimated timeline etc, then it should definitely be a separate kind.
Spring browser v.0.5.0 is here!
We've added a payment history screen for you to audit your zapping activity across apps. We also added a weekly request for feedback - there is no analytics tracking you, so your voluntary feedback is the only channel we have. You feedback is sent as a direct message, and you can see exactly what was sent to us in any app that supports nostr DMs.
Full changelog:
New:
- Add payment history screen
- Add weekly feedback request, sent as structured Nostr DM
- Add app logs at About screen
- Add skeletons to contact list feed
- Add bookmark lists and profile lists to Bookmarks page
Fix:
- Open with Native app now doesn't require fetching from network
- Fix broken encrypt/decrypt with nsecBunker (DMs)
- Hiding a tab 'pauses' it, so it doesn't waste CPU on animations etc
Play Store: https://play.google.com/store/apps/details?id=com.nostr.universe
APK: https://github.com/nostrband/nostr-universe/releases/download/v0.5.0/spring-nostr-browser-v0.5.0.apk
Notes by brugeman | export