Even worse: it silently fails if the device does not run an unmodified anf certified Google Android OS. This means, it will not work on alternative OS and rooted devices

It also silently fails if other party has android phone, but no internet connection. There is no fallback to SMS which works over plain GSM.

Alexa Echo Dot has 6 or 7 microphones. I'd expect that makes it much easier to filter out voices directionally than only the 2 microphone this hardware has. I hope they release a version with more microphones.

How does that differ from or relate to the already implemented GNS (GNU Name System)? https://www.gnunet.org/gns.html https://datatracker.ietf.org/doc/rfc9498/

More like: Many people want to run their applications on other people's phones, without those other people having any say about what that applications do or don't. It is security, but security of the app publishers against the user.

This - enterprise app creators (more concretely, their security auditors) outright demand that the users are locked out of their devices and that the device confirms and enforces that before their app is installed. The amount of these apps and these processes is increasing and has now made it into governmental rules as well (e.g. new digital IDs).

> The amount of these apps and these processes is increasing and has now made it into governmental rules as well (e.g. new digital IDs).

All the more reason to find ways to break those restrictions.

Surely running a digital ID app on something like e/os is possible? If not there should be a lawsuit.

I guess you mean: a non rooted Android, conversely, inhibits the removal of bloatware and spyware. Yes, a proper solution covering all needs is needed.

(Personally, I do not use said «critical applications» because I do not trust container, application and providers. So...)

GrapheneOS pushes hard for remote attestation though.

That's apparently just green washing. If they were serious, they would at least offer bootloader unlocking?

This does not work for map applications.

reasons: 1. most other devices don't provides access to low level wi-fi drivers to actually support AWDL. 2. Airdrop is authenticated using Apple accounts on both sides. 3. legal foo

This is wrong. Wi-fi direct has always been possible with Android phones. Android even supports wi-fi direct connections simultaneously with wifi ap connections. Abdroid also supports the new wi-fi aware, euch simplifies initial contact via broadcasts. I am not sure why the device manufacturers wouldn't implement it. Maybe they target iPhone first as the more premium users (which might only be true in the US), and then think they cannot support that feature for lowly Android users. If enough devices supported this, Apple may be incentivised to follow?

If this is possible without any further APIs needed in Android, you should develop the next generation of the eye-fi type of concept which does what OP wants. You'll make a killing, and I agree, it's the kind of thing which theoretically could force Apple to at minimum steal your idea for their platform, or maybe if they're feeling generous provide an API for developers.

I found that forced namegrab by the original autor quite rude in the beginning, but now I made peace with that and like the name hyphanet even more. That whole drama backfired for him: First, there will be always this discussion. Second, the term Freenet is quite unusable in search engines, whereas hyphanet is nice and unique to find in search engines.

Yes, Hyphanet is considerably safer and does not compete with a multi-billion Euro corporation about brand rights.