fact check: they actually don’t always do that, it’s just sometimes

you could use the clipboard to copy the link and open it in another browser

RedHat was a major military contractor with job postings like this current one [archive] long before they were bought by another older and larger military contractor.

https://en.wikipedia.org/wiki/IBM_and_World_War_II

https://web.archive.org/web/20240530005438/https://www.redhat.com/en/resources/israeli-defense-forces-case-study (original is 404 for some reason)

them: fedora is the lesser evil

me: but why do they have job listings like this [archive] with requirements like “This position requires daily on-site work at Fort Meade and an active Top Secret/SCI clearance with Polygraph” ? 🤔

they aren’t the only animal that does it: https://en.wikipedia.org/wiki/Kleptoplasty#Animals

only hobbyists and artisans still use the standalone carrot.py that depends on peeler.

in enterprise environments everyone uses the pymixedveggies package (created using pip freeze of course) which helpfully vendors the latest peeled carrot along with many other things. just unpack it into a clean container and go on your way.

If they had just repeated what I had on my image, I wouldn’t have complained at all.

They posted my address. Stop blaming me for shit other people dead.

My assumption that whatever they posted came solely from your image was because they said:

That barcode above is your full address btw

to which you replied:

But the post didn’t until you posted it.

Do you see how someone looking at that exchange would read it as you acknowledging (via the word “But”) that whatever they posted did in fact come from the barcode, and you are complaining about them decoding it?

If they in fact obtained and posted your full address via some other means, I’m sorry for misunderstanding - and curious how they learned it!

I’m still also confused by the fact that the barcode does not (as far as I can tell) contain a full address but rather just a zip+4 - which you also (still) have visible in text form in the image.

I’m really curious - was it actually your full address, or just your neighborhood? If the former, do you know how they learned it?!

From reading the thread (only after they had already edited their comment) my impression is that whatever they posted came solely from the image you posted. Was that not the case?

Apologies if I’ve misunderstood.

I didn’t. You posted my personal information on the Internet.

They did, but so did you. They could not have posted it in text form if you hadn’t first posted it as a barcode which anyone (still) can decode.

i fully agree that they should have told you privately instead of posting it in text form, and i personally would have deleted their comment if it was on the instance where i could (and if they hadn’t edited it already to remove your address).

however, i must say: you appear to be confused. it has been six hours since their initial comment pointing out that you are doxing yourself via that barcode, and it is clear from your replies that you desire not to have your address published here… yet somehow you have still not replaced the image with a version that censors the barcode.

lemmy has an “edit post” function. if you don’t want your address to be public, you should edit the post to replace the image with one that censors that barcode. HTH!

The canonical documentation is https://www.kernel.org/doc/Documentation/filesystems/proc.rst (ctrl-f oom) but if you search a bit you’ll find various guides that might be easier to digest.

https://www.baeldung.com/linux/memory-overcommitment-oom-killer looks like an informative recent article on the subject, and reminds me that my knowledge is a bit outdated. (TIL about the choom(1) command which was added to util-linux in 2018 as an alternative to manipulating things in /proc directly…)

https://dev.to/rrampage/surviving-the-linux-oom-killer-2ki9 from 2018 might also be worth reading.

How to make your adjustments persist for a given desktop application is left as an exercise to the reader :)

I’m not sure what this comic is trying to say but in my recent experience a single misbehaving website can still consume all available swap at which point Linux will sometimes completely lock up for many minutes before the out-of-memory killer decides what to kill - and then sometimes it still kills the desktop environment instead of the browser.

(I do know how to use oom_adj; I’m talking about the default configuration on popular desktop distros.)

does your resume include a sokoban clone?

that flag is upside down 🤘

keep it steady? did you neglect to install the shock absorbing plate?

I think it depends which side of the debate one is on?

$ systemd-analyze calendar tomorrow
Failed to parse calendar specification 'tomorrow': Invalid argument
Hint: this expression is a valid timestamp. Use 'systemd-analyze timestamp "tomorrow"' instead?
$ systemd-analyze timestamp tuesday
Failed to parse "tuesday": Invalid argument
Hint: this expression is a valid calendar specification. Use 'systemd-analyze calendar "tuesday"' instead?

ಠ_ಠ

$ for day in Mon Tue Wed Thu Fri Sat Sun; do TZ=UTC systemd-analyze calendar "$day 02-29"|tail -2; done
    Next elapse: Mon 2044-02-29 00:00:00 UTC
       From now: 19 years 4 months left
    Next elapse: Tue 2028-02-29 00:00:00 UTC
       From now: 3 years 4 months left
    Next elapse: Wed 2040-02-29 00:00:00 UTC
       From now: 15 years 4 months left
    Next elapse: Thu 2052-02-29 00:00:00 UTC
       From now: 27 years 4 months left
    Next elapse: Fri 2036-02-29 00:00:00 UTC
       From now: 11 years 4 months left
    Next elapse: Sat 2048-02-29 00:00:00 UTC
       From now: 23 years 4 months left
    Next elapse: Sun 2032-02-29 00:00:00 UTC
       From now: 7 years 4 months left

(It checks out.)

Surprisingly its calendar specification parser actually allows for 31 days in every month:

$ TZ=UTC systemd-analyze calendar '02-29' && echo OK || echo not OK
  Original form: 02-29
Normalized form: *-02-29 00:00:00
    Next elapse: Tue 2028-02-29 00:00:00 UTC
       From now: 3 years 4 months left
OK
$ TZ=UTC systemd-analyze calendar '02-30' && echo OK || echo not OK
  Original form: 02-30
Normalized form: *-02-30 00:00:00
    Next elapse: never           
OK
$ TZ=UTC systemd-analyze calendar '02-31' && echo OK || echo not OK
  Original form: 02-31
Normalized form: *-02-31 00:00:00
    Next elapse: never           
OK
$ TZ=UTC systemd-analyze calendar '02-32' && echo OK || echo not OK
Failed to parse calendar specification '02-32': Invalid argument
not OK

Funny that blog calls it a “failed attempt at a backdoor” while neglecting to mention that the grsec post (which it does link to and acknowledges is the source of the story) had been updated months prior to explicitly refute that characterization:

5/22/2020 Update: This kind of update should not have been necessary, but due to irresponsible journalists and the nature of social media, it is important to make some things perfectly clear:

Nowhere did we claim this was anything more than a trivially exploitable vulnerability. It is not a backdoor or an attempted backdoor, the term does not appear elsewhere in this blog at all; any suggestion of the sort was fabricated by irresponsible journalists who did not contact us and do not speak for us.

There is no chance this code would have passed review and be merged. No one can push or force code upstream.

This code is not characteristic of the quality of other code contributed upstream by Huawei. Contrary to baseless assertions from some journalists, this is not Huawei’s first attempt at contributing to the kernel, in fact they’ve been a frequent contributor for some time.

Wasn’t Huawei trying to put a Backdoor into linux?

as far as i know, that has not happened.

what makes you think it did?

After a minute of research I’m inclined to believe Godzilla egg-laying only happened in Roland Emmerich’s 1998 film.

Here is some contemporary reporting about it: https://www.chicagotribune.com/1998/05/19/godzilla-lays-an-egg-does-this-surprise-you/

Big, buff and bodacious, he’s so cool he can even reproduce himself–or herself. Turns out, Godzilla’s a hermaphrodite.

Consistent with the mythology, this giant lizard is a mutant by-product of nuclear radiation. As the only member of its species to have survived a bomb test in French Polynesia, Godzilla must assume male and female reproductive functions to maintain the lineage.

Why Godzilla feels compelled to travel all the way to Manhattan to lay its eggs is a mystery not clearly explained in the script, but, like any Sinatra fan, the monster probably thought, “If I can make it there, I’ll make it anywhere.” So, it was off to New York, New York, where–like the Knicks–the creature lays a lot of eggs in Madison Square Garden.

see also: https://fictionhorizon.com/how-does-godzilla-reproduce/