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.
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.
curl ifconfig.io works too
I agree, that would be more authentic. Or rig up an actual line printer.
But I think the fuzzy old terminal emulator at full screen gives you a more accurate view of an old curved, flickery, low-res screen.
Event a TTY on a modern screen is going to be higher res (far more than 80x24), nice crisp fonts, colors, etc.
Should have used https://github.com/Swordfish90/cool-retro-term instead of gterm for the real flickery tiny terminal experience
One way is to run Pi-hole’s admin interface on a different port. That’s configured in:
Set:
Then your URL is http://IP:8000/admin