953 karma · joined March 14, 2021
The online docs (and TBL himself) rarely mention of graph databases, but obviously the idea is tied tightly to RDF. Separating it from that implementation detail is part of the point, though. Getting people to represent their data via an additional format was never going to work.
> For the BBS mentioned here, that might actually be illegal, as it might contain PII
Can't imagine the purpose you had in even making this point. In theory, any arbitrary database exposed publicly could be illegal to replicate due to copyright, PII laws, etc. But that has nothing at all to do with a technical discussion of a technique for exposing data. What a bizarre point to make.
As an aside, I'm glad you removed the "Uh........." from the beginning of your post. We're all making an effort to reduce the typical HN snark in the comments, and there's always room for improvement :D
No, all writes have to go through a normal POST endpoint, it does not accept arbitrary writes from clients.
It is the case here. Writes are happening on a normal linux VPS, and subsequently copied to S3. The read-only queries are using the HTTP VFS. It would be incredibly bad to enable direct writes to a db from arbitrary clients.
For writes, SQLite's single threaded restriction still applies. But for most use cases, scaling reads is by far the most important thing.
> Why not just use a traditional DB like MySQL or Postgres on the backend and a WASM SQL client on the frontend?
The point is that you don't need a backend at all for reads, only for writes. All reads can be served by a static file host or cloud object store.
We can't mimic the local feel of BBSes on the modern internet but i'm confident we can capture the rest of the experience, and at least have something better than the ad-infested garbage heap we see on the web today :D
Before anyone asks about accessibility...i should point out i am still injecting a text-only version into the DOM behind the canvas tag for the sake of screenreaders.
The reason firefox looks so much worse is that it has a smaller webgl size limit than chrome (specifically MAX_RENDERBUFFER_SIZE). When rendering at full resolution, it was not large enough to hold the content sometimes. I only check that webgl value so this will resolve itself if/when firefox increases it.
Usernames just don't work because they require an authoritative server to divvy them out. Ansiwave is designed to eventually be partially or completely decentralized -- all users are just ed25519 public keys, and the ID of a post is the signature of it, so there will never be conflicts between users/posts on different servers.
In theory we could one day have a decentralized way of registering unique usernames, similar to that DNS-like thing they made on ethereum. But i'm not even close to thinking about that right now.
I think the best chance you'd have of getting the local aspect is to not run it on the public internet. Maybe use a local mesh network, packet radio, etc. But the community you end up with, if any, will be quite different than the one that formed around BBSes, i imagine.
I'm working on it. A BBS with a built-in ANSI art + MIDI music editor, accessible from terminals and web browsers, all unicode, no telnet. Ready later this month most likely.
It's hard to replicate the local feel of BBSes though. You can't really enforce local usage on the modern internet, and it wouldn't be great for privacy if you could. But the rest we can do.