Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)ST
Posts
18
Comments
87
Joined
2 yr. ago

  • That's a super valid question, as it seems sometimes that some of these things are configured in a way that begs the question "why?" As far as contributing to documentation, that's a moot point. This is already in the man pages, and that's exactly what I referenced in writing this post, in addition to some empirical testing of course. As far as implementation goes, I think that probably lies at a per distribution level, where not one size fits all. Although I don't know of it off the top of my head, I'm sure there's a security centric distro out there that implements more of these sandboxing options by default.

  • Linux @lemmy.world

    Systemd Service Hardening

    Selfhosted @lemmy.world

    Systemd Service Hardening

  • The primary thing is rather than "dumb" flood routing, you can choose the path your message takes to its destination; as a repeater operator you can also choose the path it takes to repeat out. Its a slight compensation to people carelessly placing infrastructure nodes with poor configurations in poor places. Not perfect, but better. Adoption is much, much lower though, and the licensing is not copyleft.

  • That's a great question!

    No, blocking a node -- router or other -- will only block packets originating from that node. All traffic that is forwarded by that node, but originating from others will still be received.

    Ultimately, the only place that blocking nodes strategically makes sense is on high utilization routers. If you're just blocking nodes on a client, it's not changing channel or airtime utilization for the rest of the mesh. That said though, if someone is harassing you then a block on a client is still fully worth it. 🙂

  • Meshcore does address some of the biggest shortfalls of Meshtastic, but I absolutely HATE that they're positioned to either rugpull, or setup a perpetual "freemium" model. It's also not interoperable, so if Meshcore is to work, it needs the numbers like Meshtastic has.

  • Yeah, so far the most prevalent thing around my area has been "it's a hobby for the sake of being a hobby." No one does anything terribly useful or important with it. I can tell you that I would certainly never rely on it as a form of emergency communication.

  • Selfhosted @lemmy.world

    Self-host Meshtastic Metrics in Grafana

    Meshtastic @mander.xyz

    Self-host Meshtastic Metrics in Grafana

  • It's not about user-led synergy. The personal data market is slurped up by those that already have and are building correlations. Just because a user didn't report anything to their insurer doesn't mean an insurer sure as shit isn't going to want the data if they can link it to the user whatsoever, so long as it will make them more money.

    This is hypothetical, of course, but it's the way the market of data brokers works.

  • You joke, but I guarantee there's a market. Consider health insurance companies that see an opportunity to charge everyone more unless they can prove their good brushing habits via app data.

  • Yes! Qsl cards are very much still alive and well. Some traditions will never die. The special event stations are fun to get cards from.

    Super cool anecdote on the telescope thing, I've never heard of that.

    I hope you get back on the radio, it's a great hobby. It's a nice stress relief outlet for me these days too.

  • Selfhosted @lemmy.world

    Monitor your AREDN Node with Prometheus and Grafana

    Amateur Radio @lemmy.radio

    Monitor your AREDN Node with Prometheus and Grafana

    Cybersecurity @sh.itjust.works

    Intercept and Monitor TLS Traffic with mitmproxy Using Podman - Infosec.Pub

    Selfhosted @lemmy.world

    Intercept and Monitor TLS Traffic with mitmproxy Using Podman

    Tailscale @programming.dev

    Leveraging Authelia for OIDC Single Sign-On (SSO) with Headscale

    Selfhosted @lemmy.world

    Leveraging Authelia for OIDC Single Sign-On (SSO) with Headscale

    networking @sh.itjust.works

    Monitor Your Network the GPL Way with LibreNMS

    Selfhosted @lemmy.world

    Monitor Your Network the GPL Way with LibreNMS

    Selfhosted @lemmy.world

    Monitoring OPNSense Logs with Grafana Loki (Part 2)

    OPNsense @lemmy.world

    Monitoring OPNSense Logs with Grafana Loki

    Selfhosted @lemmy.world

    Monitoring OPNSense Logs with Grafana Loki

    GrapheneOS @lemmy.sdf.org

    5g issues on mint mobile pSIM

    Selfhosted @lemmy.world

    How to Host Headscale on a Linux Server with Podman Quadlets (Part 2)

    Selfhosted @lemmy.world

    Traefik with Socket Activation via Podman Quadlets