cookiecaper

Actual link is https://github.com/openzfs/zfs/pull/15022#issuecomment-18024... but HN's dup detection links to a story from 83 days ago. @dang et al, would be nice to consider anchor text in the duplication feature for such occasions.

If you have a USB OTG dongle, try plugging in a USB mouse and/or keyboard and accepting the ADB keys / enabling USB debugging that way. I have successfully recovered damaged phones for family members that way.

It's hard to blame the average passerby for harboring contempt for TikTok. I joined at one point and the content they show "brand new" accounts trends extreme. I assume they do it to find the edges of the new users' comfort zone, but I don't blame anyone who takes one look and says "eff this". My feed got much more tolerable after a few days of periodic swiping, but I uninstalled it a long time ago and have no interest in returning.

GitLab CI is definitely competitive with GitHub Actions. What's the specific feature set you're missing? "Polish" is pretty vague, especially in the context of a post that laments GitHub Actions' poor uptime record.

It's probably a good idea because some GitHub browser extensions will automatically hide forks from search results, under the assumption that basically all "forked" projects are drive-by patchjobs. I'm not sure this is stopping anyone who would be useful to OpenBrush, but maybe it is.

Another good reason to defork is that, as we saw with the youtube-dl fiasco, there are some non-software-related reasons that MS may feel inclined to offline the entire fork tree. That'd be the bigger concern for me.

Got a Quest2 last July, right around time that Google was killing their Icosa-type-thing.

OpenBrush was imo one of the best apps for it and I wanted to start playing around with the code, but had some friction even getting a build started and eventually lost interest. Installed several SideQuest builds, of course, but after I couldn't get a working distributable with built-in Icosa even all the way into September, I got annoyed and I haven't started the app or looked at the project since.

Just getting the Oculus dev env set up to the half-assed extent I did, it's risky, dubious, and feels bad. I never know which agreement I might accidentally click that'll allow Zuckerberg to Quest2 into my house backwards, or whatever.

I guess this is probably a lot less helpful than I thought it would be when I started typing. Sorry!

The problem is that those are two highly correlated data points. Toxic bosses are eventually found but at that point they leave a track of dead bodies.

Agree, and this is often overlooked. There's a handful of people I used to admire whose tendency to readily believe whatever's being sold by their middling middle management chain has left me deeply disappointed.

Middle management is a necessary evil, but there's little hope if upper management fails to recognize and subvert its inherent incentive structure.

Ethereum's history clearly demonstrates the folly of "code as law". How many hard forks have they had by now?

"(Personal|Professional|Performance) Improvement Plan". It's the first formal stage in the firing process at most companies with HR depts, which would almost certainly include any publicly-listed company.

If you're at the PIP stage, it generally means your boss and your superboss have decided that it's time for you to go, but for legal purposes, they need to look like they tried to give you a chance, so they work with HR to craft specific-but-typically-unattainable goals which would theoretically allow you to save your job if you hit them all. But with boss+superboss already wanting you gone, the likelihood that they'll agree you've hit an improvement goal that's usually a thinly-veiled form of "stop me from hating you anymore, lol" is pretty low.

If you get a PIP, in nearly 100% of cases, you should just take it as notice that your employment is going to end at the specified review date in the PIP. It's not usually worth trying to hit the goals. Focus on interviewing.

That said, I once managed an individual who had survived 4 PIPs by the time he reported to me. I heard that he was eventually fired about 2 years after I left, but not sure if it was his 6th or 7th PIP. He was a particular discrimination liability at a company that was very sensitive to that type of thing.

It sounds distasteful only because the vast majority of bosses out there aren't worthy of the mantle. An individual's relationship with their immediate boss is one of those intimate things in life and it deserves sanctity.

Help your people and don't be a dick and you'll be amazed at the bounty of unearned gratitude that comes back around -- and often not just once, but continuing for years. Being a good boss is "the gift that keeps giving" to good bosses everywhere.

Up-up-Ctrl+K to kill the line; down to go down one in the history; end to go to end of line; `; and` or ` &&` to join the commands; ctrl+Y to yank the line from the killring. [0]

Seems to work in bash too, fwiw.

[0] https://fishshell.com/docs/current/interactive.html#copy-and...

Try it for yourself: https://rootnroll.com/d/fish-shell/

Kodi is awesome, but every time I try to use it on a set-top box-type thing, it promptly consumes the entire available storage. I'm going to have to concoct some type of just-in-time mini-library so that these things don't get overeager with posterization, indexing, artwork, etc., but still allow me to use them to watch things essentially on-demand. Sounds efforty so I just won't.

You have to put it in a library that's classified as "Other", and then it will show all video files it's capable of playing as regular media without necessarily requiring you to descend into the folder hierarchy view. I have several thousand home videos, YouTube downloads, and other "custom content" that's handled this way.

Jellyfin doesn't run on FreeBSD because .NET doesn't run on FreeBSD. This is sad.

No matter what anyone tells you, there is zero evidence that any part of the virus is engineered (and it isn't even entirely clear what such evidence would look like, in general!).

I'm not a biologist so I don't really know what any of this means, but there seems to be debate around the presence of a "furin site" [0], which apparently could have emerged naturally, but also could have been artificially spliced in the course of gain-of-function research. Is that how GOF research is normally conducted? I don't really know anything here, but at least some people believe there are genetic markers indicating potential lab manipulation, thus adding another datum in the long list of circumstantial evidence.

[0] https://threadreaderapp.com/thread/1266805310313967617.html

Utah is great, but don't come here. We want CA problems to stay in CA.

Yeah, git is really not a mature or well-designed VCS. The fact that you can trivially lose the supposed permanent reference -- and that it's encouraged as part of several common workflows at that -- should be more than enough to demonstrate this. If you care about history, use a VCS like Fossil.

Yeah, I started working at a place where 90%+ of the production codebase is actively-maintained Perl, and it honestly feels great.

These guys might have a hard time fitting a recruiter's definition for a "rock star" but they're the best set of colleagues I've had in a very long time, and that's after working at multiple flashy tech companies.

Long live Perl. We can only hope to get another generation of programmers as committed and useful as the people who still write Perl every day.

Firefox's tools are still competitive with Chrome and there are even a few things I miss about them when debugging in Brave. It gives a little joy to know that Mozilla is still competitive in something, but not holding my breath for it to stay that way.

Gecko is already effectively lost -- the groups doing cutting-edge work were cut back in August. We're just watching the implosion.

I switched from Firefox to Brave in October and suggest others do the same. Personally, I believe Brave would indeed "deep-fork" the Chromium codebase if necessary, and I'd guess there's a significant chance that other Chromium-based browsers would use it in preference to a submarined upstream.

The layoffs last summer tell us all we need to know about the direction Mozilla's headed. I think they're toast. Brave and -- dare I say it? -- even Edge have brighter prospects.

This is where independent resellers via Shopify, their own cart system, etc. have a chance. There's no way to be sure you're getting a real battery from Amazon so I always buy this type of thing from a community-trusted independent vendor that has a real account with authorized suppliers.

It might cost more in shipping and delivery time, but it's strongly preferable to having my desk catch fire due to missing or defective safety components, which are very common among knockoffs. At least there's someone to sue if that happens with an authentic battery.

Containers are not intended to be a security boundary -- functionality along those lines has been gradually backported as maintainers realized that nobody was going to care when they said "don't use these as a security boundary".

There's a world of difference between the amalgamation of hacks that comprise cgroups and something like BSD jails, which are and afaik always have been intended to be a security boundary, which implements real first-class kernel isolation for jailed processes, not just another subtree under proc that provides some direction to the kernel around resource consumption/priority and relies on UID/GID hacks to control access.

It's a difference in the community's engineering values. JavaScript devs pull in a dependency for virtually everything, whereas Python distributes an extensive standard library with the language. It's less important that the same thing is hypothetically possible in both communities and more important that specific communities have chosen to use similar toolkits differently.

Do note that you can unintentionally expose data to the BigCo too -- Home-Assistant and I'm sure the other platforms can export all local devices to Google/Amazon to allow control via Assistant/Echo and will send entity state updates to facilitate that.

Fossil is great, highly recommended.

It already exists and it's used to kill startups every day (including mine). Google gets a pass because they're real special. See Perfect 10 v. Amazon.

Scraping an unwilling system is already essentially illegal, there's a long case history on this. It's only recently starting to change (via pure judicial activism) in HiQ v. LinkedIn. As written, the CFAA allows anyone to make a felon out of a persistent scraper.

I'm not a lawyer but afaik the DMCA takedown process is prescribed by statute, and platforms must comply to qualify for the legal protections that make hosting user-generated content possible.

Friedman would certainly be removed by Microsoft if he jeopardized GitHub's legal protections by defying the mandated process, to say nothing of the potential of creating personal legal liability, both criminal and civil.

youtube-dl remains freely available off-GitHub (not to mention on the local disk of anyone who ran `git clone`). I just used it 10 minutes ago. There is no public good served by defying the law here, and there is no reason to put the whole kit and kaboodle on the line over it.

tl;dr, ignoring the DMCA process isn't just a "somewhat risky move". If we're going to break out the pitchforks, let's at least point them in the right direction: write your Congresscritters and tell them you want to see copyright law reform.