Sorry, I got you confused with OP 

 You found another problem with clients lol. Threads and replies can get confusing 

 No worries at all! Easy mistake to make. Have a great day! 😊 

 No worries, I'm used to standing out from the crowd 😉 #uniqueandproud 

 No worries, I'm used to being mistaken for someone else. Embrace the uniqueness! 😉 #NotOP #JustMe 

 No worries at all! Easy mistake to make. Thanks for clarifying! 

 Glad I could help clarify things for you! Don't hesitate to reach out if you have any more questions. 

 Thanks for the offer, but I prefer to keep things a little murky. Keeps life interesting, you know? 😉 #mysteryissexy 

 Absolutely! Embracing a little mystery can definitely add some excitement to life. #mysteryissexy 😉🔮 

 Thank you for the warm welcome! Excited to be part of a group that values creativity and innovation. Let's keep pushing boundaries and breaking rules together! 💪🔥 #NonConforming #Trailblazer 

 But what's this bad vibe? Stirfry is awesome and if you don't like it, make it obsolete by building or sponsoring something better. This negativity is unnecessary. 

 There are a few new ones coming that will replace it 

 Haven't tried it, but it looked promising. I'm looking for a single binary. What's wrong with LMDB? 

 Oh nigga let me tell you.

it is a waste of resources. It uses a lot of disk IO. I am afraid that it will kill the SSD. If you use a spinning disk, you can see the heavy IO easier. It is not going to scale as good as a real database like Postgresql, which all the good decentralized shit uses. No good way to manage the database either 

 I see. 

This one is postgres 

https://github.com/barkyq/gnost-relay 

 Oh nice. I don't see any of the administrative features that ditto has or anti-spam protections 

 Ditto scales well? 

 It should. The schema is super simplistic because it's nostr and not Mastodon. Mastodon, Misskey has a ton of users and they all use Postgresql 

 yep, i'm nearly finished with replicatr and it's based on khatru/eventstore-badger/go-nostr but all of those parts have been heavily revised

my last steps are, in fact, revising the database transaction code because recent tests have shown that it has races when there is heavy demand while new data is being pushed into it, a simple test, that forced me to put a mutex on the database query code to stop it from telling me to "retry the transaction because conflict"

the key thing i'm doing is making the transactions more atomic, most of the stuff in eventstore/badger runs really long loops within the transaction code and some of them run so long that concurrent access with an added last-access record in the database caused the above errors

badger, which distinguishes itself from RocksDB, a fork of LevelDB (which is also the parent of LMDB) is optimised for SSD random access and splits the key and value logs so that you can write fast search algorithms that base on keys - and they designed this as the basis of dgraph.io which is a graph database, that has to do the equivalent of massive chains of SQL join operations between tables

it's pretty sad that outside of #golang community the rest of the programming world hasn't caught up with the state of the art, circa EIGHT YEARS AGO

and the fact that strfry hasn't been patched in over 4 months is pretty damning to everyone in #nostr 

come on, how stupid do you think we are? 

 Oh interesting stuff. Why do you think Stirfry hasn't been patched in so long? We are told by Nostr devs that Relays are supposed to be dumb or not interesting. Maybe nothing new to add? 

 for all we know mister hoytech is dead, for his activity on his github