Well, technically, we're letting Natalie do it, which is, of course, worse in every way imaginable, since she's immune to the sense of embarrassment that sometimes restrains him from acting on every little whim.
To be honest that was actually my first theory, since the bots didn't seem interested in exploring the rest of the domain. I suppose there's no way to know for certain. I concluded that it must be an imbecile's attempt at harvesting, though, because the queries weren't really exploring the string space in any useful way. Here's a sample:
"GET
/index?author=15&go=Search&id=48&name_restrict=1&q&re&results_&results_pagenum=2980 HTTP/1.1"
"GET/index?author=2&go=Search&group=0&group_restrict=1&id=48&name_restrict=1&q&results_pagenum=5440&template=41&type HTTP/1.1"
"GET/index?author=15&go=Search&id=48&name_restrict=1&q&results_pagenum=33500&templat HTTP/1.1"
"GET/index?author=15&go=Search&id=48&name_restrict=1&q&results_pagenum=32640&templ HTTP/1.1"
"GET/index?author=15&go=Search&id=48&name_restrict=1&q&res&results_page&results_pagenum=39300 HTTP/1.1"
"GET/index?author=15&go=Search&id=48&name_restrict=1&q&results_&results_pa&results_pagenum=12340 HTTP/1.1"
"GET/index?author=2&go=Search&group=0&group_restrict=1&id=48&name_r&res&results_pagenum=6100 HTTP/1.1"
"GET/index?author=2&go=Search&group=0&group_restrict=1&id=48&name_restrict=1&q&results_pagenum=2920&te HTTP/1.1"
"GET/index?author=15&go=Search&id=48&nam&results_&results_pagenum=17940 HTTP/1.1"
"GET/index?author=15&go=Search&id=48&name_restrict=1&q&results&results_pag&results_pagenu&results_pagenum=37720 HTTP/1.1"
"GET/index?author=15&go=Search&id=48&name_restrict=1&q&results_pagenum=9360&template=41&type_r HTTP/1.1"
"GET/index?author=15&go=Search&id=48&name_restrict=1&q&r&results_pagenum=28040 HTTP/1.1"
"GET/index?author=15&go=Search&id=48&name_&results_pag&results_pagenum=10400 HTTP/1.1"
The only thing this is fuzzing is the query string parser. It's not testing the limits of string buffers, it's not using interesting characters, it's just brain-damaged. The fact that it's also fetching different page numbers shows it's trying to follow page links and failing badly at doing so.
The site gets plenty of sniffing from garden-variety pests. e.g. this half-hearted attempt to find a framework or two that I don't have:
"POST
/__rsc HTTP/1.1"
"POST/api/auth/session HTTP/1.1"
"POST/api/auth HTTP/1.1"
"POST/__nextjs_action HTTP/1.1"
"POST/.action HTTP/1.1"
"POST/_rsc HTTP/1.1"
"POST/api/auth/callback HTTP/1.1"
"POST/_middleware HTTP/1.1"
"POST / HTTP/1.1"
(of course, none of these URLs exist other than
All this said... I've seen that spammers regularly misconfigure their tools, they'll try to register accounts with names like #[X:\LISTS\NAMES.TXT] and it only makes sense that some other cybercriminals trying to get rich quick have a similar lack of interest in programming shit correctly. Generally people don't turn to script kiddie shit if they have a personality conducive to putting in an honest hard day's work perfecting their craft.
I believe the plan was to give that sobriquet to Lake Michigan, in honour of its decidedly flaccid silhouette.
I had a problem where AI scrapers were absolutely DETERMINED to fish out every possible query string from a search results page. Almost all of the query strings they tried were invalid due to shitty and dysfunctional string substitution. "&page=100" wouldn't be followed by "&page=101", it would be followed by "&pag&pag=1010" or something even more insanely half-baked, until the query strings were like 100+ characters long. It was the technological equivalent of watching HIV mutate in real time.
But the insane thing was that, aside from page number, they were always requesting info about the same other criteria: filtered by the same user, the same page type, and with no text string. So I just took those particular values and started banning logged-out users who requested that combination of criteria.
I figured I'd need to change my tactics in a couple of days once the botnet got bored of that particular page and moved on to requesting bogus entries for another user.
MariaDB> select count(*) from ip_bans;
+----------+
| count(*) |
+----------+
| 671671 |
+----------+
It hasn't.
I regret to inform you that you have woefully underestimated it. The actual retail rate offered to consumers is closer to $2200 US per gallon. Sources: internet-ink.com, cbc.ca. This $14 million fine is only worth like, seven thousand gallons, or less than 200 oil barrels of ink.
By your powers combined, I am... the British Colonies!
The main aim of Stop Killing Games is to ensure the practice of rug-pulling eventually comes to an end. They are not trying to save MMOs, for example.
Moreover they don't demand that every game currently on the market comply with open-sourcing requirements: at a minimum, companies always have the option of simply providing customers with adequate notice before shutdown. Open-sourcing the server would be nice, but it's hardly the only way to protect consumers' interests. Scott has, for example, suggested game boxes being marked with an estimated expiry date for online service functionality.
But most importantly: because this is about future games, not the present, the market has time to change. If studios and publishers are designing their games with a fair EOL in mind, then they can make decisions from the get-go to avoid licensing dependencies that they won't be able to release in a possible 'afterlife' version of the game. As suggested by your example of GameSpy in C&C: Generals, when a commercial dependency is crucial to a game's success, it tends to be a client-side library, but typically the problematic dependencies aren't crucial; they're e.g. add-ons for Unity or Unreal that the studio bought to save time. In a world with SKG laws, the providers of these dependencies aren't going to be a stagnant target either—demand for compliant libraries will motivate development of open-source versions.
Interestingly, the will for doing this does exist among game developers; they just need the institutional support from legislation to twist the arms of the studios and publishers. Ross Scott has talked to a lot of devs who are burnt out from having their projects cancelled, leaving them with huge gaping holes in their resumes and portfolios where they've spent years on unreleased projects that are stuck under NDA. In general they tend to see SKG as a path to ensuring the games that do see the light of day aren't also scrapped, which would erode their work histories even further. (Apparently it also just plain feels bad to have your work erased from history. Shocking, I know.)
Fear not! It's entirely possible the category was chosen by an AI. Editorial automation would probably reduce the error rate here.
It's all a small price to pay for Eat Your Veggies.
Duke 3D's soundtrack was not exclusively the work of Bobby Prince; Lee Jackson, Apogee's go-to music guy, also did some of the tracks, including the title theme, Grabbag.
Prince used not only his MIDI skills but also his experience as a lawyer to ensure his 'inspired' derivatives were as close as legally possible to the originals. The relationship between individual tracks is often very clear and sometimes even hinted in the metadata of the source files.
We will never truly know how many dimensions the Chess game has.
Say it with me, now. As we all know, the infamous saying goes:
A COMPUTER
CAN NEVER BE HELD ACCOUNTABLE
THEREFORE A COMPUTER MUST NEVER
MAKE A MANAGEMENT DECISION
It's really incredible how marketing departments can radiate amnesia like this with such proficiency.
Well, what are you waiting for? Step on it!
(The idiots may also have been algorithms.)
Thank you for taking the time to read all that! You are right, of course. It is something of an unsolved problem with the design. The question of "exactly what work are these draftees contributing?" is something I'm still working on; it may not literally be core parenting or teaching work, but actually more like e.g. hanging out with your cool uncle on the weekend who helps you learn life lessons. Maybe said uncle isn't exactly teaching or parenting material, but he still has something to contribute to building a child's character, and is assisting the parents just by being around to lighten the load. The Big Brothers Big Sisters charity seems to indicate that this is a sound principle with incredible ROI.
There would also be mandatory training to teach people the skills needed to do this work (critical to figure out what goes in there.) Also I'd like to hope that the system would "even out" over a few generations; if we assume the root cause of dangerous personalities like BPD or NPD is being trapped (or in an echo chamber) with a toxic parent figure, the practice of this "socialized parenting" is essentially guaranteeing kids have alternative support networks that can soak some of those traumas. Efficiency would never reach 100%, of course (does it ever?) and there would always be some difficult people for whom alternative credit would need to be devised, but in any substantial system there's always other work to do—maybe a truly broken person contributes by grading homework or something.
You can just say openly that you're an edgy, racist teenager. It's fine; the first step to self-improvement is admitting that you need help.
To be awake is to be alive. -- Henry David Thoreau, in "Walden"
