stardreamer

Harder to write compilers for RISC? I would argue that CISC is much harder to design a compiler for.

That being said there's a lack of standardized vector/streaming instructions in out-of-the-box RISC-V that may hurt performance, but compiler design wise it's much easier to write a functional compiler than for the nightmare that is x86.

Oh nice! A new tool! Do you happen to know how this compares to win10privacy?

Vanced got taken down due to trademark violations.

They need something more substantial for revanced. Especially since it's only a set of binary patches and there is no redistribution of YT source code.

iirc the bad UA filter is bundled with either base-http-scenarios or nginx. That might help assuming they aren't trying to mask that UA.

Pretty sure expiry is handled by the local crowdsec daemon, so it should automatically revoke rules once a set time is reached.

At least that's the case with the iptables and nginx bouncers (4 hour ban for probing). I would assume that it's the same for the cloudflare one.

Alternatively, maybe look into running two bouncers (1 local, 1 CF)? The CF one filters out most bot traffic, and if some still get through then you block them locally?

I've recently moved from fail2ban to crowdsec. It's nice and modular and seems to fit your use case: set up a http 404/rate-limit filter and a cloudflare bouncer to ban the IP address at the cloudflare level (instead of IPtables). Though I'm not sure if the cloudflare tunnel would complicate things.

Another good thing about it is it has a crowd sourced IP reputation list. Too many blocks from other users = preemptive ban.

According to this post, the person involved exposed a different name at one point.

https://boehs.org/node/everything-i-know-about-the-xz-backdoor

Cheong is not a Pingyin name. It uses Romanization instead. Assuming that this isn't a false trail (unlikely, why would you expose a fake name once instead of using it all the time?) that cuts out China (Mainland) and Singapore which use the Pingyin system. Or somebody has a time machine and grabbed this guy before 1956.

Likely sources of the name would be a country/Chinese administrative zone that uses Chinese and Romanization. Which gives us Taiwan, Macau, or Hong Kong, all of which are in GMT+8. Note that two of these are technically under PRC control.

Realistically I feel this is just a rogue attacker instead of a nation state. The probability of China 1. Hiring someone from these specific regions 2. Exposing a non-pinying full name once on purpose is extremely low. Why bother with this when you have plenty of graduates from Tsinghua in Beijing? Especially after so many people desperate for jobs after COVID.

I assert that this tech is biased towards bears and racoons.

Both Bluetooth and BLE are perfectly fine protocols. You won't be able to design much for short distance with that much power savings otherwise. The main issue is that for any protocols like this you would most likely need to put it in the 2.4ghz unlicensed band. And that's predominantly used by wifi these days.

I'm familiar with the Apollo retro-reflectors. Though in all seriousness I doubt a laser would provide a substantial amount of power (unless you have a specialty designed energy collector like in RFID)

Wouldn't shining back be counterproductive for this? You want the solar panels to harness the energy, not returning it to sender

My suggestion would be to try compiling the kernel locally.its highly likely the one packaged in your distro contains extensions that you don't have. Doing a local native compile should rule that out pretty quickly without having to disable any additional features.