Looks like they have valid reasons for doing this - also, remember: they still allow selfhosting. It's less about what they want to do, and more about 'people are shit, as usual, and this is why we can't have nice things'.

It's the moderation staff's responsibility. Sorry for nitpicking, I understand in this case it's likely the same people.

I just get triggered when I hear that an open source software developer should have any responsibilities at all (maybe apart from some extreme examples), and I wouldn't like this idea to stick in anyone's head.

Maybe it's obvious, but how about Kodi?
It has support for CEC (for utilizing your TV's remote through HDMI), of course there are other input options as well.
There's plenty of plugins to support online video services. Needs some work to configure them, and sometimes it requires maintenance when a plugin stops working, but I was in general happy with the way it worked while I used it for a few years.

From what I understand, the RISC-V ecosystem is not polished enough yet, so the state of PineTab-V roughly represents the state of the entire platform for desktop Linux.

They chose an action that is not harsh enough for them to be "fired" as mods, yet is strong enough to be visible.

It reminds me (to a certain extent) of absurd protests against communist authorities, which happened in my country back in Cold War times, ie. https://en.wikipedia.org/wiki/Orange_Alternative . The aim is to make the authorities look like idiots, using force to make them stop. You have to be creative, when you're fighting with someone who has total control over the platform, for me their move makes sense.

I'm as skeptical as you are, but at least they automatically preinstall a few useful gaming apps by default, ie. LatencyFlex.

• KeepassXC should just work, if the browser's key was added to your KDBX database successfully. Other than that, I am surprised.
• Yup, the motherboard clock thingy is a consequence of Windows storing local time, vs Linux storing UTC. It's a minor thing to fix in any of these systems, though.
• Shortcuts thingy - never had a problem, although I did have a problem with KDE's keyboard shortcuts to run a program, which may be related workflow and maybe both were/are broken.
• KDE Connect is surprising, as at least for me it worked flawlessly
• The reboot thingy must be related to Linux Mint. I saw similar thing in EndeavourOS. One nice thing that some distributions implemented, is the ability to apply updates when you poweroff - from my point of view it's a less annoying solution than what you describe.
• I can't comment on the 'cherry on top' one without more details.
  I had a somewhat similar issue on my work laptop a short while ago, when I installed a program, which included a bugged XML settings file, then ran system update. When the updater tried to rebuild some caches (related to ie. icons, MIME etc.), some programs which use these caches simply stopped working. Reinstalling all packages with apt was the only thing that helped, to this day I do not even know all of the parts of my system that were broken.
  But this was one of these issues that happen once per 5 years, and leave you scratching your head and asking "what the hell is going on here?". The difference from Windows is that in Linux, you can have a high understanding of system's internal modular components (at the cost of time needed to learn it), and regular system issues can be identified after a few minutes of Googling.

From what I see, it is about their recent decision to defederate from two other big Lemmy instances (sh.itjust.works and lemmy.world), because these instances (where the registration is open, contrary to beehaw) bring a lot of trolls and moderation burden for Beehaw admins. They had a chat with sh.itjust.works admin staff and both are in agreement that until there are better mod tools, there's not much more that can be done for now.

I'm guessing it's not a big deal to replace it with a third party text messaging open source app; I'm not sure about the Dialer, though.

It would be an interesting solution, to port a few mobile Linux apps to Android (some of them are already there) - I'm a bit worried about potential maintenance burden for platform support; but it could benefit KDE/GNOME apps by getting feedback from a bigger bunch of users.

The entire idea of Ubuntu Touch device support, was to be based on Halium. It's a bit different than regular mobile Linux (outside of Droidian, of course), where mainline is a requirement.

I imagine Meta will simply want to ensure that all content will be added on their servers. This allows to enshittify it for everyone (Threads users and those who federated alike). Federated instances will see the amount of ads included with Threads stuff, and will have to defederate. Then Facebook says 'hey, we made it possible to join us, but nobody wants'.

Worth mentioning, this also brings the first ever stable release of Mobian: https://blog.mobian-project.org/...
Hardware support still needs more love, as Linux phone ecosystem depends entirely on volunteers writing the drivers, but we're getting there.

I second this, I use it with a Dell docking station at work (90% sure it's the same model) and updates for firmware just work on Kubuntu.

Mobile Linux distributions for smartphones might offer some hints on how to tackle your problems - these apps are created in a convergent way, which makes them work well on laptops, tablets and PCs alike. Look for an alternate file manager, for example, to replace Nautilus. Check out https://linuxphoneapps.org/apps/

I looked through the posts.
Explanation of the issue: the userspace implementation of OpenGL for Xorg, called GLX,does not work, maybe it isn't loaded. From what I see, /usr/lib/nvidia/xorg/libglx.so is no longer included in nvidia-utils package, the new name for it is probably libglxserver_nvidia.so

Did you have any lines with (EE) in Xorg.0.log?
Do you see if this log says, if libglxserver_nvidia.so was loaded correctly?
Wouldn't hurt to check, if nvidia kernel module is loaded: lsmod | grep nvidia
Maybe reinstallation of nvidia-utils package could help, although I am pretty sure this was done already when you removed and added nVidia driver again.

Feel free to PM me, whenever you give it another go, even if it's half a year from now :) I'll do my best to provide you some advice.
('nv' is an old driver for old nVidia cards, you shouldn't look in that direction, it's normal that it doesn't load, if nvidia driver does)

It won't be much of help, but I have a few devices:

• Xperia X which so far works well, except that it feels like the phone's internals are a bit too slow for today's standards, so even if I will use it for the time being, if I were yo,u I would pick something more powerful.
• OnePlus 6 which would be very cool (especially that it's one of the best phones for regular 'mobile Linux' so far), if not for shutdown being bugged, which results in time getting reset on every boot. But it's fast enough, and I hope the bug will eventually get a fix.
• last time I tried PPP was not good enough, but it's been ~2 months ago and support was quite fresh. Might need to check again.

Mostly agreed. Although I would say G1 was (relatively to its time) more advanced and stable than mobile Linux phones. It aged quickly, and the hardware felt somewhat underpowered (similar to what probably PinePhone owners feel right now); but it never had a problem to work as a phone or had serious stability issues.

Yes, I am aware we're comparing apples to oranges, and that Google had enough resources to make it work well enough. Still, they probably didn't make it work overnight, and neither should we expect mobile Linux could do that.

Disclaimer: while I did not use G1, I used Samsung Galaxy i7500 which had the same specs (minus the keyboard), and the experience I described is based on using it.

It would be a nice feature, if Phosh behaved a bit different in landscape mode; it wastes too much vertical space, especially using Firefox to browse the web is a disaster. Maybe the top and bottom panel should share screen space at the top instead (each half of the screen); or they should be on the sides instead...

As much as I like the idea behind Pine64, make sure you understand what you're doing - their devices usually need some time before they're useful, they might underperform, etc.
On the other hand, they're usually priced well for what they offer, and I think the ARM model of new PineTab might look better than their usual new offerings. Make sure to find out, how polished it is before you buy.

Looks like the ecosystem still needs another year or two, but it's going forward steadily.