erebion

“read the changes before installing a major update”

As if people have the time to read the changelogs for every single package all the time… 🙄

This is pretty important on a server to avoid disruptions and outages, but people have other things to do.

And once it is no longer on and has become a setting, they can just remove the setting and force people to drop gsettings and then remove it completely.

They could also instead ask people on first launch. Some people enable telemetry, so they will find out how many people prefer to keep it, which I bet will be most.

Then that could be solved by displaying a message the first time GNOME is launched, not by disabling it. This will just break workflows for quite a lot of people.

XMPP server, do some decentralised communication under your control. It will federate to other servers, allowing you to speak to other people and join public chats. An old Raspberry Pi should easily be able to server 100 or 200 users. Try Prosody for that or Snikket if you prefer containers and everything working out of the box.

You could also use it as a NAS, if you don’t need a fast NAS. It will probably be enough to stream HD media using VLC on a cheap Android TV device/dongle.

But why? Then the users thinks “huh, weird” and goes on.

I’ve seen that countless times with people that are less technical.

Well, UBPorts still uses .click packages, those did not seem like good solution even in 2015… Those are just .deb files with a different extension and metadata.

Nowadays Flatpak seems more interesting, although… I personally prefer Debian packages.

I was always wishing the BlackBerry Classic would run the same OS, but FOSS and up-to-date and based on Linux.

The Classic will likely never come back (has not even been rooted yet), but it’s nice seeing an OS like that.

Hoping for tight XMPP integration into the hub and something like the BlachBerry Classic hardware-wise. With Mainline Kernel, USB-C and 5G. Ready for the next decade.

That would be my dream.

If there’ll be enough people working on it for quite some time and can figure everything out, then yes.

I’m not going to buy one just in case it gets support. It’s more likely I’ll be disappointed or would have to do it myself. And I’m already mainlining another phone, I really don’t have the capacity to work on this one as well, so… nope.

The SoC will be an unpublished MediaTek Dimensity 7000 series chipset. As it is still unpublished we can’t disclose details about it and need to wait the SoC vendor publications

Pretty sure there will be no mainline support at all…

If Google decides to, it can remove anything from AOSP, as it has done countless of times. Android is deeply controlled by Google.

XMPP server would be another idea, those will happily run on anything and barely require resources.

Just because the linked site does mention it does not mean it is not worth pointing out.

Yes, but just because SMART does not complain does not mean the drive has issues. If it does, it means there are issues. That should be kept in mind.

Several different operating systems, such as FreeBSD, NetBSD, DragonflyBSD (the latter one having a live system and being the easiest to try out). Those have their history based in BSD. But thatʼs all bit too much to fit in s reply here.

Unlike Linux distributions, those projects develop a kernel and the other parts together and make an OS.

Most software will be available on BSDs and on Linux distributions.

The OS itself is kinda nice, but having their own app format surely does not help.

They’ve waiting too long with open sourcing some components and have only just started open sourcing a bit more, I believe they’re currently open sourcing the gallery app.

I test it occasionally, but there isn’t even an XMPP client that supports OMEMO (although XMPP is built into the system), no KeePass compatible app, no Syncthing, no public transport app I could use for Germany, …

I could use it with the Android app support, but that’s proprietary and the goal would be to use Linux instead of Android, not an Android container on a Linux running on an old Android kernel.

On other distros, I can just use regular packages or Flatpak (for example pretty much everything from the GNOME project works on phones these days) and don’t miss anything really.

Just that. Also, most research I’ve seen claim no difference to be found, but surely that also depends and neurotype and several other things, so it might still be helpful for some groups.

Testing does not have dedicated security work and issues could be unsolved for a couple more days. You can use testing, of course, but read Debian security advisories. Upgrade packages from Unstable if there’s something critical and do not wait days for a fix.

It’s called unstable because packages are constantly upgraded, unlike Debian Stable, which stays the same until the next release and only gets patches. It is NOT called unstable “because they do not guarantee that it will work”, for that you’d need paid enterprise support from some company.

Yes, that seems all like neat technology, but what is the use-case for that?

~/git

Everything else is managed by Ansible or synced via Synthing (except ~/Downloads).

I was trying to find a summary of what it does, but couldn’t. That’s how far I’ve got.