Forgive my technical ignorance here: Could SQLite be used as a "lightweight" ActivityPub datastore, for a hypothetical ~single-user instance? Leaving current implementations (Mastodon, etc.) aside, I'm curious if/how this could work? /cc @simon
@simon @case @takahe Doesn’t SQLite depend on only having one process accessing a database file at a time? I would be a bit concerned about how well background workers (of whatever flavor you choose :)) would work in that scenario.
But I also haven’t really gotten to use SQLite “in anger” and am wanting to learn more about it. :)
@takahe @case @simon @edmistond sqlite supports multiple concurrent readers, and works fine with multiple writers (one holds the write lock and the rest just wait). It works fine for single person instances. I added the sqlite tests, but keep in mind it's not a focus of the project at the moment.