CountVon

I don't believe it actually does grow back faster, it just seems that way. The first inch or so gives the impression of growing back faster because the hairs are thicker at the base so they're more visible and less prone to breakage.

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.

The owner of the Cantina doesn't like droids, so my head canon is that he's repurposed scavenged droid heads as drink dispensers. Kind of a "drinking from the skull of your enemy" type thing.

Is there any benefit at all

Maybe! There's at least some scientific evidence that chemical compounds in mushrooms can have medicinal effects.

Bias disclaimer: I put a lion's mane mushroom tincture in my morning tea because it may have a neuroprotective effect (source). My father's father had dementia, my father is currently in a home with profound dementia, the chances it's going to happen to me are very high. It'll be years before I know whether lion's mane mushroom will do anything for me (and even then you couldn't claim anything from one data point), but I'm willing to try anything as long as it's affordable and has at least some plausible evidence behind it. This isn't the only thing I'm doing of course, I've also overhauled my diet (MIND diet) and lost 30 pounds (obesity is correlated with dementia).

why can’t you make it your self by pulverizing dried mushrooms of the same variety they use into powder and making the coffee yourself?

You absolutely could. Or, you know, just eat some of the same mushrooms. The benefit to dried products like Ryze, or tinctures like the one I use, are that they're convenient, easily transportable and self-stable. I've cooked up fresh lion's mane mushrooms several times, but not super often because they're not in many stores in my area and tend to be pricey for the amount you get. I've also grown my own from a kit but that takes significant time and a little bit of daily attention to maintain optimal growing conditions. The tincture is convenient and relatively affordable as far as daily supplements go.

Keep in mind that Larry Ellison is fundamentally incapable of caring whether or not "citizens will be on their best behavior." The only reason he would say a thing such as this is because he sees an opportunity to make money from such a system.

Do not fall into the trap of anthropomorphising Larry Ellison. You need to think of Larry Ellison the way you think of a lawnmower. You don't anthropomorphize your lawnmower, the lawnmower just mows the lawn, you stick your hand in there and it'll chop it off, the end. You don't think 'oh, the lawnmower hates me' -- lawnmower doesn't give a shit about you, lawnmower can't hate you. Don't anthropomorphize the lawnmower. Don't fall into that trap about Oracle.

• Brian Cantrill (https://youtu.be/-zRN7XLCRhc?t=33m1s)

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.

Tl;Dr the protocol requires there to be trusted token providers that issue the tokens. Who do you suppose are the trusted providers in the Google and Apple implementations? Google and Apple respectively, of course. Maybe eventually there would be some other large incumbents that these implementers choose to bless with token granting right. By its nature the protocol centralizes power on the web, which would disadvantage startups and smaller players.

Private State Tokens are Google's implementation of the IETF Privacy Pass protocol. Apple has another implementation of the same protocol named Private Access Tokens. Mozilla has taken a negative position against this protocol in its current form, and its existing implementations in their current forms. See here for their blog post on the subject, and here for their more in-depth analysis.

The part where he complains about how "it's such a callous indifference to the sacrifices made by (Trump's) supporters on (Trump's) behalf" just sent me. He thinks Trump is being callously indifferent now? Amazing that they'll never allow themselves to realize or admit that Trump never gave a shit about them in the first place.

One of my grandfathers used to work for Nortel. One of the projects he worked on was the Trans Canada Microwave, which was a microwave relay system built in the '50s to carry television and telephone signals across Canada. The towers were installed all over Canada in remote locations and high elevations. Maintenance on the system could be required even when the weather was bad. My grandfather told me that the engineers who worked on the towers would sometimes stick their hands in front of the microwave emitters to warm them up. It's anecdotal, but I'm relatively confident that it's theoretically possible to warm people with microwaves.

Big caveat, though. Those engineers knew how powerful the emitters were, they knew that microwaves are not ionizing radiation and thus posed no cancer risk, they knew roughly what percentage of their hands was composed of water, and thus how much heat energy their hands would absorb from the emitters at a given power level. That's the only reason they were willing to do it, well that and they were probably the kind of people who got a kick out of doing something that would appear insane to most of the populace.

It seems very unlikely to me that a microwave system could be turned into a safe people-heating system for at least the following reasons:

• Feedback loops. All modern HVAC works on feedback loops. Your thermostat detects that the temperate is cold, it fires up your furnace / heat pump / electric baseboard / whatever and produces more heat. When the thermostat detects that the temperature has reached the set-point, it shuts off the heat. Current thermostats would not be able to detect the effect of microwave heating, which prevent the establishment of a feedback control loop.
• Uneven heating. Things with more water will heat up a lot faster than things with little water. This is usually fine when microwaving food since most of our food is water, in varying concentrations. If you're heating up a burger in the microwave, you can put the patty in by itself for a minute, then put the bun in for 15 seconds, then reassemble a burger that doesn't have a cold patty or a stiff overcooked bun. If you're heating up a person, you can't ask them to take out their almost-entirely-water eyeballs to ensure they don't overheat.
• Failure conditions. If your heat gets stuck in the on setting, the maximum result is probably that your house will get sweltering hot but not hot enough to kill you in a moderate timeframe. Depending on power levels, a microwave heating system could internally cook people in their sleep if it entered a failure mode where the heating got stuck in the on setting.
• Efficiency. It takes a considerable amount of power to run even a small microwave, and that's blasting microwaves into a relatively tiny cubic area. Trying to heat people would require microwaving a much larger volume, and said volume would also be moving around. Trying to emit microwaves in even a house-sized volume would probably be prohibitively costly.
• Interactions with metal and other objects. Microwaves can create intense electrical fields around metal objects, and those can become intense enough to create plasma and electrical arcs. Hell, you can create plasma in your microwave with two grapes. Blasting microwaves into a large volume with unknown contents would be a great way to create an unexpected fire.

Not the person who made the comment, but here's my understanding. A "third place" is somewhere you spend a lot of time when you're not at home (the first place) or school/work (the second place). Third places such as community centers were vital to the civil rights movement in the 60s, it was where much of the movement's meeting, debating and organizing took place.

The Reagan administration systematically defunded any of these politically active third places that were receiving federal funds, probably because they were worried that they'd be infiltrated by those scary communists. They were so worried about what the organized people might do in the future that they did everything they could to kick the financial struts out from under these community organizations. In many cases this destroyed some or all of the local community benefits that those organizations were actually providing.

This trend cut across the political spectrum too. The Clinton administration did its own wave of defunding, though I suspect that was more for economic (i.e. neoliberal) than political ideology. Combine the lack of community investment with the rise of the internet, and you arrive at the situation we have today where third places are becoming increasingly scarce. It's hard for communities to develop and maintain a cohesive identity when there's no longer any metaphorical "town squares" where the people in that community gather.

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.