Hold on, so the events are put into an SQLite database and in the future an API will come? I'm a little confused. From reading the description I thought this would call a HTTP endpoint with a JSON payload, but instead the consumer will have to poll an SQLDB or an API in the future?
Opensource
A community for discussion about open source software! Ask questions, share knowledge, share news, or post interesting stuff related to it!
⠀
Sorry, bad wording. The README of the package should be clearer.
But in short, this package takes care of the low level interaction with the database and you define the webhooks you're interested in yourself.
So if you want to create a http request every time someone creates a comment with a specific username in the text, you configure it as a webhook in the SQLite database and next time it happens, the URL will be called.
By the api I meant that in the future you'll be able to manage the webhooks using an api instead of inserting them directly into the db.
Ooooh! Alright. That didn't come across that way. Github supports graphs (mermaid?). It might help to have there as I might not be the only one misunderstanding.
Cool project! Should probably be part of lemmy itself!