My bootstraps broke when I pulled them harder.

Turns out the local company that made bootstraps for 125 years was bought out by a hedge fund, which promptly fired all of the workers and subcontracted manufacturing to a company in Sri Lanka who could make them much cheaper by using inferior materials and by paying the Sri Lankan workers in 6 months what a fired local worker made in a day.

Ironically, the hedge fund CEO with the MBA he received as a legacy admission to Cornell only wears slippers because fuck you, I’m the boss.

Canadian confirmed, eh.

This is the gonk I’m looking for

Ah, the rarely seen “narpyarp”

Borgbackup to Borgbase

An individual instance can be load balanced pretty easily, but that’s on the admin of that instance to implement.

Pfft - everyone knows you need a soul to get online

Yes. Lemmy 2FA uses SHA256 TOTP digests, which are newer (and better) than the SHA1 digests used as default by most authenticator apps.

Critically, Lemmy will not have you verify that the generated TOTP code works before locking it in, nor will it give you backup codes.

You should check the documentation of your authenticator app to see if any changes need to be made in the app prior to adding Lemmy 2FA.

If your app only supports SHA1, or you fail to follow your app’s procedures to add an SHA256 digest, and you add the 2FA token generated by Lemmy, you’re not getting back into that account.

Link to GitHub issue about this

Don’t worry about Phoenix - they’re always blue

Month 5: Sound not working again because you read about Pipewire on the Arch wiki

lemmygrad would like to know your location

Rapunki, when he joined the Seven

Seconding clonidine, especially for blood pressure. Also might want to check out ubiquinol (CoQ10).

After those, the only logical destination is TempleOS

CSS: Myhammy

I.E. Daddy IBM wants more

Having ADHD usually sucks, but at least I don’t ever have to worry about not learning, because it’s my brain’s absolute favorite thing.

ChatGPT-4 can use a search engine (Bing) via a plugin.

Thanks for the thorough writeup! It’s worth noting that the captcha will be back in the next version, but not exactly sure when it will be released.

They removed it during the switch from web sockets (which apparently took a lot of time and effort to keep updated), but someone submitted a pull request for a non-web socket version of the captcha code, which was accepted.

So hopefully we’ll all be able to update to the new version soon.

The dev apparently used the RedReader app to test a “spoofing” method of access for a proof of concept, but they don’t want to use that method either, because it would potentially cause problems for RedReader, which they didn’t want to do:

If we do that, and cause a huge traffic boost under RedReader’s name, it might lose them their exempt status. I’d like to avoid that if I can - there’s no reason to paint a target on RedReader’s back unnecessarily (an independent, non-commercial app), especially since the equivalent can be done with the official app without the same risks.

The real problem for Libreddit instance operators is going to be acquiring an API key. It doesn’t look like it’s an automated process like most other services - you have to fill out a form, which opens a ticket, and wait for someone from Reddit to get back to you.

I run an instance, and I’m not sure I want to go to the trouble. But I’ll wait and see what happens.