A Mouse

It looks like they are working on fixing that with this pull request.

Is it https://tosdr.org/ ?

There’s also https://privacyspy.org/

I just checked myself and it’s card1 too, now I am curious why it’s not card0. 🤷

I believe it’s cat /sys/class/drm/card0/device/pp_power_profile_mode.

There’s also the power_dpm_force_performance_level.

Yeah, Debian has older firmware found in the firmware-amd-graphics package which doesn’t include the firmware. You’ll need to download it from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/ I believe anything from linux-firmware-20231030 and newer should work.

20231030 tag: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu?h=20231030 or newest(20240410) tag: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu?h=20240410

These files need to be placed in /lib/firmware/amdgpu/

Quickly skimming the readme, it states:

• OAuth token spoofing: To circumvent rate limits imposed by Reddit, OAuth token spoofing is used to mimick the most common iOS and Android clients. While spoofing both iOS and Android clients was explored, only the Android client was chosen due to content restrictions when using an anonymous iOS client.
• Token refreshing: The authentication token is refreshed every 24 hours, emulating the behavior of the official Android app.
• HTTP header mimicking: Efforts are made to send along as many of the official app’s headers as possible to reduce the likelihood of Reddit’s crackdown on Redlib’s requests.

Quad9 doesn’t report it as being blocked. https://quad9.net/result?url=catbox.moe

You can block instances. Go to settings, blocks, in block instance section search for the instance that you want to block.

grass is on the AUR… https://aur.archlinux.org/packages/grass

Not that it helps but the CEO claims they forgive for this type of attack/event. https://news.ycombinator.com/item?id=39521986

Netlify CEO here.

Our support team has reached out to the user from the thread to let them know they’re not getting charged for this.

It’s currently our policy to not shut down free sites during traffic spikes that doesn’t match attack patterns, but instead forgiving any bills from legitimate mistakes after the fact.

Apologies that this didn’t come through in the initial support reply.

And later they were asked if they would have responded if it didn’t go viral. https://news.ycombinator.com/item?id=39522029

Question:

There are only two questions everyone have:

1. Would Netlify forgive the bill if this didn’t go viral?

2. How do you plan to address this issue so that it never happens again?

Everyone here knew someone from Netlify would come and say OP wouldn’t have to pay. That was a given. Now we want to know the important answers.

Answer by CEO:

1. Yes. We’ve forgiven lots and lots of bills over the last 9 years and they haven’t gone viral

2. While I’ve always favored erring towards keeping people’s sites up we are currently working on changing the default behavior to never let free sites incur overages