lexlambda

OpenStreetMap data really is a godsend for such OSINT purposes. Works much better in populated areas too, with more features like roads, shops, electric lines that can be used to search.

You must realize, age verification is for more then just Googles Android apps.

Such a strong new legal framework must consider consumer hardware actually in use:

- Android variations Like GrapheneOS, Huawei's HarmonyOS, older phones running custom ROMs - Linux phones, which are sold in the EU and by EU companies

- Desktop operating systems

All of them can run Web Apps, and thus need age verification

as far as I'm aware, Adroid is not the same as the requirement here, which requires specific Google attestation.

There is GrapheneOS, HarmonyOS by Huawei, LineageOS for older phones and many more Android ROMs.

Additionally, Linux phones exist and are already sold in the EU to consumers, not just a prototype.

There's really no justification around limiting the OS selection.

There is also Linux, Windows, MacOS and many more operatint system not limited to phones.

Organic mentions Open Source, but I just saw that FDroid mentions the following: "This app contains non open source components - compiled binary data files (including but not limited to .mwm map files) under a non FLOSS license"

Anyone has context on the following not hidden over Git-* issues (I was left thoroughly confused trying to understand it)?

Why? To sell you something. If the traditional web incentives were to disappear, the internet will become just ads, selling things & work.

The web won't die. It will just become even more commercialized than it already is. You might recognize most of the things listed.

Selling things: Restaurants, hotels, local businesses; Ads: more of the same

Work: a) Projects people collaborate on and need to share information b) Writing articles to boost a resume

And maybe sharing what people do, they do it for free, see social media.

I second what the other commenters have said.

There are several factors at play making conflicts almost impossible:

- A central device can be immediately synced to. For Nextcloud, it could be a server, for direct synchronization that I use (Syncthing), my phone (almost always online) is the intermediate device for all.

- You are usually online when creating accounts/password, so an sync can happen directly after a change

- And finally: How often do you actually _create_ accounts rather than just read the database? And how often do you do it on two devices in quick succession?

LMDE is Debian-based, I believe you meant Linux Mint itself, which also doesn't use snaps.

You get all the driver support and tools from the Ubuntu base, with some nice additons. However, not all desktop environment are supported.

A slight factor differentiating security systems here is involved to the advantage of defenders: Attackers have to find a whole exploit chain, while defenders only need to fix one part of it.

This is a filter added by you (or by an overzealous list maintainer), it does not happen by default or even with the provided additional filterlists.

Like posting an archive.is link, others can actually read it. No login required for reading replays, no popups and signup nagss.

The donation is more or less virtue signaling rather than actual insight.

The problem can not be helped by research research against cybercrime. Proper practices for protections are well established and known, they just need to be implemented.

The amount donated should've rather be invested into better protections / hiring a person responsible in the company.

(Context: The hack happened on a not properly decomissioned legacy system.)

This is certainly missing some kind of legend explaining the colors of the lines, and what data is actually shown.

Is "red" high or low velocity? And as an example, I do not understand what the "Boeing vs. Airbus" selection is trying to represent, as well as how "Altitude & Velocity" are supposed to be displayed at the same time.

Project certainly requires a bit more care if any discussion should happen around it.

I find it rather strange that so many email providers have to develop their own "app".

There are so many good clients out there, and I'd rather have 1. The team focus on their core offering, and 2. the existing email client is for the same reason (limited developer time, and matureness) a much better choice for security