When you switch to RabbitMQ etc. consider dividing up into multiple queues/topics, as each is constrained to a single core. You can really ramp throughout by dividing them up logically. There is also a consistent hashing plugin to auto shard
_Index Nostricus_
Axum 🤌🏻 *chefs kiss*
Haven’t checked out Dioxus recently, is it suitable for production? I looked at Yew and Leptos a while back. Wasn’t convinced they’re mature enough to replace Vue in my commercial project
A Keycloak extension for NIP-07 login could be huge for building more complex apps. Unfortunately it requires JVM and I don’t know Java/Scala/Kotlin/Clojure. If I’m fluent in C/C++/Rust but have limited time which of those should I pursue?
Do you have documentation on how the integration works? Would be interested in rolling my own
Have never set up Cloudflare; is it possible to have it cache query results or does it always hit the origin server for queries which I imagine must be dynamic?
Holly crap nostr is moving so fast I can’t keep up while working effectively at my real job. Which LN address providers are Zap compatible? (I.e. send receipt back so the zap is counted)?
We’ve built complex scientific software running on HPC systems with it — yet there isn’t even a good web server package (don’t tell me vibe.d). The templating and static if are amazing tho
Oooh, I am liking the member.cash interface. I'm ~500th tho, late to the party
Unfortunately not a hotlink within Damus. I guess I can try a web client on my phone but hate to use hot keys
Trick question: intermittent fasting, don't eat lunch
I looked at a DOE wind map once and noted that southern Mo and northern AR were like nationwide low points for wind, was weird
I advocate for a base-10 system of accounting for hours per day and/or minutes per hour etc. “second” is based on vibrations of a cesium atom, what is this BS
That it's not coded in Nostream code.
It will depend on each relay admin and Code of Conduct, I suppose.
Regarding #[3] 's relay, the Terms are on the website: https://eden.nostr.land/invoices
We will see how it's applied as it goes.
I hear you, but the very first bullet point in the terms is "To not engage in spam".
Of course, but what algo (or who) determines when it "is sending spam" is the crux of my question? Is it posts of a commercial nature? Is it repetitive posting? is it dishonest posting? It is an important question. AFAICT, the definition of spam is solely cameri's determination
My codebases are littered with TODOs and FIXMEs.
I would actually love a CLI tool that scans a code base and emits some sort of structured / formatted output listing the TODOs 💡