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/)XA
Posts
3
Comments
1,144
Joined
2 yr. ago

  • I was skeptical but in the photos there's no injury to the side of his head. Just seems incredibly unlikely that a bullet would clip his ear and hit nothing else whatsoever. So yeah, an injury falling does seem kinda likely.

  • I read the damn ticket opened by mcc. I know about the non profit and I don't trust them with my personal information. Any place that captures valuable data is vulnerable to an attack in the form of financial corruption. I'll say it again, louder: If they have pure perfect morals now, you'll be pissed at them in 3 years because management has changed and money got involved.

    EDIT: IDK if lemmy has a remindme type bot, but we're gonna check back in on this one every so often so we can see how long it takes for them to sell out.

  • Well, yes. Except for the fact that advertisers now have an excuse to try more invasive things to get to their data

    They're going to do this anyway. As far as Firefox is concerned, it's the browser's job to stop them. That's what Firefox is selling: privacy

    because of they fumble it they are now an untrusted third party

    Assuming I take this for granted, they have already fumbled it by turning on an anti-privacy feature without consent. They can no longer be trusted. Not that you ever should have trusted them because whatever motivation they have for pure moral behavior now, that will change with the wind when more VC money gets involved, or there's been a change in management.

    And firefox has ALREADY had a recent change in management, which is probably why THIS is happening NOW. They just bought an adtech firm for pete's sake. Don't trust other people with your data. At all.

  • Completely facile argument, right there in the last sentence.

    We can keep fighting for something better while still accepting this as an improvement over what we have now.

    YOU BUILT THE FUCKING THING. Just turn it off and go away. Tada, we now have something better: no privacy-violating data at all.

    Who's forcing you to make advertisers happy? Don't answer that, because I don't care. You can't pretend to be about privacy and then build things that help advertisers violate it.

    This one's also pretty funny btw:

    If at some point they discover they’re doing insufficient aggregation or anonymization, then they can fix that all in one place.

    Advertisers don't give a shit. They have zero motivation to fix anonymization. They're not going to HELP us get rid of privacy violations.

  • Some troubleshooting thoughts:

    What do you mean when you say SSH is "down":

    1. connection refused (fail2ban's activity could result in a connection refused, but a VPN should have avoided that problem, as you said)
    2. connection timeout. probably a failure at the port forwarding level.
    3. connection succeeded but closed; this can happen for a few reasons, such as the system is in an early boot up state. there's usually a message in this case.
    4. connection succeeded but auth rejected. this can happen if your os failed to boot but came up in a fallback state of some kind.

    Knowing which one of these it is can give you a lot more information about what's wrong:

    System can't get past initial boot = Maybe your NAS is unplugged? Maybe your home DNS cache is down?

    Connection refused = either fail2ban or possibly your home IP has moved and you're trying to connect to somebody else's computer? (nginx is very popular after all, it's not impossible somebody else at your ISP has it running). This can also be a port forwarding failure = something's wrong with your router.

    Connection succeeded + closed is similar to "can't get past initial boot"

    Auth rejected might give you a fallback option if you can figure out a default username/password, although you should hope that's not the case because it means anyone else can also get in when your system is in fallback.

    Very few of these things are actually fixable remotely, btw. I suggest having your sister unplug everything related to your setup, one device at a time. Internet router, raspberry pi, NAS, your VM host, etc. Make sure to give them a minute to cool down. Hardware, particularly cheap hardware, tends to fail when it gets hot, and this can take a while to happen, and, well, it's been hot.

    Here's a few things with a high likelihood of failing when you're away from home:

    • heat, as previously mentioned.
    • running out of disk space. Maybe you're logging too much, throw some more disk in there and tune down the logging. This can definitely affect SSH, and definitely won't be fixed by a reboot.
    • OOM failures (or other resource leaks). This isn't likely to affect your bare metal ssh, but it could. Some things leak memory, and this can lead to cascading process destruction by the OS. In this scenario you'd probably be able to connect to things in the first few minutes after a reboot, though.
    • shitty cabling. Sometimes stuff just falls out of the socket, if it wasn't plugged in perfectly to begin with. (Heat can also contribute to this one.)
    • reliance on a cloud service that's currently down. (This can include: you didn't pay the bill.) Hopefully your OS boot doesn't fail due to a cloud service, but I've definitely seen setups that could.
  • “And since there’s still not the ability for people to shop around for other options, what are they going to do but pay that higher rate? But I think that it’s probably going to show pretty quickly that it’s necessary to keep State Farm from literally going insolvent.”

    Seems like you conveniently forgot another option here? Seize the fucking company. It belongs to California now.