Spark is a personal AI assistant. You store information about important (future) events in a local database. Spark sends this information to an AI API and compiles a summary of the events for you.
> 1/ would this be able to generate a QR code for recurring payments?
Maybe the underlying technology is not really well explained: the code is generated "offline" and static. Nothing leaves your computer when you generated it. It can be used as often as you want, but will be for the same payment (amount, remittance, destination account). Many people can scan the same code to pay the same amount, or one person can scan the code on a recurring base (eg. you pay your internet invoice every month and it's a fixed price)
> 2/ the generated QR when read would translate into a payment order accepted by any online banking platform?
You need to scan the QR code with a "compatible" banking app. Not every bank app has support for this, and if they support it, they don't always support it equally. Many banks in Belgium (and at least all the bigger banks in this region of Europe) support it, but eg. the allowed characters in the remittance message varies...
I would be interested in knowing which banks do and don't support it, actually! One can have only so many accounts with different banks... In case it needs explaining, generating a code and scanning does not cost anything (except your time and electricity), unless you hit the "confirm" button on the payment dialog in your banking app...
It's in the works under the EU Digital Identity Wallet Consortium (EUDI)[1]. Here's an example [2] of a specification being discussed that is similar to OP's QR code.
Yes; could have sworn they had weight lifting by default, but apparently not. They have other indoor activities, however. But elsewhere in the thread, people have suggested many options...
Yes, as stated in the README... I would love to. There seem to be some libraries to parse the .fit file, so when I have more time, I'll take a look at that.
I did some evaluation of HTMX a few weeks ago; while I understand the appeal, it does not yet ... vibe with me. Also, the use for HTMX is still very limited in this project. I don't think this will really change, because the project is fairly focused and will remain so for the time being. Maybe there is an opportunity with the statistics and graphs? Like switch the buckets between km, miles, and number of those (1 km, 5 km, etc), of zoom to more years.
