All about me. My Bio.

  • 2 Posts
  • 29 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle







  • 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.







  • Depends a lot on your existing reverse proxy.

    You can read the nginx config that the defaults include and it’s some basic rules to route incoming requests to either lemmy or lemmy-ui. If your existing reverse proxy is nginx you could just incorporate the rules in there.

    It also depends on why you need it behind the existing proxy, and how you’ll choose to route your traffic, and where you traffic is coming from in general.

    I’d start with taking a look at the default nginx config to see if you can move those rules to your existing reverse proxy, or just forward everything coming in that’s for lemmy straight to the lemmy reverse proxy, although that might be more complicated in correctly preserving the incoming requests.


  • Many years ago working for a monitoring software company someone had found a bug in the uptime monitoring rules where they reset after a year.

    It was patched and I upgraded one client and their whole Solaris plant immediately went red and alerted. They told me to double it to two years and some stuff was still alerting.

    They just said they’d try to get around to rebooting it, but it was all stable.

    Everywhere else I’ve worked enforces regular reboots.







  • 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.