![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/44bf11eb-4336-40eb-9778-e96fc5223124.png)
Surely any kid who went to only one high school is going to have, at the time, thought it was perfectly normal because that’s all they knew? I think our school had 4 floors in both buildings
Surely any kid who went to only one high school is going to have, at the time, thought it was perfectly normal because that’s all they knew? I think our school had 4 floors in both buildings
An overarching principle of security is that of minimum privilege: everything (every process, every person) should have the minimum privileges it needs to do what it does, and where possible, that privilege should be explicitly granted temporarily and then dropped.
This means that any issue: a security breach or a mistake can’t access or break anything except whatever the component or person who had the issue could access or break, and that that access is minimal.
Suppose that you hit a page which exploits the https://www.hkcert.org/security-bulletin/mozilla-firefox-remote-code-execution-vulnerability_20230913 vulnerability in Firefox, or one like it, allowing remote code execution. If Firefox is running as root, the remote attacker now completely controls that machine. If you have SSH keys to other servers on there, they are all compromised. Your personal data could be encrypted for ransom. Anything that server manages, such as a TV or smart home equipment, could be manipulated arbitrarily, and possibly destroyed.
The same is true for any piece of software you use, because this is a general principle. Most distributions I believe don’t let you ssh in as root for that reason.
In short: don’t log in to anything as root; log in as a regular user and use sudo
to temporarily perform administrator actions.
P.S. your description of the situation shows you don’t know the nature of vulnerabilities and security - if you’re running servers then this is something you should learn more about in short order.
Surprised no-one said <your lemmy instance here>
This is equivalent to the assertion that pi is a normal number, which is not proven.
The social construct of race is which features we consider important enough by which to categorise people. So in the USA, this is white, black, asian or hispanic. Maybe native. Those categorisations are based on real observable traits, but we could choose other categorisations. It notably groups together traits which we can easily distinguish and pull out as subdivisions, such as south-east Asians.
We could redraw these groupings: we could for example together north Africans, middle-easterners and Indians, separating out those from southern and central Africa. We could separate Europeans so that Scandinavians, Finns and Slavs are together, separately from western and southern Europeans.
let x = 0.999…
so 10x = 9.999…
subtract first line from second:
9x = 9
divide by 9
x = 1
you could instead do:
dcl() { docker container ls -aq -f name="$1" }
in bashrc
or wherever you’re setting this up.
Why create the function _dcl()
?
Must be time for a new Linux audio system. The pipewire-pulseaudio-ALSA stack of compatibility layers is old hat already.
Sealioning is talked about far more often than it actually happens, because people often perceive both fundamental disagreement and lack of knowledge about something that they are extremely familiar with as bad faith.
This is not true. The Europen ePrivacy direction (“Cookie Law”) specifically requires that cookies (and equivalents) which are not strictly necessary for the delivery of a requested service be explicitly consented to.
That means that cookies which store user preferences like dark mode require explicit consent, because you don’t need to store that cookie to deliver your service. Even though there is no way to store a preference without a cookie (or equivalent) so selecting the option could be construed as consenting to the requirements for making that particular feature work, that is not the way the law is written.
Contemplating existence
I remember looking into the situation with non-destructive editing about… 20 years ago. I wonder how long it’s been a desired feature!
If you’re hosting it, prepare to get sued out of existence!
If your feet get cut, sure. This is why tetanus vaccine is given as post-exposure prophylaxis in many places if you get a wound that breaks the skin.
I’d be quite surprised if rusting could consume oxygen fast enough to make a difference there?
Tetanus is a bacteria that lives in soil. It’s only associated with rust because rust gives more surface area to allow dirt to accumulate on which bacteria can survive, and because iron objects are often sharp enough to pierce the skin. If you were cut with a gleaming razer that had just had soil smeared on it you’d have a good chance of contracting tetanus!
That’s exactly what a “desktop” client would be anyway: a crappy, memory hogging electron app.
It had two buildings. Is that difficult to understand or what? Historically they were separate schools built close together. (Probably a boys and girls school but I don’t remember)
Each had a main part that was a single corridor on 4 floors with classrooms off it. There were extra bits that weren’t part of the main corridor, too, which weren’t as tall, and the main part also wasn’t all classrooms; in one building the bottom floor was, I think, just toilets and changing rooms, then admin offices, and only then were there classrooms, but I can’t remember for sure. In the other building there were 3 complete floors of classrooms and I think one half floor, with the rest of the bottommost floor occupied by a gym.