I’ve created a tool for similar of use-cases: https://codeberg.org/contr/contr
You could run your workload inside, say, an alpine container:
<pre style="background-color:#ffffff;">
<span style="color:#323232;">cd path/to/evil/dir
</span><span style="color:#323232;">contr alpine
</span><span style="color:#323232;">❯ # inside container, run dangerous program
</span><span style="color:#323232;">❯ ./dangerous_program
</span>
If the program needs extra dependencies, you’ll have to write a Containerfile and build an image with the dependencies installed – there’s an example in the repository. Just installing the dependencies at runtime inside the container is also an option, but all changes inside the container are lost on exit.
gnome-initial-setup will default to displaying the toggle as enabled, even though the underlying setting will initially be disabled. (The underlying setting will not actually be enabled until the user finishes the privacy page, to ensure users have the opportunity to disable the setting before any data is uploaded.)
I see what they’re saying here and how they’re trying to give users options for users to opt-out before “accidentally” sharing data.
We are not interested in opt-in metrics. To make this a little more confusing, metrics collection is actually separate from uploading. Collection is always initially enabled, while uploading is always initially disabled. The graphical toggle enables or disables both at the same time.
Given all this I have even lower confidence that the opt-out will be bug free, especially over time. If the settings are separate then why just one toggle? If it were separate, I might want to collect then inspect the data and maybe even choose to share (or use the data myself some other way).
Few users would opt in…
Well yes, if it’s all my way or the highway. I understand that this is a tough problem to solve and a tougher one to message correctly. Hopefully someone will figure it out one day.
For me efficiency and less eye strain is important. I want my eyes to be at the center of the screen for the majority of my session. Gnome is my goto for that reason but any tiling windows manager would do as welll.
KDE and the windows start bar lookalikes constantly have your eyes going to the corner or sides to open and find apps.
Here is a related question - when I was writing random or zeros to the raw device (/dev/sda) I was getting speeds of 1.7 or so mb / s now I am getting 25 mb/s writing to a file in the partition.
Have you tried it with a different enclosure or directly connected to your PC? My last two “faulty” HDDs actually just had a faulty controller in the enclosure. Drives were fine.
If you’re gonna do btrfs snapshots, you may also want to create subvolumes for certain directories to exclude them from the snapshots, similar to rootco.de/2018-01-19-opensuse-btrfs-subvolumes/
Gaming on wayland now has more or less the same performance as on x11. Some things like vrr (atleast on plasma) is even better/easier on wayland than on x11
though can’t really see any need for it as my monitors are similar resolution there
Well wayland may help if the refresh rates of the monitor is different. Also Wayland will be the only one supported in the future as if I understand correctly, X11 is no longer supported
One has 144hz 1440p and one is 60hz1080p, I’ve got one of them running on 170hz on x11 afaik, what’s normally the problem with differing refresh rates?
It’s all built on slack so the core of it runs on potato.
The idea is you whack it on a USB and boot off that. All your drives become an array for UnRaid and you can easily generate a swarm of dockers or VMs to do whatever you want.
They have a massive catalog of docker apps ready to rock, including a WefWef Lemmy client!
One more version without the obvious UPnP. At this point I think they’re not implementing UPnP in order to somehow profit from the lack of it in the future. Who on their right minds wants all traffic going over a server when in most cases you can simply use UPnP? This makes no sense.
Also yet another version with the address book not implemented, but I bet the sign in button is still on the client to continue to confuse new users. Almost 2 years that button has been there to do nothing.
the inability to deploy to macOS with a custom server (they allow this for Windows with a renamed executable). rustdesk.com/docs/en/self-host/install/#put-confi…
I am not sure myself, so the following may be wrong.
In my understanding, the rewrite refers to the RustDesk desktop whose interface appears to have been created with Sciter, which was replaced by Flutter.
That looks right actually, so they had been using Flutter already for mobile and finally decided to align their desktop codebase to it too, makes sense
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.