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.

Context? Why would anyone think this band was “AI”?

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.

There is no such thing as “fully anonymised data”. Data can be de-anonymised by anyone who aggregates it. It’s been demonstrated over and over and over again.

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.

yw :)

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.

I probably won’t switch to Plex because of what they did with sharing all your activity without your consent, but I’m curious what you liked better about it as a music backend?

Good suggestion! I intend to mess with finamp and symfonium. I had no idea jellyfin was so popular as a music backend so I’ll just keep using that.

Yeah, I’ll probably just buy a few more albums than I used to. Streaming payments has always been a way to wring dollars out of artists, so I’d rather find other ways anyhow.

Gluetun is kind of a wrapper around wireguard or openvpn, that greatly simplifies setup and configurability.

I have a VM that runs wireguard to airvpn, in a container made of gluetun. Then you share that container’s network with a qbittorrent container (or pick your torrent) and an nzbget container (or pick your nzb downloader). Tada, your downloaders are VPN’d forever.

Thanks! Yeah, figuring out how to get gluetun working properly with a vpn and downloaders was a chore and a half. Glad I got that sorted, now I feel pretty confident I can punch a mobile app through into the network pretty easily.

Oh, that’s cool, I respect that.

Anyone know offhand their stance on jackbooted thugs kicking in the doors of people who write emulation software and sending them to prison? Just trying to get a pulse on that

So an option that is literally documented as saying “all files and directories created by a tmpfiles.d/ entry will be deleted”, that you knew nothing about, sounded like a “good idea”?

Bro, if it sounded like a good idea to someone, you didn’t fucking warn them enough. Don’t put this on them without considering what you did to confuse them.

Also, nfn, the systemd documentation is a nightmare to read through, even if you know exactly what you’re looking for.

(I’m still gonna keep using systemd because it’s better than the alternatives, though. OP, don’t write stuff off because 1 guy is a dick.)

Fair enough. I guess I’m not saying “there’s no point in --” because I know people do these things. (Man, I wish I had the attention span to read as much as you.) I’m just saying I’m not going to host something just to keep track with no recommendations or interaction because that doesn’t click for me personally.

Same. I don’t really see the point of tracking what you read if you’re not interested in connecting it to other peoples’ readings. Storygraph has been great.

When they tell you they’re walking back Recall and it’s “off by default”, remember that they constantly do this shit.

I don’t usually read walls of text (attention span) but this was a good one, worth reading to the end. Well said tbh

EDIT: Noticed you’re talking about Gitlab in the question, and I responded about Github, but I’m certain that gitlab does everything the same way, because that’s all the technology is capable of. (I have no way to test the ssh -T command at the end for gitlab, though, so ymmv.)

To clear up some minor confusion here:

1. Github knows nothing about your private key. There’s very little metadata stored in the private key, and github.com has access to none of it. That includes email address or identity.
2. Github has identity information stored for you, and then, separately, you uploaded a public key. The public key also contains no information about you, but github knows it’s part of your account. Additionally, github enforces a requirement that your public key can’t be uploaded to any other account, for the reason I’m about to state below.
3. Github has an index built of everyone’s public keys (or more likely their digests, although the technical details of the index are not something known to me–and it doesn’t matter). When it sees an authentication request, it looks up the digest in the index, which maps to a user account.

At this point it already knows who is trying to authenticate. Once your authentication request succeeds with your public key (the usual challenge-response handshake associated with asymmetric cryptography), github interacts with your ssh client (most likely git) applying the permissions of your user and your user account.

BTW, github has a documented method for testing the handshake without doing any git operations:

ssh -T git@github.com

Depending on your ssh config, you might also need to supply -i some_filename.pem to this. Github will reply with

Hi aarkon! You've successfully authenticated, but GitHub does not provide shell access.

and then close the connection.

Note that the test authentication uses the username git and, again, contains no information about who you are. It’s all just looked up on github’s side.

Well I didn’t see the comment you’re apologizing for so, no apology necessary ig?