you can also just check dpkg -L $installed_package_name | grep /etc/apt/ to find files that would have been installed by the package there.

how can you be so sure about that?

none of those technologies that you mentioned execute on the browser at all

sounds like you haven’t met webassembly yet :D

• https://github.com/seanmorris/php-wasm
• https://github.com/ruby/ruby.wasm
• https://github.com/m-butterfield/django_webassembly

please don’t take this as a recommendation to use that, but it does exist.

that’s odd, my (indirect, reported by others) experience with GlobalProtect on Linux was mostly fine, although when using SAML it only really works with the GUI version and not the CLI version

I like having TLS in my browser

it’s clearly 3, stop spreading misinformation

if you’re not community banned you might still be instance banned on the community instance, which wouldn’t show up in your local instances modlog if the ban happened on a <0.19.4 instance. if the methods pointed out by other comments here fail I suggest you visit the instance of the community and check the site modlog there, searching for your user.

i suspect you’re referring to your post to a lemmy.ml community and you have indeed been instance banned there for a limited amount of time.

I have a large library of games I’ve never played on stream. a couple months back I wanted to play a game I had installed a while ago and guess what, forced always online. not from steam, but from the shitty team behind doom (don’t remember which version it was), which just happened to be at the time I had a multi hour internet outage.
afterwards I figured out I had to explicitly block some network traffic to stop it from trying to force me to sign up for an account with the developer.

while steam certainly has DRM options, they are configurable by developers and afaik can’t enforce an always online requirement with just steam, only though custom logic in the game or third party DRM. developers are also free to not use steam DRM.

DRM, as usual, harms the legitimate buyers.

that being said, steam still does bring a lot of value, such as their hardware developments, their work on better Linux gaming support, the update distribution through a trusted source, and various others.

you’re not getting banned from steam, you’re generally getting banned from participating in anti cheat secured lobbies of a single game or a group of games.

single player experience is generally not affected.

having a 3 strike system before getting banned from multiplayer just means it’s 66% cheaper for a cheater to get a new copy of the game.

this is also not new and has been the case for the current family sharing system as well.

here’s also some more context and explanation about what’s going on:

https://fedi.fyralabs.com/notes/9psdqurvye
https://fedi.fyralabs.com/notes/9psnooe6p1
https://fedi.fyralabs.com/notes/9pth6oh3xr

The 90 days disclosure you’re referencing, which I believe is primarily popularized by Google’s Project Zero process, is the time from when someone discovers and reports a vulnerability to the time it will be published by the reporter if there is no disclosure by the vendor by then.

The disclosure by the vendor to their users (people running Lemmy instances in this case) is a completely separate topic, and, depending on the context, tends to happen quite differently from vendor to vendor.

As an example, GitLab publishes security advisories the day the fixed version is released, e.g. https://about.gitlab.com/releases/2024/01/11/critical-security-release-gitlab-16-7-2-released/.
Some vendors will choose to release a new version, wait a few weeks or so, then publish a security advisory about issues addressed in the previous release. One company I’ve frequently seen this with is Atlassian. This is also what happened with Lemmy in this case.

As Lemmy is an open source project, anyone could go and review all commits for potential security impact and to determine whether something may be exploitable. This would similarly apply to any other open source project, regardless of whether the commit is pushed some time between releases or just before a release. If someone is determined enough and spends time on this they’ll be able to find vulnerabilities in various projects before an advisory is published.

The “responsible” alternative for this would have been to publish an advisory at the time it was previously privately disclosed to admins of larger instances, which was right around the christmas holidays, when many people would already be preoccupied with other things in their life.

it sure is possible, but not with the amount of work anyone would be willing to put into it.

i don’t want to go to all that effort

👀

you can just turn it off, see https://help.kagi.com/kagi/settings/general.html

original source for this badly copied blogspam link: https://cointelegraph.com/magazine/china-dev-fined-salary-vpn-10m-ecny-airdrop-asia-express/

reddthat.com.
you should also see that when you click my name, if it doesn’t already show it on my name.

to be fair, iirc it was only a total of 3 comment threads at the time, where two were started by lemmy.world users and one by a hexbear.net user. as those instances are on your instances block list, that would enough to hide the entire comment threads I believe.

seems to be a federation issue for you, I see 90+ comments (reported by client, not counted), earliest from 9h ago

is that because Microsoft doesn’t have QA anymore?

ncdu makes it even easier if you want to interactively browse through folders to see which files exactly are eating up space