aspiring Rustacean, JavaScript jockey, 3D printing addict, use Bluefin Linux, (Apple|Google)-captive, Meta-escapee, parent, husband with a husband, cisgender, he/him

  • 3 Posts
  • 24 Comments
Joined 5 years ago
cake
Cake day: April 6th, 2021

help-circle

  • interesting, i wasn’t prompted or anything, from the documentation there’s the ollama/ollama:latest image and the ollama/ollama:rocm image but either way ollama will do its own detection and silently fallback to CPU if anything even smells wrong, haha

    i’ve noticed a few people are not using the official ollama images 🤷






  • oh, sorry, now I understand the question

    yes, devices available in CrowdSupply tend to philosophically align with my values: owner is in charge, no subscriptions, cloud connectivity is not a thing or completely optional, schematics are open, drivers are open, etc

    so they aren’t usually interfered with at a functionality or technological level

    but they’re popularity and availability are subject to interference: we’ve already had multiple governments ban or consider banning the Flipper Zero for various reasons

    and we have various media codec patents and DRM requirements that prevent truly open devices from being able to be used for popular purposes like streaming video content which pretty much guarantees that only industry-approved devices will ever gain wide distribution and popularity

    I don’t think it’s too tin-foil hat to suggest that if a truly open device did gain popularity somehow, that we’d see IP lawsuits or import restrictions or mandatory modifications (e.g. countries attempting to mandate a government-operated surveillance app preinstalled on over smartphone)






  • jokeyrhyme@lemmy.mltoLinux@lemmy.mlWhere can I find Wayland solutions?
    link
    fedilink
    English
    arrow-up
    12
    arrow-down
    1
    ·
    2 months ago

    to help communicate and troubleshoot what is broken here, we need to think of Wayland as a protocol just like HTTP is a protocol

    saying “Wayland broke X” is like saying “HTTP broke X”, which is possible but not likely to be what you’re actually trying to say

    rather, we need to be talking about the implementation(s) of the protocol, not the protocol itself

    e.g. “HTTP broke X” -> “Google Chrome broke X”

    e.g. “Wayland broke X” -> “GNOME broke X”



  • thanks, i hadn’t actually heard of ntop / ntopng before!

    i believe ntopng works everywhere independent of whether calico is installed or not (and even calico is a Kubernetes-compatible and Kubernetes-optional system, just like ntopng)

    but, calico whisker displays networking information made available by the rest of calico, so it’s able to give you a live display of when a firewall rule managed by calico is allowing or blocking traffic

    i think this particular feature is absent from ntopng, but i could be wrong





  • jokeyrhyme@lemmy.mltoLinux@lemmy.mlOpen source smart watches
    link
    fedilink
    English
    arrow-up
    4
    ·
    4 months ago

    This probably depends on what you mean by “smart”

    In the old days, dumb phones were defined as devices that shipped with a set of features with users generally being unable to add new features themselves

    And smart phones could be extended by users because they allow installation of apps, etc

    But I don’t think this applies to smart watches: it seems like the difference here is that a smart watch goes beyond “dumb” by having phone/internet connectivity to display more than just times and dates