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/)N

nottelling

@ nottelling @lemmy.world

Posts
2
Comments
145
Joined
3 yr. ago

  • The ability for Fediverse apps to interact with each other is the least interesting/useful feature of the Fediverse.

    Jump

  • It just seems like cross-posting with more confusing terms for normal people.

    What I'd really like is one single sign-on for everything that was federated to my original Fediverse service instance. I should be able to just go to some Pixelfed/Mastodon/Lemmy/etc instance, log in with @nottelling@lemmy.world and I'm just magically makes me a user there. (Assuming instance permissions and federation settings and such, of course.)

    I get it, account management and implied trust is hard to do. But that's what this feature should be.

  • low power switch

    Jump

  • How "stable" (release cycle) does a server OS need to be? Experiences with CoreOS?

    Jump

  • Yup. Treating VMs similar to containers. The alternative, older-school method is cold snapshots of the VM, apply patches/updates (after pre-prod testing & validation), usually in an A/B or red/green phased rollout, and roll back snaps when things go tits up.

  • ssh into raspberry without a router

    Jump

  • How "stable" (release cycle) does a server OS need to be? Experiences with CoreOS?

    Jump

  • If you are in a position to ask this question, it means you have no actual uptime requirements, and the question is largely irrelevant. However, in the "real" world where seconds of downtime matter:

    Things not changing means less maintenance, and nothing will break compatibility all of the sudden.

    This is a bit of a misconception. You have just as many maintenance cycles (e.g. "Patch Tuesdays") because packages constantly need security updates. What it actually means is fewer, better documented changes with maintenance cycles. This makes it easier and faster to determine what's likely to break before you even enter your testing cycle.

    Less chance to break.*

    Sort of. Security changes frequently break running software, especially 3rd party software that just happened to need a certain security flaw or out-of-date library to function. The world has got much better about this, but it's still a huge headache.

    Services are up to date anyway, since they are usually containerized (e.g. Docker).

    Assuming that the containerized software doesn't need maintenance is a great way to run broken, insecure containers. Containerization helps to limit attack surfaces and outage impacts, but it isn't inherently more secure. The biggest benefit of containerization is the abstraction of software maintenance from OS maintenance. It's a lot of what makes Dev(Sec)Ops really valuable.

    Edit since it's on my mind: Containers are great, but amateurs always seem to forget they're all sharing the host kernel. One container causing a kernel panic, or hosing misconfigured SHM settings can take down the entire host. Virtual machines are much, much safer in this regard, but have their own downsides.

    And, for Debian especially, there’s one of the biggest availability of services and documentation, since it’s THE server OS.

    No it isn't. THE server OS is the one that fits your specific use-case best. For us self-hosted types, sure, we use Debian a lot. Maybe. For critical software applications, organizations want a vendor so support them, if for no other reason than to offload liability when something goes wrong.

    It is running only rarely. Most of the time, the device is powered off. I only power it on a few times per month when I want to print something.

    This isn't a server. It's a printing appliance. You're going to have a similar experience of needing updates with every power-on, but with CoreOS, you're going to have many more updates. When something breaks, you're going to have a much longer list of things to track down as the culprit.

    And, last but not least, I’ve lost my password.

    JFC uptime and stability isn't your problem. You also very probably don't need to wipe the OS to recover a password.

    My Raspberry Pi on the other hand is only used as print server, running Octoprint for my 3D-printer. I have installed Octoprint there in the form of Octopi, which is a Raspian fork distro where Octoprint is pre-installed, which is the recommended way.

    That is the answer to your question. You're running this RPi as a "server" for your 3d printing. If you want your printing to work reliably, then do what Octoprint recommends.

    What it sounds like is you're curious about CoreOS and how to run other distributions. Since breakage is basically a minor inconvenience for you, have at it. Unstable distros are great learning experiences and will keep you up to date on modern software better than "safer" things like Debian Stable. Once you get it doing what you want, it'll usually keep doing that. Until it doesn't, and then learning how to fix it is another great way to get smarter about running computers.

    E: Reformatting

  • Has Google’s search results drastically declined for anyone else?

    Jump

  • It means if you search for anything, your first 3 pages of hits are the same useless websites that exist to push ads vaguely related to your search rather than real info. Trying to research a broken TV used to return things like AVForums or reddit threads or samsung support sites. Now it's "TEN BEST TV's IN 2024" that are nothing but sponsored content and affiliate links to tvs on amazon.

    Google can't figure out how to tell the difference between the former and the latter, and isn't motivated to because they get paid for the ad clicks, and not for the forum clicks.

  • How often do you contribute to open source projects?

    Jump

  • I actually want to learn enough code to contribute, but there's this gap between "how to code" and "how to participate in a modern software project".

    Like, I've created plenty of little things. Discord bots, automation scripts, plenty of sysadmin stuff for work, etc. But like, I clone a git repo cause there's a home assistant bug I'd like to fix for example, and I'm immediately lost on where to start.

  • I am genuinely horrified to see how much data google collected from me

    Jump

  • Everything they're willing to tell you they have on you.

  • Going through and hiding all of my entities. Painful process but making it easier to use in the future. @homeassistant is looking better and better each day. [#H

    Jump

  • Fair enough, just seems like a lot of work vs. 2 clicks on the filters.

  • Need help converting dumb switches; one w/o any lights, one w/ Hue bulbs

    Jump

  • You don't need to ground your Shelly if the circuit is otherwise properly grounded. The Shelly will fail open if something internal shorts.

    Per the rest of the discussion re: hot wire loops to switches with no neutral or ground, just put the Shelly into the upstream junction box. (Wherever the switch wire branches from the circuit. Usually that's where the light is.)

  • Going through and hiding all of my entities. Painful process but making it easier to use in the future. @homeassistant is looking better and better each day. [#H

    Jump

  • ... Why? They exist for a reason, the interface has filter and sort options.

  • Neo-Nazis march in Nashville, leave after being challenged

    Jump

  • Yeah, just make sure you don't make that known during jury selection or you won't get to help.

  • Neo-Nazis march in Nashville, leave after being challenged

    Jump

  • I think the thing in this case is that it is the job of police to pull over a box truck full of human cargo. The implication here is so you think they'd have let a truck they knew was full of immigrants just drive away?

  • Is there a FOSS/privacy oriented IoT community?

    Jump

  • Is there a FOSS/privacy oriented IoT community?

    Jump

  • No apology needed, one thing about security is that paranoia is good. One problem with security is that paranoia leads to assumptions and misinformation, rather than understanding.

    Symmetric key encryption is much faster than asymmetric, and can use much larger keys with less compute penalty. So we use acPU intensive asymmetric TLS handshakes to safely exchange the keys, and then switch to the faster method for the data.

    So when ZigBee use AES 128, you can be reasonably sure the data packets are safe. The next question to ask is "do they exchange their keys safely?"

    Which in this case would be "no" if you just leave the ZigBee controller in pairing mode all the time. However, you only allow pairing when you want it, and only pair with devices you explicitly allow. Unauthorized devices never get your network key.

  • Is there a FOSS/privacy oriented IoT community?

    Jump

  • That's fair, since it's possible these chips have some backdoored bootloader or something, I've never personally analyzed them with an electron microscope, but the architecture and wire traces are published, so you could start a chip fabrication plant and roll your own silicon.

    The actual running code on them is usually GitHub hosted though, or you can write it yourself and just import the libraries you need, again usually from GitHub or the platform specific repositories.

    If you're worried about Chinese chips in your open source though, I have some real bad news for you.

    If you're using FOSS specifically as a control against Chinese spying, and not analyzing the commit logs of every package you download, I have more bad news for you.

  • Is there a FOSS/privacy oriented IoT community?

    Jump

  • Your Https connections are also symmetric, so that's a silly thing to dislike.

    The handshake and key exchange are asymmetric, and used to establish a symmetric session key.

    ZigBee encryption is fine for the use case, because you're only adding devices you know are being added. You inherently trust that your physical ZigBee device is the device it claims to be.

    There's potentially an opportunity to hijack the key exchange between devices at network join, but you'd have to approve the listening device to your network in the first place.

    https://development.libelium.com/zigbee-networking-guide/security-and-data-encryption

  • Is there a FOSS/privacy oriented IoT community?

    Jump

  • There is an entire ecosystem of open SoC devices, code, platforms, development boards, etc. One of the most popular is the ESP32/8266 boards, which is a pretty good place to start.

  • Fox show hosts said Taylor Swift "should be conservative" given her background, because to them it's an identity.

    Jump

  • The problem is that plenty of smart people are conservative. Because conservatism is fundamentally a grift, and the smart ones use the dumb ones to get richer.

    Swift just has enough empathy to realize she's already rich.