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/)C
Posts
2
Comments
635
Joined
3 yr. ago

  • I think there is a much stronger argument for tech businesses being forced to finance and support FOSS. They are the ones directly benefiting from the free work.

    Not a clue how to force that though, would probably need to be via some form of regulation. I can't think of any good way to do it without leaving gaping loopholes for abuse. :(

  • You'll definitely get lots of login attempts. I used to have a port 22 ssh, hundreds of attempts per day.

    Would be interesting to see what post login behavior was.

  • Wanna bet they expose SSH on port 22 to the internet on their "critical" servers? 🤣

  • Sure, but the author makes it sounds like thats its their standard way of doing things, which is insane.

    And if you do have a misconfiguration, the rational thing is to fix that, not dump the entire platform.

  • If the hypervisor or any of its components are exposed to the Internet

    Lemme stop you right there, wtf are you doing exposing that to the internet...

    (This is directed at the article writer, not OP)

  • Thanks to AUR, I haven't manually run a autoconf build in years, but I remember them being very fiddly. Lots of "google for header file, install and retry".

    I think maintainer burn-out somewhat contributes to the hostile approach some projects have, anything that is accepted into a project needs to be maintained and comes with a risk of being broken in the future. If the original committer isnt around, then the maintainers either have to take on that burden, or remove it.

    Its a tough cycle to break, I don't know what the answer is.

  • You're not wrong. Ive had all those experiences as well :(

  • Lol, its an Octoprint plugin, and I already rewrote half of it to Rust, but the other half is going to be Python as long as Octoprint is.

    I'd be happy for someone to fork and/or rewrite it :)

  • In my (very limited) experience, even getting contributions is near impossible. Lots of people like to open issues, far fewer like to work on solving them.

    Add in xz, and my package will likely die with me (which is fine, its not critical, and I have a few decades left)

  • AI just let's script kiddies churn out garbage faster. I've yet to see better code as a result.

  • The malware argument is a bit weak, if your router is vulnerable to something it'll likely be found and pwnd in a matter of minutes, so turning it off a night won't really save you. And once a patch is released, it'll be reverse engineered in a few hours/days, so ideally you want patches as soon as they are released.

    Using your own device is usually a good idea anyway, telco stuff is usually pretty mediocre. And as soon as your device is slightly custom, it becomes a less valuable target.

  • I think its better to keep your gateway basic, and run extra services on a separate raspi or similar. Let your router/gateway focus on routing packets.

  • Openwrt can run Adguard, and as long as your gateway can run docker, you can probably get pihole working.

  • Sure, except we are defenceless to the rampant dropbears. /s

    Australia is a funny example for gun control. Yanks seem to think we have no guns at all, but the reality is that as long as you are mentally sound and store your guns safely, they aren't that hard to get.

  • I thought that was the case tbh, has it changed?

    Edit: is-even depends on is-odd.

  • Is-even and is-odd on npm.

    For a while, openssl was maintained by 1 or 2 people.

  • Did the services fail to come back due to the bad reboot, or would they have failed to come back on a clean reboot? I ugly reboot my stuff all the time, and unless the hardware fails, i can be pretty sure its all going to come back. Getting your stuff to survive reboot is probably a better spend of effort.

  • I'll stick with git commit . -m "stuff" /s

  • I've heard of it, and don't know what the point is.

    In zigs defence, I felt the same way about rust a few years back as well.

    I wonder what the killer feature for zig is. At least rust promises safer code, what does zig promise?