• 0 Posts
  • 429 Comments
Joined 10 months ago
cake
Cake day: January 2nd, 2025

help-circle
  • Exactly, keeping components separated, especially the router.

    Hardware routers “cost money because they save money” (Sorry, couldn’t resist that movie quote). A purpose-built router will just run and run. I have 20 year old consumer routers that still “just work”. Granted, they don’t have much in the way of capability, but they do provide a stable gateway.

    I then use two separate mesh network tools, on multiple systems. The likelihood of both of those failing simultaneously is low. But I still have a single failure point in the router, which I accept - I’ve only had a couple outright fail over 25 years, so I figure it’s a low risk.


  • Separate devices provide reliability and supportability.

    If your all-in-one device has issues, you can’t remote in to maintain it.

    Take a look at what enterprises do: redundant external interfaces, redundant services internally. You don’t necessarily need all this, but it’s worth considering "how do I ensure uptime and enable supportability and reliability? ".

    Also, we always ask “what happens if the lone SME (Subject Matter Expert) is hit by a bus?” (You are that Lone SME).






  • Onomatopoeia@lemmy.cafetoMemes@sopuli.xyzAdmire the passion
    link
    fedilink
    English
    arrow-up
    1
    ·
    12 days ago

    American cheese is fine, don’t conflate the real cheese (which is just Swiss without aging or bacteria) with Kraft American Cheese Food product.

    I’ve had American cheese that wasn’t the processed thing most people think of, just a cheese made from dairy, like any other cheese.

    The problem is in labeling - since American cheese can be anything from real cheese to the processed stuff, people don’t know what they’re getting unless they know the producer.





  • Onomatopoeia@lemmy.cafetoMemes@sopuli.xyzAdmire the passion
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    12 days ago

    Sadly most people only know mayo from a jar, and then it’s all the crappy brands.

    There are like 3 or 4 brands of mayo that have any flavor (Hellmann’s, Best Brands, there’s one from the southeast that I can’t recall, etc).

    Once you make your own in 5 minutes (for about 75¢), you realize how weak store-bought stuff is (for $5).






  • Much of this stuff is automatic - I’ve worked with such contracted services where uptime is guaranteed. The contracts dictate the terms and conditions for refunds, we see them on a monthly basis when uptime is missed and it’s not done by a person.

    I imagine many companies have already seen refunds for outage time, and Amazon scrambled to stop the automation around this.

    They’ll have little to stand on in court for something this visible and extensive, and could easily lose their shirt with fines and penalties when a big company sues over breech when they choose to not renew.

    Just cause they’re big doesn’t mean all their clients are small or don’t have legal teams of their own.


  • I just added a 30mm case fan to my SFF. I went with a compressor style given the space constraints and restrictions (they tend to draw more current because of the load).

    It increased draw by <1 watt - it barely registers on the meter.

    I don’t think fans really make much difference. My 120mm compressor is 4w on the label (which is peak load, like startup). It probably drops back to 1/2 W after startup. And that’s a huge fan in a compressor style, equivalent to a 200mm+ in a conventional fan.


  • Yea, it’s the end of the world with Signal.

    Having such a dependcy just exposes yet another way their story doesn’t add up, like dropping SMS support because of engineering costs. Apparently, SMS is so hard to do there are free SMS apps.

    I can’t trust them at this point.

    And how does E2E require a middleman?

    More like it’s their store-and-forward servers. Why that’s on AWS, or more importantly not distributed with auto fail over is a major fail, as in “get fired” failure.