I'm sure for the prodigy-level students there is an even higher streamlined process for keeping them engaged.

This sucks because it's now not possible to use the browser's built-in image viewer which has better UX.

I am expecting them to eventually put ads on the page as well.

Random example: https://i.redd.it/144knacbw3rb1.jpg

https://i.imgur.com/3DKc9OC.png

I have never seen this page before when trying to login. Make of that what you will.

I showed them the sudden loss of power events in the logs. "It must be a problem with your OS modifications that we don't support".

OK, I wiped the machine to the stock image that you provide and it's still having power loss events. "Sure, we'll run a stress test for a couple minutes ... stress test passed OK, it's still your fault!".

The events happen randomly during the week, a stress test is not going to show that. Can you just move me to a different physical machine? "No."

This was over the course of several days, when I had an event coming up that I NEEDED the server for. I ended up going back to Azure and paying 10x the cost, but at least it worked great.

1. No dynamic resize, have to know size at compile time or allocate based on max expectations. And yes, std::vector sucks too.

2. Despite being only statically sized, several classes of bugs are not prevented at compile-time. For example:

std::bitset<4> fail1{"10001"}; // This produces a value of 0b1000, no warnings or exceptions thrown

std::bitset<10> fail2; fail2.set(11); // Exception at runtime. Why is this not a static_assert?

3. Size is implementation defined. std::bitset<1> can use up to 8 bytes depending on compiler/platform.

4. Debug performance is 20x slower than Release. In many cases you are going from what would be a single assembly instruction to multiple function calls.

5. Limited options for accessing underlying storage efficiently (for serialization, etc). to_ullong() will work up to 64 bits, but beyond that it will throw exceptions.

6. Uses exceptions. This is still a deal breaker for many.

7. Cannot toggle a range of bits at once. It's either one or all.

[0] https://old.reddit.com/r/2007scape/comments/95zk30/psa_first...

In my experience, Boost Beast[1] is the easiest library to just get going with but you have to deal with all the Boost-isms that comes with. libwebsockets is the 'standard' C implementation but unless you know the websocket RFC front to back it's quite difficult to work with and has a lot of foot-guns.

[1] https://www.boost.org/doc/libs/1_78_0/libs/beast/example/web...

https://www.gamasutra.com/view/news/387227/Gamasutra_is_beco...

Halo 1 reference: https://andrew.gg/scripts/00reference.html

Decompiled campaign scripts: https://github.com/Nibre/blamscript/blob/master/blamscript/h...

If you had a mic that had issues in any way (buzzing, volume, balance), "The Wizard" and "AGC" were supposed to fix it for you. Do not fret little one, for you do not need nor want to manually fiddle with settings, The Wizard will make everything right [1]!

The pivotal feature that was the reason so many people I know stopped using it is the ability to change the volume of an individual person [2]. It has been a requested feature since the beginning of time, yet it took until 2016 to implement in dev branch and didn't actually make it into a release version until 2020! Too little, too late.

[1] https://web.archive.org/web/20200223143654/https://wiki.mumb...

[2] https://github.com/mumble-voip/mumble/issues/1156

In a TAS, the game is being played by the computer using a series of pre-programmed inputs. The fun in TASing is creating the most optimized set of inputs that completes the game in the shortest amount of time. There are often precise one-frame tricks or inputs that would not be possible for a human to perform but can be done easily when you can fully control what happens on each individual frame of gameplay.

Mixing TAS and non-TAS runs doesn't make much sense as humans would never be able to compete.

I am heavily invested in speedrunning culture, but myself am mostly involved in the Halo community. I have a couple of world records of my own, and I also do routing and other technical things for the community.

Halo has its own long history of cheaters, many of whom were also pivotal founders of the community. In the wider speedrunning scene there are many examples of similar situations. I do not think that speedrunning necessarily has a higher percentage of cheaters, if you compare against other competitive sports and activities the rates would likely be comparable. But that number is far from zero.

I am working on developing TAS (Tool-Assisted Speedrun) tools for the Halo games. With the tools you can create frame-perfect recreations of gameplay that are indistinguishable from actual play.

I am honestly at a stand-still on whether I should ever publicly release a working version of the tools. The main worry is that the tools will be used to submit "fake" runs passed off as human gameplay. I have built in basic safeguards to deter the most basic cheaters, little things that you would never see as a casual player but if you know what to look for would stand out in a video. But there is always the chance a sophisticated user could reverse those changes and fly under the radar.

On the one hand it could open a floodgate of awesome content, tricks, and discoveries. On the other it could potentially completely ruin the integrity of the leaderboards. I am quite conflicted on how to continue with this project if anyone has any insight that might be helpful.

Click the wrench next to controller 1/2, click in each of the input boxes and press the button on the controller to map it. I had no issues setting up my XB1 controller.

$Employer gives you a form to fill out with your disabilities and their Employer ID#. You fill out the form (if you get hired) and send it to $GovernmentAgency yourself. $Employer lets $GovernmentAgency know that they hired you. $GovernmentAgency gives a quarterly statement to $Employer without any specific information tied to individuals.

Same thing with race, sex, age, and all the other affirmative action qualifiers. These are really things that employers should not know or care about in the hiring process.

As it is, don't feel bad about lying on the forms with stuff like this. The system is rigged against you, don't give them any more ground if you don't have to.

https://techcrunch.com/2014/01/29/godaddy-admits-hackers-soc...

Stay far, far away from godaddy.