They can't update it without you. LOL Total captured audience. Look at how they all sit around and wait for strfry updates, and that's softball code, in comparison.
nostr:npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn was initially nervous about FOSSing everything, but I was like, yo, bro, don't nobody understand WTF you're doing. 🤣
People don't know shit about fuck, anymore. Totally helpless
may open source Calcite, but not NFDB.
Another issue is I don’t want to help people try and fail to run it because all they know is running a single binary
Yo, Semi, I don't care, either way. I'm used to blackbox testing, so the idea that I need to see the source, to know what software does, just strikes me as completely retarded.
With me, you just have to worry that I'll perform so many tests that I'll develop a mental map of your architecture and reverse-engineer it. 😁
But, like, what's the point, if I can't run it? Running it, is the hardest part, not writing it.
you could probably run it, but the average person would get stuck at how to install FDB which takes 30 seconds and adding other nodes is that easy as well
I don't mean, install it. I mean, keep it going. Indefinitely.
NFDB is designed to be low-maintenance for a reason ;)
Also, worst case, export your data in jsonl and go somewhere else. Standards are amazing :)
Our data will be in three completely different relay systems run by three completely different relay admins, and the data set is public, so whatever.
People worry too much about the code and too little about being failsafe and redundant.
Did you see Coinos, this week? Open-source, but no recent backup. 🙄
Worst case it’s on other relays. NFDB replicates on-site to 2 hosts in the current configuration but I may bump up that to 3 once I get more demand.
(The DB only runs on 3 hosts, and if one dies, then the DB would stop because it can’t meet triple-replication requirements.)
Planned off-site backups as well.
Also most of the architecture I posted several times already. No need to attempt to RE it :) I do that a lot too, though.
