No, this is clearly Stargate Command. It's even in the same place!

Last year Unity merged with ironSource - a "mobile monetization and distribution" company that was once blacklisted by Microsoft for developing and distributing actual malware. I'd assume the tracking is done via a product brought over from that side of the business.

That second one is apparently sub-ms latency, which is incredibly unnecessary for a TV.

Why bother actually installing? Just use a packet sniffer to find the data being sent to Unity and replay it in a loop. You could probably hit somewhere in the range of 100k-1M "installs" per minute.

Imagine wanting to run software locally on hardware you already own instead of paying someone else to run it on theirs.

Is it fiber or copper? Copper is probably not going to get you that far, but fiber can supposedly still deliver a decent signal at up to 60m.

Permanently Deleted

Still is 3 hours after you. What are we up to, 27 hours and counting?

Yup. The binary is precompiled proc macros. Should save a negligible amount of time...

GN released a followup this morning addressing his response. The bit about "already" having an agreement to compensate Billet Labs is nothing more than a bald-faced lie. He reached out after the GN video, and Billet hadn't yet responded when GN asked them about it. Billet is not "good" as he claimed in another post.

He posted on the LTT forums, which seem to be down atm.

EDIT: Someone on Reddit posted a screenshot: https://i.redd.it/dh24b8ss85ib1.jpg

I'm not sure how Celeste does it specifically, but I think the important part is just being able to jump for a few extra frames after leaving a surface. I'd try it both ways and just go with whichever feels better.

My gut feeling is that gravity off will feel better, because it keeps your max jump height the same as it would be if you jumped before coyote time. It keeps things more predictable. Gravity on will mean that the max height gets slightly lower for each frame of coyote time before the jump starts.

Oh man I didn't even see that in the menu. That is handy.

Secure is what you're looking for.

It seems they're basically DDOSing themselves.

This is second-hand, so take it with a grain of salt, but I've seen mention of a bug that sometimes causes the same graphql query to be executed in an infinite loop (presumably they're async requests, so the browser wouldn't lock and the user wouldn't even notice).

So they may essentially be getting DDOS'd by their own users due to a bug on their end.

Edit: better info: https://sfba.social/@sysop408/110639435788921057