So like syncthing but you have to pay for it and requires a server. Seems useless…

If you want to sync while not all devices are online, just spend 50$ or something and get a RPI and put syncthing on it.

Recently deepwiki links started popping up in my search results, when I wanted to research some software. They offered so much genenerated ‘documentation’ that it caused so much confusion and irritation to me, I installed an extension just to block this site from my search results.

Why do I ever need to read the ‘architecture’ or whatever from an ancient no longer maintained project. The deepwiki page didn’t mention that it isn’t maintained, but the readme.md in the repo states it clearly at the very top with big letters…

Any suggestion for a browser plugin that blocks AIslop pages from search results? I think we really need some kind of ad block for this, but differently. A well maintained list of pages containing AI slop and then filtering out those pages from search results instead. So that the internet becomes/remains usable and mostly unpoisend by this stuff.

AIslop should never outrank human created content.

I am not someone that cries about the end times much, but… If this issues isn’t addressed effectively and the internet becomes filled with aislop that outrank and thus hide human content… it becomes useless… We might really have to look for a new one…

The internet is for connecting humans through their machines. If it starts to exist without requiring humans, then it can be its own thing and humans have to find something else then.

/rant

IronFox

But you don’t need to misuse language to assign responsibility.

What? I am interested… How else would you assign the responsibility to people that designed something intentionally bad, if you cannot used language?

“Misuse [of] language” is a concept I cannot even begin to wrap my head around…

Do I loose the warranty if I use language in unintended ways?

It is their responsibility for breaking the system.

You just ‘misused’ language to assign responsibility to people for breaking the system.

Saying the system was always designed for this removes responsibility.

No? Responsibility is not a binary concept. Someone can kill someone else, and would be responsible for that death, and the people around that killer could also share responsibility for not noticeing their unusual behavior. And the system could also be responsible for not giving the killer the support they needed, which drove them to kill someone. And the people that designed or constructed that system could also be responsible for not caring enough about these kinds of deaths to prevent them systemically.

There is a difference is saying “I does what it does” and “what it does is per design”. The latter assigns a responsibility.

In OP Aziraphale gives socienty the responsibility to fix a broken system incrementally and Crowley gives the people in power the fault of intentionally creating a bad system and calls for revolution.

True. But most good stuff isn’t a solution for everyone. It takes real effort to escape vendor-lockin. Bigtech made sure of that.

If something is too simple to set up or requires no set up, or comes from a for-profit company, but doesn’t cost anything, then it always suspicious.

I am just saying that the issue is not with passkey itself, but the individual implementations and that google/twitter/etc. is pushed towards regular users.

Critiquing passkey because vendor-lockin is like critiquing HTML for allowing ads.

True. But I would say that this isn’t an issue intrinsic with passkey. Many people don’t have time/energy or the attitude to think critically about technology and are herded towards Google/X-corp/etc with offers of convenience and because they are often the only offered choice on the web sites. But from the POV of passkey they just act as a password manager.

I use them with bitwarden and a self hosted vaultwarden. If my phone breaks, no issue. If my server breaks, I got local backups… Keys are stored encrypted in a postgres database for which I have access, if I need to restore it. No lock-in issue or risk of loosing access when one or two devices break.

A better, well defined API for password managers to insert login information to the site compared to text boxes.

I self host vaultwarden, and use bitwarden clients everywhere. Passkeys are stored there

Passkeys to me, are a better way to insert login information. Some developers don’t think of passwords getting automatically filled in, so this autofill sometimes breaks. Passkeys might be a improved interface to integrate password managers. Also, sometimes 2FA keys from my bitwarden client gets copied into the clipboard, which sometimes overwrites the stuff I wanted to preserve in there. This does not happen with passkeys.

I store the passkeys in my self hosted vaultwarden, they are a good replacement for auto inserting random passwords via text boxes.

You can? At least I do that. I host vaultwarden myself and store the passkeys there.

Passkeys to me are just a better way to autofill in login data.

I echo the criticism of the term ‘sideloading’, before it started to mean just installing software, I assumed it meant using a separate device or software on the side, like a PC with a debug interface or memory inspection tools, to inject custom code into a running system or software.

Similarly to preloading libraries into games or other software to replace functions in order to change or enhance the game or software. For instance used with script extenders or game mods. There it is ‘pre’ because the software is not running yet. ‘Side’ would be on running software.

But installing applications (the distribution doesn’t matter) is in no way side loading.

And I really hate that the press or whoever picked this term up from apple or google and ran with it without question.

And now, because that term is so strange and useless in that way, its definition keeps getting changed into whatever the industry needs in order to squeeze out more money and personal data, while taking away the freedom and rights of the owners.

Apart from questionable quality of the result, a big issue to me about LLMs is the way it substitutes human interaction with other humans. Which is one of the most fundamental way humans learn, innovate and express themselves.

No technological innovation replaced human interaction with a facsimile, that way before.

If it would run a open source firmware or be open source hardware, it would be nice. But they are using a non-OSI/non-FSF license, so it is not open source.

Once it passes inspection, the F-Droid build service compiles and packages the app to make it ready for distribution. The package is then signed either with F-Droid’s cryptographic key, or, if the build is reproducible, enables distribution using the original developer’s private key. In this way, users can trust that any app distributed through F-Droid is the one that was built from the specified source code and has not been tampered with.

https://f-droid.org/en/2025/09/29/google-developer-registration-decree.html

The issue there AFAIK is that some app builds aren’t fully reproducible, because if they were the developer signature would still apply and be used. In the reproducible case the security of the build infra wouldn’t matter, because the same app would be produced the same regardless were they are build.

Without reproducible builds, you cannot really trust the software anyway, because the Dev could hook some hidden code only for the released binary app and sign that.

Na… The likelyhood of installing some bad or fake app from google play store is much higher than on fdroid.

The ‘availability’ is misleading. If they offer OpenVPN or Wireguard then they are available pretty much anywhere.

Using just plain Wireguard or OpenVPN configs would also be much better than installing random VPN provider apps.

Hmm… I am using git for maybe 15 years… Maybe I’m just too familiar with it… and have forgotten my initial struggles… To me using git comes natural… And I normally pay a lot of attention to every single commit, since I started working on patches for the Linux kernel. I often rebase and reorder commits many times, before pushing/merging them into a branch where continuity matters.