I generally agree but it depends on the application and the computer purpose / input you will most use.

Like.. it doesn't make much sense to have a CLI/TUI for an image editor.. if you start using things like sixel you are essentially building a GUI that runs in a terminal, not a TUI. The same happens with videogames, video players and related entertainment applications.

But like I said, I do generally agree. I'd even argue that when possible, GUIs should just be frontends that ultimately just call the corresponding CLI programs with the appropriate parameters, avoiding duplication.

3. The Pixel is easily unlockable, so one can install custom firmware without being a "pro", it was successful/popular enough that got enough hackers interested to form a community around it, and its hardware is (or was reverse-engineered to be) compatible enough to make the experience seamless, with a whole firmware project that it's exclusively dedicated on that specific range of hardware devices, making it a target for anyone looking for a phone specifically to install custom firmware on.

But it could still be a mix of 2 and 3.

Yea, but he's (intentionally?) misrepresenting things.. people are not unimpressed by AI, what they are uninterested in is having the AI be integrated deeply into the OS, particularly when it's designed to be tethered to the network and it's privately owned and managed by human entrepreneurs that do have the company's interests as first and main priority.

And even if they did somehow manage to get permission to switch the license, all previous versions would still be open in perpetuity so a fork would come easily. Immich source isn't only open, and not only GPL.. but AGPL-3.0 which is as copyleft as you can get.

Paradoxically, this move towards trying to make things more secure is actually gonna make things LESS secure.

Because it means that now the only way for people to continue using alternative apps is for them to be shipped with debug keys (the ones used during development) which are fundamentally insecure since they allow anyone to produce an apk and be accepted as a valid update of the app..

You still can release an apk that works by using a debug key.. the problem is that debug keys have essentially "public" credentials. Until now, it was possible to use your own credentials and ensure the app is secure by protecting your own keys and credentials, which is what F-droid was doing. Now this no longer is possible. I don't think this is the end of F-droid, but it'll be the end of F-droid using mechanisms for verification that used to be built-in on Android.

But I expect F-droid should be able to have it's own system for verification, before installing, that is parallel and independent of the apk signing process. They could have signatures in a separate file, outside the APK. This also has the additional paradoxical result that in order to ensure that the apps installed are safe, it's MORE important now to have a store app alternative that you trust and that can implement alternative signing/verification methods.

So... if anything, this move from Google makes Android less secure and makes key signatures within the apks kind of moot for any store that isn't Google-owned... however, it also means installing a non-Google owned store with some level of security guarantees is much more important now.

So paying in order to prevent search engine competition is ok as long as you are rich enough that your payments become essential for those receiving them.

The desktop has been losing market for a while. I feel Windows is already under serious threat (if not already in the minority) when you think about all the devices that mainstream audiences orbit around (phones, tablets, portable consoles, etc), often using the Linux kernel. Only about a third of most website traffic comes from desktops.

Many of the people who frequently use Windows desktop do so because of their job, and often avoid using it outside of work as much as possible, since it feels like.. well, work.

Microsoft has been desperately trying to appeal to those other bigger sectors of the pie and has failed every time.

PC Gaming was one sector they had advantage on, yet that has already started to crumble thanks to Valve. I feel that MS will just try to push for integrating their xbox with Windows OS more and more...

I feel it's a battle with many fronts, since PCs have many uses.. so MS is likely to run their typical spiel: copy what the competition are doing and try to centralize/integrate it with their OS in a way that gives them an advantage, as they are famous for doing.

Another sector they can do this is with the WSL (Windows Subsystem for Linux)... they could turn Windows into a frontend for running Linux apps... so if Linux apps became popular, they could try to advertise Windows as the "best" way to run Linux software without losing the full first party support of legacy Windows software.

This is grounded in the assertion that a website’s HTML/CSS is a protected computer program that an ad blocker intervenes in the in-memory execution structures (DOM, CSSOM, rendering tree), this constituting unlawful reproduction and modification.

This is ridiculous... the in-memory structures are highly browser dependent, the browser is the one controlling how the DOM is represented in memory.. it would imply that opening the website AT ALL in a different version of the exact specific one they target or with a different set of specific features/settings would also be a violation, since the memory structure would likely be different too.

At that point, they might as well just ask for their website to not be visited at all.

Thunar is a much better alternative, in my opinion.

I think that's the point, he's saying he'd rather use USA-linked FOSS than non-USA proprietary software.

From what I gather, I don't think it's about any stance from Codeberg in general, it seems they are attacking "several projects advocating tolerance and equal rights" in particular. They just happen to be hosted in Codeberg.

espeak default voice backend is synthesized without using actually real voice samples. So it doesn't require downloading a huge package for each language, which is convenient in some cases, but the outcome is extremely robotic.

You can use MBROLA as backend for espeak so that it uses some voice samples and the result should be less jarring (it'd still be easy to tell it's not natural voice, but at least you'd be able to understand it better). There's a tutorial on this here: https://github.com/espeak-ng/espeak-ng/blob/master/docs/mbrola.md

Or you can try piper (https://github.com/rhasspy/piper) it's one of the most natural-sounding TTS (here are some samples).