Tool like this exposes big problem with the current shape of the Internet, I believe.

Everything should be possible with just plain netcat and IP stack. Someone asks about NAT holepunching, encryption, static IDs, permissions, etc., yes this is what Internet lacks and why every P2P app reinvents it over and over again.

notabug wontfix; that's the end-to-end principle in action. Bring your own all of that.

Here is another, not so new, idea:

Username is your public key, password is your private key. So we get end to end encryption and account ownership out of the box. Something similar to how .onion addresses work. Needing easy to remember addresses? Build aliases on top of that. Needing server-side automation? Handle trusted server your private key.

Also, almost everyone carry a 24/7 powered and Internet connected device in their pockets. The Internet - network that allows globally sending any data between devices. Maybe with full redesign third-party email servers should be made optional.

I believe we should focus less on how to redesign whole service and build more universal layers instead. First, vsending any data to any machine. Second, optionally remotely accessing our data. Third, mail-like format of data.

Tightly coupling identity to cryptosystems should be entirely dismissed for anything that is supposed to have broad adoption.

First off, these systems always require indefinitely-lived secrets. To rotate keys (or the whole cryptosystem—think future possible quantum computers) is to change identity. Therefore, to change keys is to break the previous identity. Anything that requires users to think about long-term secrets is user hostile and leads to a fragile system.

Second, the economics of pubkey-as-address are untenable. Can you imagine publishing .onion addresses on billboards and business cards, let alone sharing them verbally? Absolutely not.

Unless there’s something I’m missing (please do say), these problems are intractable when you’re dealing with cryptosystem-based identity.

In the end, identity and naming and fundamentally human concerns. If you try to kludge around this with purely technical solutions, all you’ll end up with is a system that doesn’t adequately reflect what identity means to people. Good systems support this (DNS, email); bad systems fight this (cryptocurrency, nostr).

We need more and more varied DNS zones so there's competition between them. And not gTLDs which are just extensions of .us, but zones with genuinely independent administration.

Agreed. DNS is, afaik, the very best naming system we've got. But there's plenty left to do to make it better for human beings. Legally encoded rights to DNS names paired with easy-to-use GUIs for non-technical users would be near the top of my list.

And greater zone diversity like you say too. Kinda related to that, something like increased pinning of non-root DNSSEC keys so that the root isn't so all-powerful.

Edit: s/economics/ergonomics/

"Real" here is very stretched, it is more on the Android than Fedora side, if we measure being "real" Linux as being close to popular desktop distro stack.

It is based on Hallium. And no Flatpak or swappable graphical environments here.

Still cool project.

it is more on Ubuntu side. Fedora is different branch (rpm package system), while Ubuntu is deb package style. Here Ubuntu Touch is using 'click' packages which is basically deb packages. so still more Ubuntu side than Fedora.

in regards of Android: yes it is using ADB as means to flash (like Lineage OS), but in order to change that, you will have to design such system from scratch and that is not easy for community based project like Ubuntu Touch is.

"...avoiding OS security restictions by going through the debug port..." the user delibretry opened and paired to app with clear visual confirmation in order to use it.

What you are is one factor. What happened to MFA approach here? Also it is a factor we cannot change, so if someone obtain a video of our face like that or success in making a working fake, we cannot change our look like we can with a password.

Uruky allows JSON formatted output and basically started to use them as API for my private SearXNG instance. Basically using them as paid search API that is much more reliable than scraping DuckDuckGO and Brave, with the benefit of blocking common AI slop sites and manual ranking of domains. Having EUSP first and Mojeek second somehow gives very satisfying results, both small nearby European businesses and big sites are searched up well, even without depending on American index.

Almost all LLM do traditional web search in the background anyway. So if you want data straight from the source without probabilistic text generation, it will be faster to do the search yourself. Like if I want to know the country of origin of a company, would type its name and go to Wikipedia. While LLM would usually search literally "What is the country of origin of ..."? and then visit LLM generated sites that SEO optimized the query on which a fraction of text is going to be relevant after which the information is very low quality.

Abstraction and reusability is good even when copying is getting cheap.

In a same vain, why create functions or classes, when AI can rewrite the code in place and keep track of rules.

Even on the Android or iOS phone the EU app won't run if the device owner made even a tiniest change of the operating system without Google or Apple approval.

The EU developed system excludes the 1% of people for which the popular mobile solutions do not work and also make the rest 99% totally dependent on the selected corporations.

Even in a world where Android and iOS have 100% of market share, the law (including indirect but obvious consequences of the law) should not force using them.