Wait, so after ~10 years Wayland is finally going to have window positioning?

To my not up-to-date knowledge (2021-ish) audio calls work but they require an extension (on both participants) and are limited to 1:1, no “audio conference” support.

I do think there’s bridging for Mumble? If so that should at least cover the “audio chat” use case.

Version 127.0.0.1 forever!

Good luck! Report results.

This whole “FOSS names are bad” sounds like a Mccarthyism sysop by this point. Like, really, who is pushing that crap?

XMPP aka Jabber.

Well, recalling from my experience with a lot of software products, they all tend to rust by around or shortly before version 7, so…

Oh thanks, I know well about it. podman unshare is the reason why those permission issues are not major (eg.: you don’t need to ever sudo to solve the permission issues rootless causes, I think?). But my going to was more focused o borking the output or workflow of using some of the “usual” tools of a Linux console, such as needing to account for the potential existence of a podman environment on the user account (or any given user account, if doing house cleaning under root) if you ever need to rely on the recursive results of things like chmod or find.

Nothing (well maaaaaaybe IRC) beats XMPP / Jabber when it comes to installing for small institutional needs. There are pretty good servers around, such as Prosody.

I can understand the point that Word is needed for producing some borked, glitched, eldritch formatting that 99% of people expect as correct because Office is that much widespread and has trained people to be Wrong on the Internet; and in that case yeah I would still recommend running a(n older version of!) Office just so that you can process (and test) that you are producing what is expected in the exchange.

It’s curious actually. While LO compatibility has improved, I don’t think anything close to an umbrella “Imitate Word [$VERSION] Glitches” option has ever been added or even considered for LO? How about the other Word imitators? Can eg.: WPS or Calligra replicate Microslop idosyncracies? Because if so, running those would be better than running Office on a remote.

It’s pretty great, and I like that the workflow for creating containers is sliiiightly easier than on Docker. I switched from Docker to Podman for most stuff about a year ago and so far there are only two hiccups that I lament:

• the higher disk consumption due to not being able to share image storage. (I’ve tried with additionalstorages but that seems to only be respected for podman run; podman build and podman compose seem to ignore it and always pull images from the registries)

• Some annoying isses with fule permissions due to rootless design - running rootless containers will create files under your user storage that you as a user have no permission to transfer or remove for cleanup or security, and severely breaks the output of tools like du or find due to error spammage.

If the only thing you need is not even the whole Office suite but just a Word processor (and not even any particular version) and since you’ll be remoting to it for the graphical access, you don’t need to spin up a whole Windows VM for that. You can just spin up something with Wine and install the Word component from Office 2013 on that (I’d say Office 2013 at most; you might be able to get away with Office 2007 but I wouldn’t recommend it).

I certainly hope so! But still, that’s useless for Flatpak if they themselves don’t also make the change.

It’s quite telling that a system intended to make apps usable everywhere on Linux, does not use the audio backend that works everywhere on Linux.

Nice try, fed.

Potter the same lamepotterycrap of systemd? I can feel where this is going.

Kudos to them for giving wayland a chance, maybe one day it will be possible to implement a decent desktop environment on wayland, but for the time being, small steps.

XMPP is the best among the listed options, although ??? is not that far behind (or wouldn’t be, I still can’t find a mobile app, does anyone know one???). Good servers include Snikket, ejabberd and Prosody. It’s also the best fit for a small and/or private installation because it’s quite light (not lightweight like IRC, but still light), whereas Matrix is a nu-protocol and this quite hefty on resources, and honestly I have never seen benchmarks on what running a ??? service is like, not even for the official Docker container.

One of the big hindrances of Flatpak is precisely the dependency on PA, when both ALSA and Pipewire exist and the former has worked perfectly for over 20 years. Only way they could have made it worse was if it depended also on systemd.

Energy management is the part that still complicates things most for me. Rfkill not being managed correctly. Machines that suspend but don’t hibernate, or that hibernate but don’t suspend. Laptops that de-suspend during transport. Batteries that overdrain during suspend. Bluetooth. And most annoying of all, NVidia (insert Torvalds iconic scene).