I worked out this was odd behavior on my OPNSense firewall NAT rules.

For some reason some syncing worked (eg. beehaw.org) but new connections failed. I’m not sure why. Maybe established sessions were kept alive.

Those rules haven’t changed in months and months, so I’ll chalk that up to “weirdness”.

Yeah, I’ve tried that a couple of times too.

And run through all the federation troubleshooting steps in the docs.

I thought that, and in the past I’ve been off for a day or two and always caught up.

This time I haven’t and it’s been a week or two since coming back online.

There’s always a way: https://www.youtube.com/watch?v=VhYEOG9LOIk

Last time my dishwasher died I just had to take it had and clean the pump underneath. Basically the connections apart under and had to just scrub them out. One tiny bit of plastic was gumming it up, causing some checks to fail. Stopped it running.

They’re surprisingly simple machines.

For Samsung I always buy the extended warranty. For our washer and dryer Assurion must have spent a fortune keeping them running. A lot more than I ever did to guy them. They’re only 8 years old too. It’s sad, but for Samsung they work nicely but fail frequently,

For your next one but Bosche. They’re all good, get a base model and it’ll clean well and reliably.

Given this is !privacy and the advertise as front page features both “works will all your messaging apps” and “end to end encryption”, it seems important to flag currently those aren’t mutually compatible.

It’s not their fault the apps don’t have e2e APIs, it’s a tough problem, but the secrecy and privacy guarantee is just “trust us to stick to our policy”. And they’re a start-up, tooling isn’t perfect (or even exist), mistakes happen, etc

Their self-hosting looks interesting, but then it said to use your own clients too, which took the fun out of that.

“For example, if you send a message from Beeper to a friend on WhatsApp, the message is encrypted on your Beeper client, sent to the Beeper web service, which decrypts and re-encrypts the message with WhatsApp’s proprietary encryption protocol.”

So, not really end to end for most common use-cases.

I don’t think it’s about lemmy.

https://www.militarytimes.com/news/your-military/2023/07/17/sensitive-us-military-info-exposed-in-accidental-emails-to-mali/

Needs the www:

https://www.castleholic.com/2020/01/the-wittelsbacher-ausgleichsfonds-or.html?m=1

I really don’t like the “but otherwise we’d need a warrant” approach.

Yes, of course you should need a warrant. That’s the bit that’s the safeguard and actually is the checks and balance against abuse. It’s not a problem to be optimized away.

Traditional lox is just brined in salt, no smoking.

Gravadlax is brined in salt and sugar with spices.

Smoked salmon is just smoked salmon, like nova, in the US.

Due to customer preference and lack of knowledge, most want smoked salmon when they ask for lox, so are sold lox.

See: https://forward.com/news/7669/the-raw-truth-about-lox/

Sounds like you need bevel gears.

https://www.grainger.com/category/power-transmission/gearing/bevel-gears

I’m with Gordon though. It’s easier to move the fitting than rig up gearing.

I’ve done this for years, but also:

• anything automated goes straight to specific folders for those categories. Very quickly identify stuff that’s noise and put in rules to move it out of your inbox. Sure some stuff you might need, but anything that’s corporate spam needs automating away.
• use (and create if necessary) the right mail groups so your whole team, project partners, whoever see the right emails and ask people to use them.
• add a VIP rule to highlight emails from the boss, VP, anyone you know you want to read right away
• be clear with people on how to reach you. If you prefer Slack for immediate stuff, tell people. It’s fine to be clear that email is for less immediate consumption, or non-conversational stuff. Slack is far better for collab.