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

help-circle

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


  • It’s likely CentOS 7.9, which was released in Nov. 2020 and shipped with kernel version 3.10.0-1160. It’s not completely ridiculous for a one year old POS systems to have a four year old OS. Design for those systems probably started a few years ago, when CentOS 7.9 was relatively recent. For an embedded system the bias would have been toward an established and mature OS, and CentOS 8.x was likely considered “too new” at the time they were speccing these systems. Remotely upgrading between major releases would not be advisable in an embedded system. The RHEL/CentOS in-place upgrade story is… not great. There was zero support for in-place upgrade until RHEL/CentOS 7, and it’s still considered “at your own risk” (source).


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


  • Am I understanding this right that the scalper buys a legit ticket to extract the token, then it can be used any number of times to get in a venue? I thought their system should be able to identify a token/ticket has already been scanned after it’s first used? That’s why there are no re-entry rules at most venues.

    I don’t think the intent of the scalpers is to allow ticket reuse. Like you say, there are likely additional checks at the gate when a bar code is scanned. If a rotating barcode is cloned, only the first person to scan is going to get in. Everyone else who tries to use a clone of that now-used barcode is going to get denied entry because the door staff’s scanner is going to throw a “ticket already used” error of some kind. So while it’s technically possible to clone one of these rotating barcodes, just like it’s possible to have multiple authenticators producing the same OTPs, there’s no point in doing so.

    What the scalpers are after is a platform that allows them to resell tickets without giving TicketMaster a cut. TicketMaster allows their rotating-bardcode tickets to be transferred to a wallet app like Google Wallet. Wallet apps like Google Wallet have features to allow you to transfer tickets to another user’s wallet, but the wallet specification also includes a flag for whether wallet-to-wallet transfers are allowed. TicketMaster sets that flag so you cannot give (or sell) your ticket to someone else using your own wallet, instead you have to go through something that TicketMaster controls. For transfers to friends and family, TicketMaster forces you to use their app. For reselling tickets, TicketMaster forces you to use their reselling site. TicketMaster’s primary motive is obvious: they want to take a cut of ticket resales, and this is how they do that.

    The whole thing is a legal fight between two utterly shitty groups, TicketMaster and scalpers. Here’s hoping they somehow both lose.





  • Any increase in accuracy would not be worth the tradeoff. The current system in Canada is very simple and very visible. Scrutineers for every candidate can watch the votes being counted and immediately understand what is happening. No amount of trust is required for the system to work.

    A machine that counts votes would be a black box to observers of the election. Most would need to trust that the machines are operating correctly. When machine counts and manual counts disagree, even slightly, it sows confusion and discord. The mere existence of voting machines and machine counts in the US has been sufficient to give rise to numerous conspiracy theories. In my view they are part of the rot besetting American democracy, and I don’t want them where I live.


  • Hey, don’t get me wrong, it’s not all sunshine and roses up here in the north. We have huge problems with cost of living, especially housing, which our current government is failing to address. We have a multi-party system but in my lifetime the national power only ever oscillated between two parties, Liberal (roughly equivalent to US Democrats) and Conservative (roughly equivalent to US Republicans pre-MAGA, or maybe even pre-Reagan). Based on current polling, Canadian discontent looks set to sweep out the incumbent Liberals and sweep in the opposition Conservatives sometime between now and Oct. 2025. I don’t think the Conservatives are going to do any better at addressing cost of living, but fear that they’ll bring in a bunch of regressive crap while they continue to fail in the same way the Liberals have failed. There are lots of other areas where Canada has room for improvement, but within the very narrow scope of how Canada runs its elections, that I will claim we got right.


  • It only “costs little” because you have a ton of people willing to do it.

    First off you say that like it’s a bad thing. For the record, it is not. Second, many of the people counting votes are paid, i.e. Elections Canada employees. Scrutineers could be volunteers or paid employees of the party/candidate they represent.

    What if there’s something that prevents people from volunteering?

    That would equally inhibit people from voting. Besides which, elections can and have been postponed in cases of severe weather, and wildfires have been considered in cases where they’ve been occurring around an election. No politician or Elections Canada supervisor is going to send voters, employees and volunteers out to die for an election.

    Or maybe a worldwide pandemic?

    We had one, it went fine. Anyone who didn’t like the thought of voting in public had the option of voting by mail, something that every Canadian has been allowed to do since 1993.

    There’s really no reason to not machine count with a matching hand count.

    Yes there fucking is. Machines add completely unnecessary complexity to a simple system that works.


  • Why not machine certify and hand-count verify?

    Because the manual system works well and costs little.

    Could have both systems for quick results on the day and verified accurate results in the longer term.

    Canada already has hand-counted and verified results the same day the election occurs, in a country with a population roughly equivalent to the state of California. Adding machine counting would only add complexity and cost while producing no additional benefits.

    Have the voting machine

    Canada doesn’t have voting machines, nor do we want them. Our ballot system is a piece of paper and a pencil. That’s it. That’s our whole voting “machine.”

    The real genius is in how the vote counting process works. Every candidate is allowed to provide a representative, often called a scrutineer, to oversee the counting process at each polling station. Scrutineers are allowed to challenge a ballot if they feel it has been attributed to the wrong candidate or should have been considered a spoiled ballot. The doors to the polling station are locked while ballots are being counted, and no one is allowed to go home until the count is complete. Basic self-interest ensures that counts are done in a timely fashion, while also ensuring that every candidate can have a representative that was part of the counting process.

    Under the Canadian system, for all practical purposes it would be impossible to perpetrate election fraud. A candidate would need to somehow induce Elections Canada employees and/or volunteers at multiple polling stations to miscount ballots. They would also need to convince multiple scrutineers to turn a blind eye, scrutineers who were nominated by their opponents. Each riding typically has 4+ candidates (at minimum Liberal, Conservative, New Democrat, and Green party candidates, plus often some independent or fringe party candidates), and every single one of those candidates is allowed to provide a scrutineer at each polling station. There will be many polling stations across a single riding, so that’s potentially dozens or hundreds of people that would need to be coerced or convinced to contribute to the election fraud. And that’s just for one single riding.



  • I’m sure there would be a way to do this with Debian, but I have to confess I don’t know it. I have successfully done this in the past with Clover Bootloader. You have to enable an NVMe driver, but once that’s done you should see an option to boot from your NVMe device. After you’ve booted from it once, Clover should remember and boot from that device automatically going forward. I used this method for years in a home theatre PC with an old motherboard and an NVMe drive on a PCIe adapter.





  • If you look at the Steam player charts for the game you’ll see when it’s working vs. when it’s not. Off-peak it works fine, but right now the player base is ramming up against their temporary player cap for hours at a time on-peak. If you try to connect when there are thousands of others also trying to connect, that’s when things go south. That was the case for much of the weekend.

    Edit: Here’s a chart illustrating what I mean:

    In the last 48 hours, player counts hit 400k at about 7pm Eastern UTC and just stayed there for 6-ish hours. That isn’t normal, almost all other player count charts show a gradual rise and fall over the course of a day. The devs implemented an artificial cap after they found that their servers bog down when there are too many active players, basically sacrificing the peak time login experience to preserve the in-game experience. If you try to connect while the active player count is pegged, you’re essentially joining a swarm of other players who are also trying to connect at the same time. That swarm is likely DOSing some aspect of their own login systems.