• 3 Posts
  • 4.22K Comments
Joined 1 year ago
cake
Cake day: September 21st, 2023

help-circle
  • Yep.

    I have an older frame that has an email option so people can send photos to the frame.

    I bought it because it supports both USB thumbdrive and connects to SAMBA shares for photos, too, which is how I use it. Never even signed up for the service, and I’ve blocked internet access for it (bastardin’ bastards designed the network stack to require DNS entries, picks).

    The setup is annoyingly clunky, but once setup it does work fine.

    My next one will start with a Raspberry Pi, then it’s just a generic Linux box.






  • Well before.

    And “refuse to change their ways” - are you going to underwrite the project to implement a transition and hold all the liability for the risks?

    Its not like changing systems is just a click of a button, this is an extensive project, that you better get right or you’re dealing with records going the wrong way, potentially having serious life and safety implications.

    Plus, you have to maintain this legacy fax system because not everyone else has migrated to something new. So for the remainder of your career, it still doesn’t go away, and you’ll have to continue to pay for its maintenance.

    Companies have systems they’ve built up over years, that works. They’ll move forward as it makes fiscal sense.


  • “embedded in many workflows”

    Key statement right there.

    And once people see what that really means, and what it would take to move past it (including time, cost, and risk), they may start to understand. You’re dealing with it first hand, so you know what’s involved.

    It became the de facto way to send stuff with high confidence it went to the right place. Then tech addressed the paper-to-paper over one phone line issue with modem banks into a fax server. So all the same fundamental comm tech (so fully backwards-compatible), but a better solution for the company with that infrastructure. Such a company has little motivation to completely change to something new, since they’d have to retain this for anyone that hasn’t switched. Chicken-and-egg problem, that’s slowly moving forward.

    It’ll be a long time before it’s gone completely. Perhaps in 20 years, but I suspect fax will still be around as a fallback/compatibility.






  • BearOfaTime@lemm.eetoAndroid@lemmy.worldGraphene vs LineageOS what's the diff?
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    1
    ·
    edit-2
    2 days ago

    Graphene is technically more secure than Lineage, because you can re-lock the bootloader.

    But wait, the latest versions of Lineage you can re-lock the bootloader on Pixel devices (or is it with DivestOS, a Lineage fork, on Pixels? I forget). Either way, both can be re-locked on Pixel (I know, I’ve done it).

    At that point there’s little difference in my opinion, if you aren’t using any kind of Google services.

    Once you go to use Google services (either sandboxed on Graphene, or microG on Lineage), it can be argued that Graphene is more secure. Though Lineage and Divest install microG as user apps, so you could install them to a second profile and isolate it there.

    But if you’re going to run some form of Google services, you’re kind of negating the advantages of Graphene at that point (though some would argue it’s still more secure, again, depending on your threat model - if a state actor is after you, don’t go putting Google stuff on your phone).

    Really it all comes down to your threat model. I’m currently running DivestOS on a Pixel with microG, because there were a few apps I still needed. My next reset (in about 3 months) that will be gone, and I’ll no longer need anything Google. But I’ll probably stick with DivestOS, as there’s no clear advantage for me to switch to Graphene.






  • I’d certainly use it more.

    I don’t hate Linux, I think it’s an amazing bit of kit. A brilliant idea to build a Unix-like OS for desktop hardware.

    The flexibility it has is astounding. The different distros really exposes this.

    This flexibility is also it’s Achilles Heel - no single UI to Rule Them All means it’s not approachable by the average user. The lack of standard tools in all distros means you have to add them, but which ones? (Of course this lack of tools means you can assemble a smaller, more compact, reduced risk-surface build for specific purpose).

    I currently run 3 or 4 different distros/builds for different purposes - Proxmox, UnRAID, Mint, Truenas, etc.

    The problem with Linux is the community. Us tech folks are (as a group) terrible at clearly documenting things in ways that address why someone would be reading docs, e.g. the minimalism of man pages that only show switches. That’s tolerable for man pages (or was 30+ years ago, when the only people using these systems were studious technical folks who had put lots of effort into learning the systems first), but most other docs today look just like them.

    Related, we’re also not great at working with people, often assuming they know what we know, so our answers tend toward only answering the very specific part of a question, rather than the bigger picture, e.g. “Use this command”, without explaining what’s going on, how this command addresses the issue, or even trying to understand what they’re actually trying to do. We tend toward efficient terseness.

    Just step into a business meeting with Senior Management and tech folks - the tech folks are gritting their teeth to get to the next thing, because in our minds we’ve already solved what management proposed, while management wants to spin the idea around seven ways to Sunday before they feel good about it. (Neither is “wrong” just different sets of priorities and responsibilities).

    TL:DR, Don’t hate Linux, we (the tech head community), are the problem.