The delusion that always baffles me is gang-stalking. For the ones who don’t know, there is a fairly common delusion where someone believes that they are being gang-stalked. They think random people going about their day-to-day lives are actually secretly working together to stalk the one person specifically. They think people band together and form massive gangs for various surveillance/stalking reasons. For fun/gossip, for government tracking, for secret shadow cabals keeping tabs on people, etc.

That person you pass during your walk, who politely nods as they pass you? They were an agent, and now everyone knows where you are.
That girl you see walking her dog past your house three times every day? She’s making a thrice-daily report on you.
That utility worker, doing maintenance on the power lines? They secretly installed an antenna to track when you’re at home.
That dude who edges past you in the grocery store, because you took up the entire goddamned aisle with your cart sitting in the very middle of the row while you stopped for three fucking minutes to look at three different brands of pickles? (Just pick one and get the fuck out of the way already!) Obviously he was trying to plant nanite tracking robots on your groceries, so the group can listen to your thoughts after you eat them.

I think it’s due to the (extremely common) “I’m being watched” paranoia, without having a specific target to pin the blame on. Instead of that breaking the delusion and realizing that nobody specific is watching them, they simply pin the blame on everyone around them.

The even worse part is that if you simply search up “Gang stalking”, you’ll find the wiki article on it… But you’ll also find a bunch of websites made by deluded people, who legitimately believe they (and thousands of others around the world) are being gangstalked. They call themselves “targeted individuals” and it very quickly becomes a self-perpetuating delusion. Any attempts to break them out of it only serve to reinforce the delusion, because obviously you’re a gang-stalker sent to try and trick them.

On Cloudflare, you’ll want to set a DNS record to point any relevant subdomains to your current WAN IP address. IPv4 will be an A Name record. IPv6 would be an AAAA Name record, but I’m not going to deal with IPv6 for this… Here is an example of mine, with info blocked out:

So for instance, maybe you have a peepee.example.com subdomain, a poopoo.example.com subdomain, etc which all point to your WAN IP address. That will basically tell Cloudflare’s DNS to forward any traffic for those subdomains to your WAN IP. Each subdomain can also choose whether or not to proxy the content, or just directly send it to your WAN with DNS. Basically, when Cloudflare propagates the DNS records to the various DNS servers, you can choose whether that record has your WAN IP (DNS Only) or one of Cloudflare’s (Proxied). In most cases, you’ll want DNS Only. Proxy support will depend on the individual service. Some will work fine with it, some won’t. And it’s also possible that you don’t want services proxied through Cloudflare for privacy reasons.

Next, you’ll want to set up a reverse proxy service. This will be something like Nginx Proxy Manager, Caddy, etc that you run on a device on your LAN. It can even be on the same machine running your various services. The big reverse proxies all offer Docker images, so you can incorporate it directly into an existing Docker stack if you already have one. Personally I use NPM, but Caddy is also very popular.

You’ll tell this reverse proxy “when you receive valid traffic addressed to {subdomain}, forward it to {relevant service on your LAN}.” You can also set some additional options for each subdomain, like automatically upgrading to https. For instance, maybe peepee.example.com forwards to 192.168.1.100:42069 on your LAN, and is configured to automatically upgrade any http traffic to https, and to require https.

You can also set up automatic TLS certificate renewal, so https traffic can be properly encrypted. The reverse proxy will need an API key, and it will allow the service to automatically check expiration dates and pull a fresh TLS cert for your domain if the date is coming up soon.

You’ll probably want to use a wildcard certificate, (basically *.example.com) because the TLS certificates are open to the public. So if you do individual certs for all of your various services, bots will scrape the public records and you’ll inevitably get a lot of bot traffic probing your various subdomains. A wildcard domain usually means the bots hit the standard example.com and www.example.com first, which makes them super easy to detect and block. I even have rules set up to automatically block anything that tries to access my www subdomain, because I specifically don’t host a landing page and don’t have anything available there. So I know that any traffic hitting that www subdomain is a bot trying to access common subdomains.

Next, you’ll want to forward ports 80 and 443 to your reverse proxy. Port 80 is the standard port for http traffic, and 443 is the standard port for https traffic. These will be the ports that your reverse proxy actually receives the traffic on, before forwarding it to the various services. Note that lots of lazy devs default to using 80 and 443 for lots of things, so you may want to configure your router to use a different port (like 81 or 444) for its config page if you’re able. Otherwise, you may end up accidentally locking yourself out of your router’s config page, because it will attempt to use 80 to reach the page, then get automatically forwarded to the reverse proxy instead.

Finally, for some ease-of-maintenance, you may want to consider adding a DDNS service (like Cloudflare-DDNS) to your docker stack. This will occasionally check your current WAN IP, and update it with Cloudflare if necessary. For example, if you have an outage and your router gets a new WAN IP when it boots back up again. Normally you would need to manually go to Cloudflare and update the IP info to point at your new address. But DDNS does that automatically.

The way traffic flows when it is all set up is along these lines:

1. A device wants to access your service at peepee.example.com. It doesn’t know where to find that site, so it asks a DNS server.
2. Cloudflare has told all of the various DNS servers “hey, peepee.example.com can be found at {your IPv4 WAN address}”.
3. The device follows that DNS record, and attempts to connect to your IPv4 WAN address, on port 80 or 443. For this example, let’s say it tries to connect on port 80 for standard http traffic. The device knocks on port 80’s door and says “hey, I’m here to access http://peepee.example.com/.”
4. Your reverse proxy checks the configured list, finds the valid peepee.example.com subdomain, finds it has a valid TLS cert, finds it is configured to automatically upgrade to https, and responds “Yes, please upgrade to https. Http traffic is not allowed.”
5. The external device knocks again, this time on port 443’s door. It goes “hey, I’m here to access https://peepee.example.com/. Your reverse proxy goes “thank you, here is the TLS cert and my half of the TLS security handshake.”
6. Your external device uses the data in the TLS cert to validate and complete the TLS handshake with the reverse proxy, and the traffic between the reverse proxy and your external device is now encrypted with https. Your device gets the nice little “secured” padlock icon in your browser. Because the traffic is encrypted, a malicious actor may be able to tell what kind of info you are passing (for example, a video stream will likely have a pretty obvious pattern) but they won’t be able to see what specific data you are passing. They may be able to tell that you’re streaming a video, but they won’t know which video specifically.
7. The reverse proxy forwards the traffic to the service, configured at 192.168.1.100:42069.
8. Your service does not ever know the device is being accessed via WAN, because (as far as the service can tell) the traffic is coming from your reverse proxy (also a LAN device). So any “pay to use WAN” services will continue to work for free.
9. The external device never gets access to info like the specific LAN IP or port number, because it only has access to the reverse proxy. All of the traffic is passing back and forth between the reverse proxy.

But notably, keep in mind that the reverse proxy didn’t do any actual user authentication. If your service has a weak password, a reverse proxy will act as a gateway for any potential hackers to gain access to the service. The same way an open port is a gateway directly to the service, the reverse proxy is now a gateway that simply requires an attacker to use a subdomain instead of an IP and port number. And if you make your subdomain something like jellyfin.example.com it will probably be dead simple for a bot to guess. And any vulnerabilities in the service will still be exploitable via the reverse proxy, because the reverse proxy is simply making sure the request is valid, and then passing the traffic back and forth. It isn’t actually inspecting the content of that traffic, so it’s not going to stop things like attackers. When you hear digital security folks talk about things like attack vectors, this is what they’re referring to. Your reverse proxy is a potential vector of attack for your configured services. Use strong passwords, keep your services updated, etc…

You can technically add authentication to a reverse proxy. So for instance, maybe a service doesn’t have any built-in way to add a password. You can have the reverse proxy act as an authentication gate, so it will prompt the user for a username+password before they can even reach the service. This will make the services more secure (yes, even the ones that already have passwords, as long as you use a different password for your reverse proxy authentication) but it will break most apps that are designed to work with a service. For instance, Jellyfin has several apps that work, but those apps won’t have any way to get past the reverse proxy’s password gate. So those apps will simply break if you add a second layer of authentication with your reverse proxy.

There are also some security options you’ll likely want to enable on Cloudflare’s side, but this comment is already long enough.

Was going to comment something along the lines of “Inb4 someone posts that obscurity will keep you secure” but here you are. No, you won’t be secure just because it’s on IPv6. And TLS certs are open to the public, (they literally have to be, since any device attempting to access your server needs to be able to validate the cert) so bots will scrape them and instantly have whatever you made it for. So it wouldn’t even keep you obscure.

That does exactly what I said in the second method. It insulates everything except the top, so it freezes in one direction. So I guess thanks for proving my point?

If you’re into making fancy ice, then you can get into making your own purified water using complete combustion. If you’re into making purified water with complete combustion then can get into making your own hydrogen, carbon, and oxygen. If you’re into making your own hydrogen, carbon, and oxygen then you can get into making your own universe.

That may help slightly, as it lowers the water’s ability to hold dissolved gasses. So boiling it beforehand will force out a lot of the gas that would have become air bubbles. But it’s not perfect, and results vary a lot. There are two main ways to get clear ice:

1. Keep it moving while it freezes, so the air bubbles can escape
2. Insulate it so it only freezes from one direction.

Basically, the air bubbles cause foggy ice. And air bubbles tend to get trapped because water freezes from the outside (where the cold air is touching it) first. This forms a hard shell, which then traps the gas and causes foggy ice. By agitating the water, you ensure that it doesn’t start freezing until all of the water is ready to freeze. It prevents the shell from forming first, meaning gas can escape the center of the cubes as it freezes.

For the second method, by insulating it, you ensure that the water freezes from one direction. For instance, if you fill an ice chest/cooler with water (effectively insulating it from the sides and bottom) and throw it in the freezer without a lid, the top half of the cooler will be clear ice and the bottom will be foggy. Because as the top freezes, the gas is able to escape down towards the bottom of the cooler. So your ice doesn’t get murky until the gas runs out of room at the bottom of the cooler.

If it happens before the end of the year, Vance won’t be allowed to run for a third term. So if Trump croaks as a result of this heat, Vance would only be able to be in office for (at most) six more years instead of nine or ten.

I don’t think Vance would realistically win in the next election regardless. But it would be comforting to know that if he does, it would for sure be his only full term.

I mean, the crowds at the Great American State Fair are a pretty good indicator. I’ve seen longer lines at my local Starbucks. The administration had really lofty attendance expectations, and forgot to account for the fact that Russian bots can’t visit the fair. This was aired on Fox News, which means it is the most flattering crowd shot they could find:

I’m honestly shocked that nobody has corrected my incorrect usage of Poe’s Law.

I think this is a very well thought out approach to handling it. I can’t personally think of any better solutions, at least. I probably would have chosen some different phrasing for the tags, (CBH feels… Disconnected? I’d probably go with something like “No AI” or “AI-Free” instead), but that’s just a matter of personal diction. Outright banning posts about projects that use AI likely isn’t going to be feasible in the long run, and I think that simple declaration requirements will go a long way towards encouraging people to actually disclose their usage.

If you outright ban it, people will simply hide their usage. It feels like it’s akin to the US War On Drugs^TM in that way. If you allow it and simply require responsible disclosure, more people will be inclined to be upfront about it. And that allows projects to be more accurately audited and vetted. The same way the war on drugs consolidated power to organized gangs (by making them the only ones capable of producing and transporting illegal drugs at scale), an outright ban on AI would only encourage people to hide their usage.

One potential way I see people trying to skirt the rules regarding self-promos is via proxy/strawman accounts. It would be trivial for me to spin up a dummy account and post my own project as an “I found this cool project but don’t have to disclose my AI use because I didn’t make it” post. I don’t personally have any projects in the works to post about, but I can easily see someone using it to try and skirt the disclosure requirements. Especially when we have seen situations like the (now infamous) Huntarr debacle, where the vibe-coder dev was actively avoiding AI disclosures. Because they knew it would tank the project’s popularity if people knew it was vibe coded.

I’m not sure if there is a good solution for this potential issue, except maybe to limit posts by new users. But even that is trivial to bypass. If you limit them based on account age, simply making a few strawman accounts and waiting for them to age is easy. Hell, I already have a few old throwaway accounts that I could swap over to whenever I want, and I’m not even planning anything nefarious.

There are similar problems with restricting users based on post/comment count, as that will likely stifle discussion from new users who are trying to be active in the community. One of the more frustrating parts about Reddit was that many of the most popular subs banned posts from users who were below a certain post karma threshold or who didn’t have enough previous posts. It created a catch-22 where you needed to have a few popular posts before you were allowed to make any posts. So there were people posting on random niche subs, simply for karma farming before they could then post on the larger subs. And if I was a vibe coder without scruples who is already looking to skirt the rules, it would be trivial for me to spin up an LLM and let it make a few comments before I start using it as a dummy account.

This may end up being a non-issue in the grand scheme of things. But I figured I’d mention it, because I genuinely don’t see a good solution for patching the big glaring hole in the self-promo rule. You’re absolutely correct that requiring disclosure for every post is unrealistic, because lots of users who post projects here aren’t the devs. They just stumbled across a cool project and wanted to share it, and they have no realistic way of knowing if the project uses AI. And if you restrict promo posts to only devs, you’ll only get posts from the people who fall into the (likely very small) overlapping section on the “is a Lemmy user” and “makes projects” Venn diagram. Lemmy is already a small community in the grand scheme of things. And restricting promo posts to only the people actively developing the projects would make it feel even smaller.

If I do use mine, I’ll put it up on codeberg so everyone can see exactly what its doing… and then get mad and tell me there is a better way.

Poe’s Law is always in effect. The best way to get an answer on the internet is not to ask a question; it is to post an incorrect answer, because people will go out of their way to correct you.

Portable DVD players, yeah. This was literally the first thing I thought of when I saw the headline.

I block all of my smart TVs at the DNS level with my pi-holes. All of the benefits (native streaming apps, easy casting, a functional remote without any fuss, etc) without any of the ads or tracking.

Yes, but not everything does. But luckily, Docker exists on Windows. So anything that runs on Docker can be run on Windows.

Given, Docker’s implementation on Windows is… Uhh… Not Great^TM. Because it’s basically using WSL to trick Windows into supporting a Linux file system. So it has some quirks. But it does technically work.

You have trouble getting Docker to auto-start on Windows? I thought that was the default behavior… Hell, even if it’s not, you can just add a Docker shortcut to the Startup folder.

Yeah, I keep a “Kids” profile on my Plex/Jellyfin server, specifically so I can throw Bluey, Mr Rogers Neighborhood, Miss Rachel, etc on and not worry about it. Elsagate (which is still a big problem) means you can’t just put on YouTube Kids and expect auto-played content to stay safe. But with my server, running solely on content I have curated, I know that everything in that “Kids” profile is going to be safe.

Same brand. Same price. Suddenly there’s only 200 pills in the bottle AND it’s in a larger bottle now?

AKA Shrinkflation. Retail is full of it, and it is usually done in a way that leaves the original package size alone. The goal is to reduce the amount of product inside of the package, without changing the package noticeably. The linked Wiki page uses Toblerone as an example, but here is another good example:

The package dimensions for the peanut butter appear to stay the same, (at least when it is sitting on a shelf) so customers don’t immediately notice the smaller size. They just think “my last jar was this same size, so I’m getting the same amount.” It feels like the same amount, even though it is much less for the same price.

My personal favorite example is the Terry’s Chocolate Orange, which slightly reduced the thickness of each individual wedge. By adding that air gap between wedges, they were able to reduce the amount of chocolate in each orange by like 15%, while still maintaining the overall size and shape. Here is the old vs the new:

Notice how thin the new slices are? That means less chocolate per wedge, for the same price.

Usenet will likely still be around, and torrents are like playing whack-a-mole.

My only complaint is that lots of my streaming devices don’t natively support newer codecs. So if I convert everything to AV1, my server will end up transcoding basically everything. Smart TVs are particularly bad about supporting anything past h264.

Yeah, the *Arr stack has effectively eliminated the need to permanently retain media. I want to watch something? I just request it, and 10-20 minutes later it is available on my server. I tend to treat *Arr requests the same way I used to treat Blockbuster trips. It takes a few minutes to get what you want to watch, but that’s also a chance to make some popcorn, grab a beer, and settle in.

I only (“only”) keep ~25-30TB of media available at any one moment. And even that is plenty. It’s literally hundreds of movies and TV shows. And if I want to purge old content, that’s easy to do too. Hell, I can even sort by the last time it was watched, and start with the shit that hasn’t been touched in like 18 months.

Gate keeping art is as old as art itself.