So-called "cookie banners" usually ask for your consent to much more than optional tracking cookies. By accepting you might be giving your permission to e.g. track you through various fingerprinting methods, build a profile and share it with advertising partners.
I think that's what GnuCash does by default. Even with years of past transaction data it still gets some very obvious matches wrong for me. In my experience it's about 90% accurate for the ones it really should be able to do based on the training data.
>There is a sign-in/create account screen, but this is easily bypassed if you know how to edit an sqlite file.
You can also just add "SideloadedMode=true" to your "Kobo eReader.conf" to achieve that. This removes the "Home" and "Discover" tabs as well, defaulting to the clean "My Books" tab instead.
>Add special signals you can change on your server, which the app will understand, such as a forced update that will install without asking the user.
I understand the reasoning, but that makes it feel a bit too close to a C&C server for my liking. If the update server ever gets compromised, I imagine this could increase the damage done drastically.
I tried the the linked example search for "baby cat" and it returned the same three AI cats you can see in their Google search comparison screenshot on the first page. None of them labeled as AI generated.
Edit: When I explicitly choose to "Include" AI images from the toolbar option, they disappear. When I choose to "Exclude" them, they reappear. Still seems a bit buggy.
>Not if this is one of a few dozen or few hundred similar ongoing operations. The risk is always there, they have to expect some amount of failure.
That actually makes me think it's not happening at a larger scale, since we'd likely have heard of at least a few similarly elaborate cases being uncovered by now. If not during the attempt itself, then at least at some later point in time.
Either almost all of these operations remain undetected, because they are even more sophisticated and much of the world's software ecosystem has been secretly compromised for years or there aren't actually that many such operations.
>simply making the username equal to "[deleted]" is likely compliant.
What if any of the comments themselves contain a name, username or other personal data that could be used to connect it to a person? "Anonymization" by deleting comment's authors like that just seems unnecessarily risky considering the potential fines.
I've been using OpenSnitch on Linux for some time now as well. While the user interface can be finicky at times, it's generally working very well. My biggest annoyance would be creating robust rules for applications using runtimes like Python, Java, Node, Electron or even Wine. After a bit of trial and error, I often end up with a relatively complex regular expression for the specific command and its possible parameters, that may or may not work for all future invocations.
Don't all Firefox extensions have to be signed by Mozilla in order to be installable (in non-developer Firefox editions at least) these days? Even if they're publishing it on their own site, it should have gone through the review.
>imagine that every spam mail receives a masterfully crafted response showing utter fascination and interest in SEO
That would necessitate reliably detecting the emails as spam in the first place though. False positives in particular could be devastating. Imagine a chat bot coming up or going along with business proposals in your name for example.
I agree, it's a little weird that some very basic quality of life features are missing from such a popular and relatively mature product.
Folder management in particular seems to have been an afterthought. You create a subfolder by setting its name to its full path in the hierarchy, including all its parents. And thus, in order to rename a folder you have to manually go through every single subfolder and rename the particular parent in its name.
Other annoyances off the top of my head are things like the inability to change the type of a custom field from e.g. text to hidden without deleting it and creating a new field. Or the browser extension forgetting everything you just typed into the new item form (unless you remember to pop out the window) when pasting a generated password on the site you're trying to register to.
After switching from KeepassXC to Bitwarden for its better auto-fill detection and convenient synchronization, I can't help but feel that it's also been a downgrade in more ways than expected.