it’s more likely they’re a regular-sized linux user and it’s only their inflatable penguin which is giant

It’s free software which you can host yourself. The source is here (GPLv3). You can read more about the people that make it here: https://en.wikipedia.org/wiki/Framasoft

This add-on is not actively monitored for security by Mozilla. Make sure you trust it before installing.

It’s pretty lame that Mozilla’s addons site still doesn’t show source code which is guaranteed to correspond to the binary you’re installing.

Anyway, I went and read the source on github (which probably corresponds to the extension one can install) and while this part seems very straightforward this other part exceeds my understanding 😂 (i’m not suggesting it is malicious, i just don’t understand everything it is doing there or why it is necessary).

What I was really looking at the source for was to see if they were simulating keystrokes (and inserting plausible delays between them) to defeat a more determined anti-pasting adversary, or if they were simply suppressing the hostile website’s onPaste handler so that pastes can happen as normal. And: they are doing the latter.

I wonder if any paste-blocking websites detect and defeat this extension yet?

I can think of two ways: either using a password manager with a browser extension, or using the browser’s built-in one.

bonus: make it something easy to remember, like your year of birth

(disclaimer: this information might be years out of date but i think it is still accurate?)

SSH doesn’t have a null cipher, and if it did, using it still wouldn’t make an SSH tunnel as fast as a TCP connection because SSH has its own windowing mechanism which is actually what is slowing you down. Doing the cryptography at line speed should not be a problem on a modern CPU.

Even though SSH tunnels on your LAN are probably faster than your internet connection (albeit slower than LAN TCP connections), SSH’s windowing overhead will also make for slower internet connections (vs rsync or something else over TCP) due to more latency exacerbating the problem. (Whenever the window is full, it is sitting there not transmitting anything…)

So, to answer OP’s question:

• if you want to rsync over SSH, you usually don’t need a daemon (or to specify --rsh=ssh as that is the default).
• if you the reason you want to use the rsync daemon is performance, then you don’t want to use SSH. you’ll need to open a port for it.
• besides performance, there are also some rsync features which are only available in “daemon mode”. if you want to use those, you have at least 3 options:
  • open a port for your rsync daemon, and don’t use SSH (bonus: you also get the performance benefit. downside, no encryption.)
  • setup an SSH tunnel and tell the rsync client it is connecting to a daemon on localhost
  • look at man rsync and read the section referred to by this:

    • The remote-shell transport is used whenever the source or destination path contains a single colon (:) separator after a host specification. Contacting an rsync daemon directly happens when the source or destination path contains a double colon (::) separator after a host specification, OR when an rsync:// URL is specified (see also the USING RSYNC-DAEMON FEATURES VIA A REMOTE-SHELL CONNECTION section for an exception to this latter rule).

HTH.

deleted by creator

💯

or, possibly: d) all of the above

Hikarunix

big oof.

We can conclude: that photo isn’t AI-generated. You can’t get an AI system to generate photos of an existing location; it’s just not possible given the current state of the art.

the author of this substack is woefully misinformed about the state of technology 🤦

it has, in fact, been possible for several years already for anyone to quickly generate convincing images (not to mention videos) of fictional scenes in real locations with very little effort.

The photograph—which appeared on the Associated Press feed, I think—was simply taken from a higher vantage point.

Wow, it keeps getting worse. They’re going full CSI on this photo, drawing a circle around a building on google street view where they think the photographer might have been, but they aren’t even going to bother to try to confirm their vague memory of having seen AP publishing it? wtf?

Fwiw, I also thought the image looked a little neural network-y (something about the slightly less-straight-than-they-used-to-be lines of some of the vehicles) so i spent a few seconds doing a reverse image search and found this snopes page from which i am convinced that that particular pileup of cars really did happen as it was also photographed by multiple other people.

🥛🤝🦆

(it’s odd that PBS is promoting this, as it is actually a terf movement)

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” ? 🤔

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.

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.)

404 Media neglected to link to her website, which is https://ada-ada-ada.art/