Scaless

I was about to make a similar comment. One property of coal plants is that they can't ramp up or down very well with usage demands. I have a friend that operates at a coal plant where they installed miners to run during off hours when the demand is low, so rather than running at a loss during that period they more or less break even. It definitely would tip the balance for keeping that plant running for longer rather than replacing it with better alternatives.

What you are hearing as "suspense" is likely "sus". "sus" is short for "suspicious", and was popularized by the viral video game 'Among Us'.

I have a new Kagi account with no custom rankings and I see the same terrible results. Basically the same as what he describes. yt-dlp is not found at all, the 2010 link to youtube-dl, and a bunch of spam sites.

For non-geniuses like myself, you can just ask to test out of some of the lower tier introduction courses. I got a typically 4-year degree in 3 years this way. It's called credit-by-examination.

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

As of a few months ago, Reddit no longer allows linking directly linking to their hosted images. You are directed to a pseudo-page that links back to original thread it was posted in.

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

I am not much of a conspiracy theorist, but after going to the Hetzner site to look at my support history I was presented with this:

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

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

In my experience support will gaslight you into thinking it is your problem. I had a Hetzner server that was shutting off at random hours several times per week.

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.

It is not "solved" at all. std::bitset has terrible properties and an awful interface.

1. No dynamic resize, have to know size at compile time or allocate based on max expectations. And yes, std::vector<bool> 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.

WD externals were extremely popular a few years ago because they contained standard WD Reds at $20 under normal market rate. Really easy to shuck the case and slap it in your NAS. I bought about a dozen myself. Of course the people who did what burned you ruined it for the rest of us, and now they build the externals with custom pinouts on the drives.

It is not just crypto, it has been happening in gaming communities for a long time. Sometimes it's just fishing for more of their own page views, other times it it more malicious such as offering a trojaned game client that will steal your login details [0]. It is very cheap and easy to do because the communities are relatively small.

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

websockets unfortunately have to start at the HTTP layer and negotiate down to the TCP wrapper layer, so you need at least a partial HTTP stack and everything else that involves to get there. This complicates things a lot. It's like stuffing a turkey, cooking it, then throwing away the meat to just eat the stuffing.

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...

Gamasutra IS Game Developer now, they rebranded recently.

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

The scripting language for Halo 1/2/3/ODST/Reach were based on Lisp. Halo 4 kept a similar syntax but got rid of the parentheses to be more BASIC-like. Halo 5 and now Infinite moved on completely to Lua.

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

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

For Mumble in particular, the devs had their heads in the clouds for so long that it is no surprise that it is no longer relevant.

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

Sorry if I did not explain it well, TAS does not mean just small helpful enhancements.

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.

Anyone who even remotely looked at the numbers and followed the situation can tell Dream cheated. The only people I see claiming otherwise are either infatuated with his cult of personality or otherwise just don't give a shit, "It's just a kids game who cares"? I care.

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.

At that point why even show the masked emails at all? All you're doing is leaking people who use their own custom domains (e.g. XXXX@myname.com), and XXXX@gmail.com isn't going to help me know who that person is either.

gamepad mapping can't be configured

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.

In a proper system this is something that should be self-reported and not handled by the employer. An example:

$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.

6 years later, nothing's changed.

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

Stay far, far away from godaddy.

I am not Australian and have not seen any updates since it was passed, but "forcing companies to build backdoors" is a massive understatement. The government could effectively compel any employee to act as a spy, without their consent. Don't want to play along? Go directly to jail.

The new law also allows officials to approach specific individuals—such as key employees within a company—with these demands, rather than the institution itself. In practice, they can force the engineer or IT administrator in charge of vetting and pushing out a product's updates to undermine its security. In some situations, the government could even compel the individual or a small group of people to carry this out in secret. Under the Australian law, companies that fail or refuse to comply with these orders will face fines up to about $7.3 million. Individuals who resist could face prison time.

https://www.wired.com/story/australia-encryption-law-global-...

The wording is very clear, you can NOT require login to change subscription settings. A password would classify as additional information outside of email address and preferences. Otherwise someone could sign up with your email and you would have no recourse to end the spam, or the company could just bulk create accounts for you without any way to log in (i.e. Facebook).

Yes, what they're doing is illegal. [1]

§ 316.5 Prohibition on charging a fee or imposing other requirements on recipients who wish to opt out.

Neither a sender nor any person acting on behalf of a sender may require that any recipient pay any fee, provide any information other than the recipient's electronic mail address and opt-out preferences, or take any other steps except sending a reply electronic mail message or visiting a single Internet Web page, in order to:

(a) Use a return electronic mail address or other Internet-based mechanism, required by 15 U.S.C. 7704(a)(3), to submit a request not to receive future commercial electronic mail messages from a sender;

[1] https://www.law.cornell.edu/cfr/text/16/316.5

Let's actually look at where it's being used.

html metadata - once in a <title> tag, once <meta name=title>, another in a <meta property=og:title>, another in a <meta name="twitter:title">. Probably some duplication for compatibility and different platforms.

2 times in <link rel=alternate> tags, for alternate versions of the site.

Actual displayed title below the video.

Suggested playlist mix - twice, one is the html tag 'title' and the other is the tag content.

Once for a title over the top of the video if the player is embedded in an iframe.

Once in a minified blob of javascript.

Basically all of these are ok use cases for duplicating data in the HTML. It's not excessive at all and I would have actually expected much more.

I don't know why the existence of metadata is a shock to the author.

You are more or less describing the architecture of the PlayStation 3: https://en.wikipedia.org/wiki/PlayStation_3_technical_specif...

The problem with this type of system is both the software and OS have to be aware of what is or isn't a "main thread" job. You have to architect your whole program around job systems to spread your data between the main thread and sub-processes which was a major complaint of gamedevs for the PS3. There's also the fact that many consumer software developers just don't care and will flag all of their processes as high priority jobs.

It worked out decently well on PS3 because it was such a locked down system, but for a general purpose desktop it would be utter chaos.

Every single news organization has read the original study wrong or parroted another article about the 90% figure. The full quote from the study [1] is "the top-ten rivers with the highest loads contribute ~90% of the total river-driven plastic inputs into the sea."

The top 10 rivers contribute 90% to RIVER-DRIVEN plastic input, not TOTAL input. It is still a large problem, but a vast amount of ocean trash is dumped by coastal cities in Asia.

[1] https://www.ufz.de/export/data/2/149396_EGU_2017_Schmidt.pdf