The popular use for power delivery through a display cable is charging a laptop from your monitor; it’s already very common with Thunderbolt or USB-4 monitors. But 480W seems a bit overkill for that.

You get what you pay for. If you are actually concerned about your privacy, then go with Mullvad. If you just want to download stuff for free without getting caught, then Privado is probably fine.

1. If you’re connecting to random free Wi-Fi, you’re leaving yourself wide open to attacks.
2. A lot of security researchers play with penetration testing scenarios like this. It’s how you learn to defend against techniques that real attackers use.

Lol this sounds like toothless bullshit. Are they confident that these people live in the US? Do they even know if these two twitter accounts are run by single individuals?

Accusing somebody else of licking the boot, while you’re having the same boot ground in your face and just acting like it’s no big deal, not a problem.

I think there’s some confusion here. You’re talking about Multi-Account Containers, that person was talking about the Facebook Container. Both Firefox features with confusingly similar names, and honestly that’s on Firefox for naming them.

Facebook Container is similar to this TCP feature, but focused on Facebook. And of course it was a separate extension, so very opt-in. Now, Firefox has rolled it out for ALL sites by default, which is awesome and SHOULD HAVE BEEN HOW COOKIES WORKED IN THE FIRST PLACE!

Kinda misleading or poorly written title. He was not convicted of falling for a crypto scam. He was convicted of embezzling funds from the bank, which he did while pumping them into a dumb crypto scam. It would have been illegal even if the crypto thing was NOT a scam (which is rare, I know).

Sometimes these issues happen because of the IP range you’re using. If your local network and your remote network both use the 192.168.x.x range, then there can be conflicts and issues like this. This is a thing that happens generally with VPNs, not sure how Tailscale specifically functions with this issue.

Even if that’s not what’s going on here, you might try setting up your remote node as an exit node, and configuring your local node to route all traffic through it. Theoretically that shouldn’t be necessary, and it will also slow down your traffic if you’re routing EVERYTHING through Tailscale. But it could work in a pinch.

Actually, I’m looking at Tailscale documentation now and I see that they recommend setting up subnet routers instead of exit nodes in most cases. Maybe go that route instead, that makes more sense to me. That way you’re only routing necessary traffic through the remote node, rather than everything.

Well, Nextcloud runs like shit on a Pi WITHOUT having to do AI stuff, so…