CountVon

Oh I'm streets ahead, I never took him at his word in the first place.

I'm all for de-Googling, but... is it possible that Restricted in this context mean those apps have no data usage because they're restricted from using it? It could be trying to say that the app is restricted, not that you're restricted.

OpenAI on that enshittification speedrun any% no-glitch!

Honestly though, they're skipping right past the "be good to users to get them to lock in" step. They can't even use the platform capitalism playbook because it costs too much to run AI platforms. Shit is egregiously expensive and doesn't deliver sufficient return to justify the cost. At this point I'm ~80% certain that AI is going to be a dead tech fad by the end of this decade because the economics just don't work now that the free money era has ended.

I think you're referring to FlareSolverr. If so, I'm not aware of a direct replacement.

Main issue is it’s heavy on resources (I have an rpi4b)

FlareSolverr does add some memory overhead, but otherwise it's fairly lightweight. On my system FlareSolverr has been up for 8 days and is using ~300MB:

NAME           CPU %     MEM USAGE
flaresolverr   0.01%     310.3MiB

Note that any CPU usage introduced by FlareSolverr is unavoidable because that's how CloudFlare protection works. CloudFlare creates a workload in the client browser that should be trivial if you're making a single request, but brings your system to a crawl if you're trying to send many requests, e.g. DDOSing or scraping. You need to execute that browser-based work somewhere to get past those CloudFlare checks.

If hosting the FlareSolverr container on your rpi4b would put it under memory or CPU pressure, you could run the docker container on a different system. When setting up Flaresolverr in Prowlarr you create an indexer proxy with a tag. Any indexer with that tag sends their requests through the proxy instead of sending them directly to the tracker site. When Flaresolverr is running in a local Docker container the address for the proxy is localhost, e.g.:

If you run Flaresolverr's Docker container on another system that's accessible to your rpi4b, you could create an indexer proxy whose Host is "http://<other_system_IP>:8191". Keep security in mind when doing this, if you've got a VPN connection on your rpi4b with split tunneling enabled (i.e. connections to local network resources are allowed when the tunnel is up) then this setup would allow requests to these indexers to escape the VPN tunnel.

On a side note, I'd strongly recommend trying out a Docker-based setup. Aside from Flaresolverr, I ran my servarr setup without containers for years and that was fine, but moving over to Docker made the configuration a lot easier. Before Docker I had a complex set of firewall rules to allow traffic to my local network and my VPN server, but drop any other traffic that wasn't using the VPN tunnel. All the firewall complexity has now been replaced with a gluetun container, which is much easier to manage and probably more secure. You don't have to switch to Docker-based all in go, you can run hybrid if need be.

If you really don't want to use Docker then you could attempt to install from source on the rpi4b. Be advised that you're absolutely going offroad if you do this as it's not officially supported by the FlareSolverr devs. It requires install an ARM-based Chromium browser, then setting some environment variables so that FlareSolverr uses that browser instead of trying to download its own. Exact steps are documented in this GitHub comment. I haven't tested these steps, so YMMV. Honestly, I think this is a bad idea because the full browser will almost certainly require more memory. The browser included in the FlareSolverr container is stripped down to the bare minimum required to pass the CloudFlare checks.

If you're just strongly opposed to Docker for whatever reason then I think your best bet would be to combine the two approaches above. Host the FlareSolverr proxy on an x86-based system so you can install from source using the officially supported steps.

My dream was to work as a game developer. This was nearly 20 years ago. I actually got an offer in that field at one point, and the salary was like $20k less than what I was already being paid. I was the main bread-winner in what was a (mostly) single-income household at that time, with my partner pursuing her PhD. Gave up the dream, and I'm glad I did based on what I later learned about that industry. If I went into the game industry I'd be making far less money and have far less free time to do the things I enjoy, like playing the games other people make.

From https://www.githubstatus.com/ (emphasis mine):

We suspect the impact is due to a database infrastructure related change that we are working on rolling back.

If you fuck up the database, you fuck up errythang.

Anything that pushes the CPUs significantly can cause instability in affected parts. I think there are at least two separate issues Intel is facing:

• Voltage irregularities causing instability. These could potentially be fixed by the microcode update Intel will be shipping in mid-August.
• Oxidation of CPU vias. This issue cannot be fixed by any update, any affected part has corrosion inside the CPU die and only replacement would resolve the issue.

Intel's messaging around this problem has been very slanted towards talking as little as possible about the oxidation issue. Their initial Intel community post was very carefully worded to make it sound like voltage irregularity was the root cause, but careful reading of their statement reveals that it could be interpreted as only saying that instability is a root cause. They buried the admission that there is an oxidation issue in a Reddit comment, of all things. All they've said about oxidation is that the issue was resolved at the chip fab some time in 2023, and they've claimed it only affected 13th gen parts. There's no word on which parts number, date ranges, processor code ranges etc. are affected. It seems pretty clear that they wanted the press talking about the microcode update and not the chips that will have the be RMA'd.

One of my grandfathers worked for a telephone company before he passed. That man was an absolute pack rat, he wouldn't throw anything away. So naturally he had boxes and boxes of punch cards in this basement. I guess they were being thrown out when his employer upgraded to machines that didn't need punch cards, so he snagged those to use as note paper. I will say, they were great for taking notes. Nice sturdy card stock, and the perfect dimensions for making a shopping list or the like.

He was a raging alcoholic who hid his illness from the medical professionals who examined him as part of his Super Size Me "experiment." A lifetime of booze did way more damage than 30 days of McDs possibly could.

I haven't actually tried the new ones, I probably should do that before I slander them. The Harvest Cheddar ones were so good though. I haven't seen them in at least a few years, unfortunately.

I noticed that Miss Vickie's has a new sour cream something or other flavour in a bag that's the same colour, or nearly so. Every time I go through the chip aisle I get very excited for a second, then I realize it's not actually the Harvest Cheddar and my hopes are dashed. I'm developing an irrational hatred of those impostor chips.

The image on the right is a fake. If dude could grow a beard that looked anywhere near that good, he would've done it years ago.