• 0 Posts
  • 31 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle



  • 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.



  • 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.


  • MinuteCast from AccuWeather does exactly this. It looks at your location, looks at radar data for storm systems approaching your location, and estimates when precipitation will start at your location and how intense it will be. It’s generally pretty accurate, with some limitations. It seems to be pretty good for consistent rainstorms but it can get tripped up by pop-up thunderstorms, where the radar track can go suddenly from no rain to downpour. It doesn’t make predictions more then 2-3 hours out because past that timeframe it’s not easy to predict if weather will continue on its current track or change direction. Even with the limitations, I use it all the time. Mostly to tell if I should take the dogs out right away, or if I should wait an hour or two.







  • There are some viruses that have targeted Linux, but they’re rare compared to other platforms and their ability to spread is relatively low. One of the main reasons is just down to how software tends to be installed on each platform. Viruses have an easier time spreading on Windows or OSX where users are more accustomed to downloading an executable and running it. Once there’s a malicious running process, it has a comparatively high chance to spread because it can attempt to escalate its privileges either by exploiting a bug or socially engineering the user to click through a privilege escalation prompt. That entire workflow is practically nonexistent on Linux, users just don’t tend to download and execute random binaries. Instead most Linux software gets delivered in one of these ways, each of which has impediments that reduce the chance a virus could spread:

    • through an OS repo; it would be difficult for a malicious actor to get a virus through the release process and into a trusted repo
    • through a public source like Github; again it would be difficult for a malicious actor to get a virus into public source code without someone noticing
    • through a container image from an image library like DockerHub; I believe a malicious container would be sandboxed, making it hard if not impossible for that container to take over the host system
    • through an application image like a snap, flatpak or appimage; again, I believe these run in their own sandbox from which they would have difficulty breaking out

    There are some exceptions, for example some companies like Hashicorp will distribute their stuff as precompiled binaries. Even in that case you’re probably fine as long as you don’t run the downloaded binary as root. Users in the habit of downloading strange binaries from sketchy places and running them as root just aren’t very common among the Linux userbase. I’m sure there are some (and they should really stop doing that), but there aren’t enough of them to allow a virus to spread unchecked.


  • I don’t think dedicated antivirus software is really required anymore. I haven’t run third-party AV software on any of my systems in the last decade.

    On Windows, the built-in Windows Defender is good enough for most use cases. When it first launched Defender had a pretty bad track record at stopping viruses, but now it routinely ranks at the top.

    On Linux, antivirus software has never really been required. One major exception I can think of would be if you’re running a file server or mail server that talks to OSX or Windows systems. Even then the AV software isn’t really there to protect the server, it’s there to make sure you don’t pass malware or viruses to those non-Linux clients.