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.

Claude / Gemini + OSM Turbo is a crazy you can do natural language queries like "find me a bus stop in germany that's surrounded by more than 5 three story buildings"

*Only works reliably in Germany

yea , heard about them before, but didnt know that whole treasure till I really used it , impressive

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

Well, none of them _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.

All this are Android flavors.

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)?

OrganicMaps rolled their own 'data license' for the actual map files: https://github.com/organicmaps/organicmaps/blob/master/DATA_...

Plus the code that's necessary to generate the map files that OM relies on is no longer openly published. So while true that the actual app code is open source, you can't use it without relying on their proprietary map files.

>Plus the code that's necessary to generate the map files that OM relies on is no longer openly published.

Seems like a big red flag. And another reason to migrate to CoMaps.

>Seems like a big red flag. And another reason to migrate to CoMaps.

Why do you think OM user base forked and mass migrated to CoMaps?? haha

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.

Both are great. I'm currently using the Debian Editon, that at least for me works out of the box. The transition from the Ubuntu-based traditional edition was seamless. I used Mint MATE before.

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.

> news.ycombinator.com:443 is using X25519, which is not post-quantum secure.

This is the result of Cloudflare's test "Check if a host supports post-quantum TLS key exchange" offered on https://radar.cloudflare.com/post-quantum.

Hoping there is already a migration plan. Fortunately many modern tools make it easy to switch to PQ, maybe someone knows which stack HN is running and if it would be possible.

Wow that’s a lot better browser support than expected

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.

Yeah, I remember going on https://filterlists.com/ one day all mad and just adding a ton because of how many ads and manipulative patterns I was dealing with