extension: think about better ways of querying visits

[karlicoss]

Search is nice, but ideally just somehow expose the visits database to the browser, so you could easily filter/sort/query/etc

[koo5]

I don't want to expose the whole "visits" database to browser I hope my database will eventually be big, and it seems proper that it will be maintained in a proper database server, and we'll query it like "give me everything related to <URL>". Possibly that returns a lot of stuff. Also the server will possibly be shared among multiple people.

So next in line is filtering/sorting in the browser, as you say. This kind of comes down to "personal" preference. I'm gonna want to be able to write bits of js to do this, either hardcoded or in the settings page. At some point, i'm also gonna want to turn the json that your server returns into json-ld, and run a rule engine over it (when my other projects mature to that phase..). And i'll want to run a second server that returns json-ld directly, so i'm not limited by the kind of "meta" data i can store and query/filter for..

[karlicoss]

Ah yeah, didn't mean literally moving everything in the browser! More of just having a nice interface to the underlying proper database, because at the moment the only way to query is basically by using search by substring or 'search around'. But since you can use, say, sqlitebrowser directly against the db, maybe it's not really worth spending time doing that in the extension at all..

Maybe it's fine to allow a server endpoint that allows you to directly send SQL (just need to be careful with possible injections etc).

At some point, i'm also gonna want to turn the json that your server returns into json-ld, and run a rule engine over it

Oh, this looks interesting! Can you elaborate what kind of functionality it would allow for in Promnesia?