Avatar
leo
717ff238f888273f5d5ee477097f2b398921503769303a0c518d06a952f2a75e
"In an authoritarian state, rights derive from the state and are granted to the people. In a free state, rights derive from the people and are granted to the state. In the former, people are subjects, who are only allowed to own property, pursue an education, work, pray, and speak because their government permits them to. In the latter, people are citizens, who agree to be governed in a covenant of consent that must be periodically renewed and is constitutionally revocable." Snowden

ok that's interesting, maybe a relay that responds with wrong data?

I am not checking data against the filter as it comes from the network, something for ndk

still wip you can not create lists and invite links in the app yet, should arrive this week

fuck it. Here is the beta release:

android:

https://play.google.com/apps/testing/de.lox.dev.camelus

ios:

https://testflight.apple.com/join/wJWCr1dX

by no means a functioning app, more of a progress report #buildinpublic

please be more sensible about this topic. There are people here who almost died or lost their loved ones

wow thought it is impossible to see northern lights over berlin

Its the best feeling to deploy new solar panels and watch the graph grow 🤤

With collaboration we win

Replying to 21823843...

I just tagged strfry 1.0.0. Here are some of the highlights:

* negentropy protocol 1: This is the result of a lot of R&D on different syncing protocols, trying to find the best fit for nostr. I'm pretty excited about the result. Negentropy sync has now been allocated NIP 77.

* Better error messages for users and operators.

* Docs have been updated and refreshed.

* Lots of optimisations: Better CPU/memory usage, smaller DBs.

Export/import has been sped up a lot: 10x faster or more. This should help reduce the pain of DB upgrades (which is required for this release). Instructions on upgrading are available here:

https://github.com/hoytech/strfry?tab=readme-ov-file#db-upgrade

Thanks to everyone who has helped develop/debug/test strfry over the past 2 years, and for all the kind words and encouragement. The nostr community rocks!

We've got a few things in the pipeline for strfry:

* strfry proxy: This will be a new feature for the router that enables intelligent reverse proxying for the nostr protocol. This will help scale up mega-sized relays by allowing the storage and processing workload to be split across multiple independent machines. Various partitioning schemes will be supported depending on performance and redundancy requirements. The front-end router instances will perform multiple concurrent nostr queries to the backend relays, and merge their results into a single stream for the original client.

* As well as scaling up, reverse proxying can also help scale down. By dynamically incorporating relay list settings (NIP-65), nostr queries can be satisfied by proxying requests to external relays on behalf of a client and merging the results together along with any matching cached local events. Negentropy will be used where possible to avoid wasting bandwidth on duplicate events.

* Archival mode: Currently strfry stores all events fully indexed in its main DB, along with their full JSON representations (optionally zstd dictionary compressed). For old events that are queried infrequently, space usage can be reduced considerably. As well as deindexing, we are planning on taking advantage of columnar storage, aggregation of reaction events, and other tricks. This will play nicely with strfry proxy, and events can gradually migrate to the archival relays.

* Last but not least, our website https://oddbean.com is going to get some love. Custom algorithms, search, bugfixes, better relay coverage, and more!

Can't wait for the proxy 🚀