I'm sorry but clearly the introduction of these apps with these requirements in the near past and near future represent regression over time rather than improvement.
I think it was last year that there was a good presentation from them about how they were going to use ZKP and it was indeed very trust inspiring. But do you think the latest digital wallet solution from eg Danish government uses ZKP? Of course not!
I have to say that the tune they play at FOSDEM and what we see put into production are just two different things.
I see your point about the disconnect between the rhetoric and what we actually see in production. Perhaps "regression" is a strong word, though, IMHO I tend to see it as a very slow and uneven evolution.
Even if the pace is frustrating, there are still pockets of genuine open-source adoption in the European public sector. For example, we're seeing projects like Germany's OpenDesk or various municipalities moving toward Nextcloud and other sovereign cloud solutions.
The EU Open Source Strategy[0] was announced just under a month ago and it specifically mentions the EU Digital Identity ecosystem, including the European Digital Identity Wallet (EUDI Wallet) mentioned in the article. I agree with OOP that the requirement of an Apple or Google phone goes against these ambitions, and I will contact my elected representatives.
What he's correctly saying is that if even one major country adopts an EUID Wallet implementation that only allows for Google and Apple, this on its own has a magnitudes bigger impact than the pockets you're talking about. That's a regression.
Do you mean something like rerouting you to make sure you pass a mcdonald’s at lunch time? Or are you talking about mcdonald’s always showing up when you search for food along your route? Rerouting would surprise me, but really it wouldn’t surprise me that much at this point.
Rerouting. Not that it completely takes over the route ofc, but that (potential) ad revenue is a metric just like traffic, speed limits et.c. that gets considered in the decision making.
With cryptographic keys, normally stored on a smartphone. BankID[0] is the most common solution, but there are others. I personally use biometric 2fa to log in, and PIN to sign contracts or pay.
Does it handle both recurring events and recurrence?
E.g. move the lawn every other week vs pay rent on the 17th every month. If I go a week overdue on rent I still need to pay the next on the 17th. If I go a week overdue on the lawn I don't need to mow again for two weeks, not one.
For recurring tasks, the tool tracks the current interval and don't attempt to verify past intervals. Similar to past due single time tasks, they won't show unless you query specifically.
One of the reason is complexity, the other is that I'd rather have this tool be helpful whenever invoked, vs. forcing users to remember to update yet another tool.
stoically, the maintainer and creator of this extension unfortunately passed in early 2023. There's a new fork available[0], linked from github[1].
I briefly discussed this extension and how to proceed after the passing of a maintainer with Mozilla staff in their Extensions and People teams at FOSDEM this year, but there was no real procedures in place at the time of our chat.
Yes, that's truly sad that he passed. It is fortunate that he left that open-source project, where others can pick up the torch. As the forks continue, it becomes a small tribute to him.
Ente looks like Immich[0] (which I self-host for myself and family) with e2ee. I like non-e2ee because if something breaks then the files are stored as-is on disk for easy retrieval.
At FOSDEM, we discuss this at great length. There has been some movement, and I am optimistic that it is improving year on year.