A Mouse
It’s a relatively low performance hit and it benefits me when having to replace a failing/old disk. I can just toss the drive without having to erase the data first, that is as long as the key is a secure length.
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
Yeah, I originally was hoping for a singleplayer mode and realized that it didn’t have any way to reset player progress. Ubisoft needs to realize that MMOs aren’t meant to have sequals so often and are meant to support them for a long time and instead release expansions, look at Runescape, WoW, and Guild Wars 1 for examples.
It has been released as exactly that: https://www.knockoutcity.com/private-server-edition#section-download
Isn’t that what they did? https://www.knockoutcity.com/private-server-edition#section-download
From the article:
There’s one thing, however, that Harrison recommends studios do above all others when sunsetting a live service game: let players keep playing the game on their own servers. Before shutting down Knockout City, Velan released the game as a standalone Windows executable with private server support. It’s still available to download.
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:
Would Netlify forgive the bill if this didn’t go viral?
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:
Yes. We’ve forgiven lots and lots of bills over the last 9 years and they haven’t gone viral
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