• 0 Posts
  • 377 Comments
Joined 3 years ago
cake
Cake day: June 16th, 2023

help-circle



  • I’ve been watching halow for a while, I haven’t yet seen any sustainable, real-world examples beyond a few hundred kbps (not bytes). I have seen the 1Mbps results, and they’re promising, but most places with any other traffic in the free band is busy. If you have any successful and repeatable tests hitting at usable speeds, I’d love to see them.

    After getting into meshtastic and a few other lorawan projects, I’m a bit concerned that tests for these are always high and visible, which doesn’t work well in the mountains, even at shorter ranges.

    I used to be more hands-on with these new standards, but I’ll wait for better tests to come from halow before I try it out.




  • If you’re not fond of manipulating config files manually, just use nmcli (from your link):

    You can get an idea of NetworkManager’s settings by running nmcli on the command line.

    It is a bunch simpler. The days of just raw-dogging resolve.conf and nsswitch are long behind us.

    Aren’t these docs an admission that it’s a clusterfuck?

    The Debian wiki admittedly needs work, but it is a wiki, so make an account and update what you think is lacking or unclear.





  • non_burglar@lemmy.worldtoSelfhosted@lemmy.world•Immich Is Now Stable!
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    edit-2
    10 months ago

    OK, thanks.

    Not really that helpful, it’s just more he said/she said.

    Grapheneos is a pretty poor choice of example, it has its own issues, they have conflicts with many others (see France pullout), they have openly fought with Murena, e/os, fairphone, among others. Plus, grapheneos likes to throw shade on “less permissive licenses”, which is really weird, considering they use an MIT license, whose loose terms is abused by many not-so-great companies.

    The lead of grapheneos is just as controversial as futo, gets into public spats with others, generally difficult to work with, etc.

    I say this using GrapheneOS myself.

    I’m not a fan of the Curtis Yarvin association, though.

    The people running these companies aren’t perfect. Sometimes they aren’t ideal, either. But I’d rather use Immich than Google photos and heliboard than Swiftkey.









  • APIs. Or the ends are achieved by sharing data between apps in common data storage. But I prefer to be a tourist in my infrastructure, I no longer hand-bomb changes to systems.

    My design pattern is essentially to integrate more and more of the container creation into config. Right now I’m using ansible and it’s nice. More automation means troubleshooting has fewer variables.

    I had issues yesterday with a package upgrade across several containers, and it ended up being two config changes. I cycle the apps and done. That’s it.