Wireless devices let me use 2 different tables and an armchair+TV. That would simply not be an option otherwise.

The benefits of going wireless vastly outweigh an occasional connection annoyance to me. And worst case I can still plug them in.

Ctrl-X Ctrl-V in micro, if you appreciate a sane editor with sane keybindings.

Physical connectivity comes courtesy from an RJ45 socket, a pair of USB-A ports, a sole USB-C connector, a microSD slot, and an HDMI connection

wasn’t expecting that

this guy doesn’t smile for the camera

this is what I’m talking about, Pete. It’s for your own good. This obsession with gathering data has to stop.

as opposed to human-generated code

Scientists using macs connecting to servers and other machines running Linux.

Unknown share is high too; Linux usage on desktop in Antarctica could be as high as 15%.

Exactly. A few months ago the headline was a patent of Roku hijacking HDMI to show ads.

I’ll save my energy to be pissed off when this garbage actually makes it to market.

sus

why would you lie

Well, not far off

Pete adopted the stage name “Megan Thee Stallion” after she was called a “stallion” during her adolescence due to her height (5 ft 10 in (178 cm))[7] and “thicc” body frame;[10] voluptuous, statuesque women in the southern United States are sometimes colloquially called “stallions”.[1]

is that really a thing for unit files? Why the hell a comment needs escaping?

HeliBoard has it for some time now

object-disoriented

I’ll steal this to shit talk about code; until git blame points to my past self

from their actual report

As long as one fork exists, any commit to that repository network (ie: commits on the “upstream” repo or “downstream” forks) will exist forever.

   This further cements our view that the only way to securely remediate a leaked key on a public GitHub repository is through key rotation. We’ve spent a lot of time documenting how to rotate keys for the most popularly leaked secret types - check our work out here: howtorotate.com.

I’ve seen a post today reach -17 in one community and +23 in another at the same time, so don’t stress about it

a problem that is documented is obviously a feature

The takeaway is to not use forks if there are changes you want to keep private.

I don’t think you can create private forks from public repos (the fork is public upon creation). This is more like the opposite:

If there’s a private repo that is forked and the fork is made public, further changes to that original private repo become public too, despite the repo remaining private and the fork not being synced.

wat