4 ms·
ZeroNet makes it easy to serve dynamic content with its p2p SQL support.
by corv 11y ago
ZeroNet makes it easy to serve dynamic content with its p2p SQL support.
- kefka 11y agoI don't know.. That just seems inelegant. SQL was great years ago. But after working with things like MongoDB, MNesia, and blockchain tech, SQL based databases just seem inelegant.
- zbyte64 11y agoI don't think it is SQL over P2P but rather it just uses SQL internally for syncing. Or at least that is the impression I get from reading: https://docs.google.com/presentation/d/1_2qK1IuOKJ51pgBvllZ9Yu7Au2l551t3XBgyTSvilew/pub?start=false&loop=false&delayms=3000#slide=id.g9a1cce9ee_0_4 https://docs.google.com/presentation/d/1_2qK1IuOKJ51pgBvllZ9... Sqlite is preferred for embedded databases which seems to be what this app is using it for.
- kefka 11y agoThat's not as bad as I was thinking. It sounded like (and documents are sketchy) that this was some sort of shared SQLite db over their net. It sounded rife with potential problems and interesting injection issues. I've dealt with enough bad SQL statements and poor websites with injections and all. Poor bobby tables. Now, I thought about how to handle a similar dynamic data issue with IPFS: We had Usenet years ago and it's still creaking along in a few places. What if we bring that tech back, to an IPFS era? I'd be eminently glad to get rid of 'forums', and go back to what we had prior. The only piece that was missing is how we maintain all the different groups and posts. That's now solved by a blockchain containing the root pointing towards other 'chains, and then to posts themselves. I'm seeing it in my head how to construct this, but it could be relying on faulty understandings too :)
- zbyte64 11y agoNot sure what you mean by "dynamic" because both systems publish static files and register a link to a root document with a name system (namecoin or ipns).