Oh, I assumed you already had setup OBS…

And WHIP is probably unneccessarily complicated anyway.

I was able to stream the output of my V4L2loopback-device (the virtual camera created with OBS’ output) to a browser accessing localhost:<port> with Motion without any setup other than creating a single-line config file defining the port…

Teamspeak and Mumble (which I prefer because it’s free and open-source… also already vastly superior sound quality years ago when Teamspeak was stil the common option most peope used) are indeed “separate applications” doing only one of the jobs… voice communication in this case.

Discord alternatives are complicated, because Discord is conceptual bullshit. It started as voice communication, yet became popular for the text communication.

So you won’t find a good replacement (unless something new created in particular to mimic discord), because the things it now provides are better handled by seperate applications.

PS: OBS should already work on it’s own, without a dedicated webserver on your side. Basically every media program (also browser) should be able to handle streams

OBS’ WHIP (WebRTC-HTTP Ingestion) support should allow direct connection to web browsers.

(I’ll will take a look at it when I’m home)

Fun fact: Contrary to popular believe you are better off using a channel already used by a strong signal than a weak one. Your router will be better at filtering which packets do not belong to your wifi when the signal is strong and clear.

Because the default is set for healthy performance. But users in actual reality don’t care for raw performance but want responsive systems. If you are opening a browser to pass time while some longer process runs in the background, you are less interested in that background process being done 10% faster than in your browser not being sluggish.

PS: Sidenote… Many recommendations are based on older kernels. Since 5.8 swappiness is not measured from 0 to 100, but 0 to 200. So the 60 default is already half of what it was many years ago.

But distros are comparably tiny. So you can use up all those ancient sticks with a few GB you got as advertising that are collecting dust in some corner of a drawer for years. Sometimes they are even actually tiny when you free them from their tacky mascot- or logo-shaped exterior.

“It’s not a professional’s job to read the manuals they need to know for their job unless I specifically tell them to” is an interesting take. A really stupid one but interesting non-the-less…

“Some people don’t like Snaps” 😂

Don’t be rediculous. By then Debian will be on 258 at best…

The problem is that this is not targeting the <1% that would just build their own router. Surveilance and control of the other 99% is sufficient.

Oh, no! Yet another field I will simply leave blank like all the others.

fact is that this change was made

No, no change was made in fact. It was a pull request… that was rejected.

Guess if I propose to edit you comment to “I’m stupid” and you say “no” you have also made that change somehow…

You snapshot them separately, with snapshots stopping where another subvolume starts. Have a problem booting? Copy the latest /-snapshot. But if for example /var/log is a separate subvolume it persists and you can look up what was wrong.

My setup right now has subvolumes root(mounted to /), home(mounted to /home) , logs(mounted to /var/log), snapshots(mounted to /.snapshots), pacman-cache(mounted to /var/cache/pacman) and swap(for the swapfile obviously).

I do snapshots of root, home and logs (landing in snapshots) regularly that don’t require much space (only the difference between on subvolume and its snapshot uses real space in btrfs) and which can all be restored together as well as separately, while losing the temporary data in cache and swap is not problem.

And you can also transfer the snapshots somewhere else as backup (into another brtfs filesystem or as a file), including just transfering the difference from the last one as an incremental backup.

sure it might be possible to install an OS into a btrfs subvolume without wiping other subvolumes, but do I wanna risk it?

There is neither a “might” nor a risk. Subvolules behave like partitions with the only actual difference being that they are not fixed in size but all share the same space.

Blue like Arch?

#1793d1 pls…

Cool… if they won, is there now some money to invest in infrastructure or personal to prevent flatpak fuckups?

In light of recent events I’m referencing bullshit like just uninstalling nvidia drivers as part of a messed up upgrade. And the fact that they finally solved it yesterday resulting in download speeds of ~5kb/s for a 100+mb file because everyone and their grandma tried to finally fix their systems at the same time.

No, that’s just the latest official nvidia driver still supporting those cards provided as a regular package for that distro.

Basically the moment nvidia dropped support for some cards, they split the nvidia package. They are now provinding nvidia-open (all cards still officially supported by nvidia are also supported by the new open soruce driver) and ‘nvidia-580xx’ for older ones. And although the actual driver by nvidia doesn’t change anymore the package isstill maintained in the sense that they look out for it to work with up-to-date Linux kernels.

Arch Linux at the moment provides (via the community maintained repos) nvidia drivers all the way back to ‘nvidia-340’. That’s GeForce8800 or QuadroFX age from 20 years ago.

I don’t know how Ubuntu in particular handles their drivers, but I would assume that at some point support of your card ends end you will then have to install nvidia-<number of the last driver version with support> or nvidia-legacy or something like that, which automatically replaces nvidia.

Nvidia ends support at some point, no matter which OS.

Your card is one of the oldest series still supported (Turing), they just cut support for roughly gtx750 to 1080 (Maxwell, Pascal, Volta).

So 10 years from now, you won’t get working Nvidia drivers anymore and will have to rely on older driver versions.

But unlike Windows -where you will have the same problem and MS won’t care at all, so when an old driver has problem with Windows then, you will be on your own- you will have distros or their communities still providing those older drivers regularly and also there is now an open source driver. And your card is the first generation supported by that driver, although with still some hickups. That one will not go away and get better over time, too. Probably also including some work to increase performance on older cards if there is demand - and if I take a look into my crystall ball (or at the hardware prices shitshow) I assume there will be demand.

TL;DR: I can’t absolutely guarantee that your card still works in 10 years as Nvidia’s support will just end at some point. But your chances are a) very good and b) definitely much better on Linux than on Windows.

In my experience that is in fact more of a MS Word feature (and very inconsistent at it) than a general word processor feature. But maybe I’m underestimating the impact on “average texts” simply because my use of MS products is far below average.