I’m genuinely curious who you think will be blocked next?

This is a wildly popular measure in Australia.

No, it’s not unwise. Mozilla has no mechanism with which to surveil your activities built into the browser.

That said, you should avoid categorising companies as generally trustworthy or untrustworthy. Any given service will have privacy considerations - some may be important to you, others may not.

I’m not denying that, but the comment above is talking about a story about a woman discovering she’s a bot,.

Lately there’s been someone chopping chives every day and posting a photo of the result.

There was a bit of a drama when someone noticed that the same photo was reused from a couple of weeks back.

The poster said they didnt have time to do it that day but wanted to keep the streak so they just re-posted an old one hoping no one would notice.

It was just such an amazing and engaging sequence of events and I feel fulfilled having been able to follow this roller coaster of emotion /s.

Bob only thinks hes human for about half a page?

I use redlib to lurk.

I find the drama subs like /r/AITAH entertaining. I know its all fake, but the groupthink responses are intriguing.

Ok, you’re probably right. It wasn’t “the reason”. It was part of the discussion at the time though.

“By simply banning ports, we get rid of abuse of content hosted by our IPs via ports, and can focus on giving better privacy for the broader mass of people,” said Jonsson.

He said: “Statically linked port-forwards are not good for privacy, it can be linked to a user account. A VPN service that can identify a user, is not a good option for using port-forward with, if anonymity is important.”

https://www.techradar.com/news/mullvad-removes-port-forwarding-on-security-grounds

Mullvad stopped doing it because it can’t be done anonymously.

I torrent through mullvad. I’m not “connectable”. It’s fine for my uses.

Yes but… not really.

If you’re amazingly talented and spend 10 years of your life building something amazing but have no money, when someone offers you millions you’re just gonna take it.

I think i agree for the most part.

These energies would be better spent ensuring that porn stars aren’t being exploited and have access to appropriate support.

Syncthing. You don’t need nextcloud.

I think there’s a variety of complex legal, political, and technical reasons why torrent sites can avoid having their domain “seized”, but I think the summary is: there be dragons here and it’s not worth playing around with.

Politically, some jurisdictions define piracy differently and hosts won’t comply with legal threats from the US.

Legally, hosting a torrent is not the same as hosting a ROM. In the former case the actual copyright works are hosted by users, the torrent site just hosts the torrent file which is a list of users from whom you can download the content. ROM sites tend to provide the actual file for download, which contravenes relevant copyright laws.

Technically, you don’t need a commercial host platform to operate a website. It’s entirely possible to host a site in your mum’s basement on your laptop. Obviously for a large site you’ll want more appropriate hardware but the point is larger torrent sites are likely to run on hardware maintained directly by the admins.

The most compelling reason not to get involved in a public facing grey area site like ROM or abandonware hosting, is that it doesn’t really matter where you stand with the law - you won’t have the resources to defend yourself. Suppose Nintendo decides they don’t like you doing what you’re doing. They have an army of sophisticated lawyers who have spent a lifetime learning how to weaponise the law. It doesn’t really matter who’s “right”, all that matters is how much money you have with which to engage lawyers to defend yourself.

I’ve been using Linux for a long time and I don’t know any of this really.

Basically, home directory is for everything, unless some instructions say some other path.

Probably not that much honestly.

The resource intensive part is the initial training.

Tuning later is much less so.

It was definitely a thing at school in the 80s.

People have been talking about “post scarcity” since forever.

Yes, in the far distant future people will be able to have things they need and not have to work. AI will also exist in that future.

However, I don’t think anyone believes that future will arrive in the next decade.

This isbprobably a philosophical question that i dont know the answer to, but its still a waste.

This is really just a guess but… I think “agent” in this context means a personalised AI.

Training gen AI models requires huge amounts of resources. Its not practical to train an AI for your personal use.

Creating an agent is something like, taking an existing model, asking it to keep your entire browser history in mind while you ask it to do your homework.

IMO its actually one of the big limitations of gen AI, but somehow the word is supposed to mean the opposite. As in, the current approach has reached a dead end requiring exponentially more resources for less and less improvement. So because we can’t make a model that just knows or learns everything, we have to make agents that know lots about specific things.

I’ve never used tailscale but use wireguard extensively.

There’s not much of a learning curve for you as the administrator. You have to discard some misconceptions you might bring from other VPNs but really after 30 minutes of looking at configs you’ll get it.

I use wireguard for my small team of 5 people to access self hosted services. You install wireguard, load the config, and then it just works.

The trick, if it can be called that, is using public dns for private services.

On your server, suppose you have service-a service-b and service-c in containers with ip addresses in the 10.0.2.0/24 range. Then you’d have a reverse proxy like traefik at 10.0.2.1. You’d also create a wireguard container with an IP in that same 10.0.2.0/24 range, and configure it’s wireguard adapter to be 10.0.12.1 or soomething so you have “2” for the containers and “12” for the wireguard clients.

Then in wireguard configurations you direct all traffic for 10.0.2.0/24 through the tunnel but everything else just uses their devices normal internet connection.

Finally create a public dns record pointing to the reverse proxy like *.mydomain.com > 10.0.12.1

now whatever.mydomain.com will resolve to your reverse proxy but is still only available to devices connected to the wireguard container on your server.