Avatar
47
3492dd43d496a237f4441fd801f5078b63542c3e158ffea903cb020a1af4ffdd

Seeking some UK or Australian slaves to participate in market research of users in authoritarian regines nostr:note1yh3myvrd2vrxk7nffrtlw2je7rzq95j9cn4f86rdgh4ajsw0xjyqtgngmf

Replying to Avatar Gigi

GM

master of images. gm

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!

fucking legend, ty

lean in to interoperability

Discover Episode Eighty Nine - Discovering #Bitcoin with nostr:npub1mz704n7dsaw3jcj3kr5le45n97tqughyt5lxe3yv3xy3025hv3dsp5tl8g 🔶👀

🎙mindbender, writer and author on Bitcoin, energy, time and space and life.

🎧 https://fountain.fm/episode/xHQCzqFOlCDHJ5UvtrCJ

- -

WE discuss:

• Tomer's Bitcoin origin story

• Mind-Bending

• Concrete Bound

• Bitcoin Saves

• Heaps More

YUGE thanks to Tomer for sharing some of his scarce⏳ and finite⚡️🙏

- -

SHOW YOUR SUPPORT: Zap Sats! ⚡️

via #value4value: discoveringbtc@fountain.fm

via @geyserfund: https://geyser.fund/project/discoveringbtc

via P2P: djdbtc@zeuspay.com

If you dig the show, please zap sats in support! 🫡

Look out for Episode 90, soon! 🔶👀

- - -

🟠 New to Discovering #Bitcoin?

Talk to @TheBTCAdviser - to help you discover Bitcoin, take self-custody, become sovereign, and ensure confidence about your Bitcoin position every step of the way.

Tell 'em DJ from Discovering Bitcoin sent you: https://content.thebitcoinadviser.com/discovering-bitcoin

Love being exposed to new pod! ty 🫂