I don't see how game streaming at least in the US market would ever work without higher performance infrastructure anyway. Functionally, it's not a matter of bandwidth but latency. Xbox servers are centralized regionally, so even with latency within WebRTC range (like sub-20ms), cross-country traversal can add up to 30ms which makes games feel awful in terms of control.
I run NixOS as a daily driver and on a box for docker containers.
I will say that it is stable to point that since nothing seems to ever really break, I don't feel I really understand the configuration as well as I could (since I'm not having to fix things and learn).
I started with just traditional NixOS but later moved to using flakes. Because of flakes input pinning, it's much more reproducible but also even more stable. The biggest benefit I see to flakes is the use of local git for updating. Since I have git logs for auditing, if something were to go wrong, I'd just find that change in log and revert to before that commit hash (or just revert to different generation).
The biggest problem I've had is how procedurally some tasks change and sometimes are made more difficult. Symlinks is a good example of that. In Arch, symlinking is just a basic one-liner. In NixOS, it's a matter of writing config more verbosely to the configuration.nix file :
(pkgs.writeTextFile {
name = "tst";
destination = "/bin/tst";
executable = true;
text = builtins.readFile ./scripts/tst;
})
That's a good takeaway from NixOS: things are more verbose in setup, but tend to get set once and never again.
That's wild. So basically a user asking for compensation is treated as the same threat level as that user walking into their offices armed.
That "considered reasonable according to social norms" is REALLY open ended, too. That sounds a lot like the social norm they've been trying to push for "you won't own anything and you'll like it".
It has gotten to the point where devs are just being asked to disprove a negative, though.
"Ok, well you didn't use AI in what you showed but you used it somewhere else."
Short of devs wearing body cams to try and prove literally every step in every process, people are going to have to have some faith that developers aren't using it.
You can but the effectiveness is debatable.
A good question might be how are you seeing that Google still knows it's you?
They more than likely are, but how are you determining that?
There is a glaringly obvious issue with this article that I see a lot of people in the comments seem to have missed:
Only one copy of any given book exists
The pretense to this entire thing is that AI companies are destroying the books both because of the process used AND to prevent competitors from accessing the book. There is more than ONE copy of that book. If you buy a book, that doesn't prevent me from also buying that book. You can not like AI for a number of reasons, but this is just stupid.
NOTE:
If destroying the book actually prevented competitors from accessing it, that means that all of these AI companies are only going out on the weekends to used bookstores looking for good deals on second hand books.
From an adtech perspective, switching to different distros is not going to make any difference. Google does fingerprint activity that is not tied to user accounts and can easily associate you. If not to specific user, then to household, if not to household, then to family group, etc. That doesn't make it less private though, just not anonymous (which isn't really a thing on the Internet anyhow).
Your only real option is to just not use Google. There isn't any magic bullet to use their services without providing them details they can then ID you with.
I would say their writing is also absolute shite. The whole concept of a "dragon break" in Elder Scrolls is just a mechanism to retcon their own stories because they've been making them so long that it's too much work to make them consistent and avoid stepping all over previous storylines.
I think it's more just Tim Sweeney trying to be a "billionaire influencer". He has a lot of money and yes men surrounding him, so he believes everything he thinks must by that fact be the correct take.
So, really the issue is you expect KDE to present it in UI which is not the case.
You would have to use the control binary to stop it from running (akonadictl stop).
To prevent it from running in the future, you'd have to edit/create it's configuration in $HOME/.config and add something like StartServer=false to [General].
There is no way to do this in the UI.
Akonadi itself isn't bloatware though. It's an important component that lets "desktop" applications access PIM.
It can be a resource hog, but that's not the same. It serves a valid role.
So long as you aren't using Kalendar, Kmail, etc, just remove it.
This really isn't a technical issue, it's more an estate planning issue.
The basic concern is if you die, everyone gets locked out. That is where a will, safety deposit box, and named executor come into play.
Whatever credentials and guides needed can be safely stored and upon death that will activates and the executor hands over the access to whoever you are needing. The safest assumption to make in these scenarios isn't that someone won't know how to access the information, it's that they won't even know that information exists.
You also have to remember that there is a lot of things to do after someone dies and that these people would also be mourning. So, with that consideration in mind, try to make the process as seamless as possible. Off-loading to an executor of the estate (someone who is not family) also lets those people close to you mourn without having that final burden.
No it was not, as laid out by SKG's own goals from their website (which is now restricted - including past legislative attempts) and by Article 225 whereby they are asking an EU commission to submit a legislative proposal to the EU Parliament for enacting new laws.
This is literally the backup plan they are on now. Stop framing a loss as some sort of planned win. That's not what it is.
And regarding Past Results (https://www.stopkillinggames.com/en/past-results), this isn't the first time they've been here.
The EU has ruled multiple times that it is on the member nations to enact/amend these laws, this has all happened before with the same result.
This is a fair question to ask given recent events.
I don't run Fedora currently, so others could probably give a much more exact answer, but from what I understand of it:
Bazzite is built on top of Fedora with uBlue.
To compromise one of the packages, the attacker would have to bypass the Fedora enterprise team who are rage filled roid-driven experts who don't take kindly to that sort of thing.
They heavily secure their stuff.
Even if an attack was successful, it would have little lasting effect because of immutability and having access to easy rollbacks.
It's not impossible (like somehow stealing Bazzite's keys), but it's incredibly unlikely.
AUR/NPM package sketchiness is not anywhere on the same level as compromising Fedora's keys.
I'm not going to that site because I don't want malware.
I'm guessing the titles include such classics as:
I don't see how game streaming at least in the US market would ever work without higher performance infrastructure anyway. Functionally, it's not a matter of bandwidth but latency. Xbox servers are centralized regionally, so even with latency within WebRTC range (like sub-20ms), cross-country traversal can add up to 30ms which makes games feel awful in terms of control.
I run NixOS as a daily driver and on a box for docker containers. I will say that it is stable to point that since nothing seems to ever really break, I don't feel I really understand the configuration as well as I could (since I'm not having to fix things and learn).
I started with just traditional NixOS but later moved to using flakes. Because of flakes input pinning, it's much more reproducible but also even more stable. The biggest benefit I see to flakes is the use of local git for updating. Since I have git logs for auditing, if something were to go wrong, I'd just find that change in log and revert to before that commit hash (or just revert to different generation).
The biggest problem I've had is how procedurally some tasks change and sometimes are made more difficult. Symlinks is a good example of that. In Arch, symlinking is just a basic one-liner. In NixOS, it's a matter of writing config more verbosely to the
configuration.nixfile :That's a good takeaway from NixOS: things are more verbose in setup, but tend to get set once and never again.
This is just hyprland + quickshell. Why are people saying this guy built all this?
I too have hyprland installed and looking nice... so that means I made hyprland. It's mine. I created it.
That's wild. So basically a user asking for compensation is treated as the same threat level as that user walking into their offices armed.
That "considered reasonable according to social norms" is REALLY open ended, too. That sounds a lot like the social norm they've been trying to push for "you won't own anything and you'll like it".
It has gotten to the point where devs are just being asked to disprove a negative, though.
"Ok, well you didn't use AI in what you showed but you used it somewhere else." Short of devs wearing body cams to try and prove literally every step in every process, people are going to have to have some faith that developers aren't using it.
You can but the effectiveness is debatable. A good question might be how are you seeing that Google still knows it's you? They more than likely are, but how are you determining that?
There is a glaringly obvious issue with this article that I see a lot of people in the comments seem to have missed:
Only one copy of any given book exists The pretense to this entire thing is that AI companies are destroying the books both because of the process used AND to prevent competitors from accessing the book. There is more than ONE copy of that book. If you buy a book, that doesn't prevent me from also buying that book. You can not like AI for a number of reasons, but this is just stupid.
NOTE: If destroying the book actually prevented competitors from accessing it, that means that all of these AI companies are only going out on the weekends to used bookstores looking for good deals on second hand books.
From an adtech perspective, switching to different distros is not going to make any difference. Google does fingerprint activity that is not tied to user accounts and can easily associate you. If not to specific user, then to household, if not to household, then to family group, etc. That doesn't make it less private though, just not anonymous (which isn't really a thing on the Internet anyhow).
Your only real option is to just not use Google. There isn't any magic bullet to use their services without providing them details they can then ID you with.
As someone with adtech engineering experience, oh we know what you are doing in there! We aren't looking at you, but we know! lol
I would say their writing is also absolute shite. The whole concept of a "dragon break" in Elder Scrolls is just a mechanism to retcon their own stories because they've been making them so long that it's too much work to make them consistent and avoid stepping all over previous storylines.
Yeah, he needs to use named keys to make that work.
I think it's more just Tim Sweeney trying to be a "billionaire influencer". He has a lot of money and yes men surrounding him, so he believes everything he thinks must by that fact be the correct take.
3rd party issue. No action needed by jackett.
So, really the issue is you expect KDE to present it in UI which is not the case. You would have to use the control binary to stop it from running (
akonadictl stop). To prevent it from running in the future, you'd have to edit/create it's configuration in$HOME/.configand add something likeStartServer=falseto[General].There is no way to do this in the UI. Akonadi itself isn't bloatware though. It's an important component that lets "desktop" applications access PIM. It can be a resource hog, but that's not the same. It serves a valid role. So long as you aren't using Kalendar, Kmail, etc, just remove it.
This really isn't a technical issue, it's more an estate planning issue. The basic concern is if you die, everyone gets locked out. That is where a will, safety deposit box, and named executor come into play.
Whatever credentials and guides needed can be safely stored and upon death that will activates and the executor hands over the access to whoever you are needing. The safest assumption to make in these scenarios isn't that someone won't know how to access the information, it's that they won't even know that information exists.
You also have to remember that there is a lot of things to do after someone dies and that these people would also be mourning. So, with that consideration in mind, try to make the process as seamless as possible. Off-loading to an executor of the estate (someone who is not family) also lets those people close to you mourn without having that final burden.
No it was not, as laid out by SKG's own goals from their website (which is now restricted - including past legislative attempts) and by Article 225 whereby they are asking an EU commission to submit a legislative proposal to the EU Parliament for enacting new laws.
This is literally the backup plan they are on now. Stop framing a loss as some sort of planned win. That's not what it is. And regarding Past Results (https://www.stopkillinggames.com/en/past-results), this isn't the first time they've been here. The EU has ruled multiple times that it is on the member nations to enact/amend these laws, this has all happened before with the same result.
StealingAcquiredThis is a fair question to ask given recent events. I don't run Fedora currently, so others could probably give a much more exact answer, but from what I understand of it:
Bazzite is built on top of Fedora with uBlue. To compromise one of the packages, the attacker would have to bypass the Fedora enterprise team who are rage filled roid-driven experts who don't take kindly to that sort of thing. They heavily secure their stuff. Even if an attack was successful, it would have little lasting effect because of immutability and having access to easy rollbacks.
It's not impossible (like somehow stealing Bazzite's keys), but it's incredibly unlikely. AUR/NPM package sketchiness is not anywhere on the same level as compromising Fedora's keys.
Just because I ads, here is a straight-forward guide to setting up Grafana and Prometheus to do this exact thing and without any monthly charge: https://medium.com/@achanandhi.m/how-to-monitor-a-linux-host-using-prometheus-node-exporter-and-grafana-3c1d259c22e5