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.
Current biggest is 14tb
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.
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
It’s basically everything. Tweets, quoted tweets, replies, and even ads all count against the limit. I’ve seen people saying they hit the limit in under 10 minutes of scrolling. One person said they only managed to post two tweets before being limited.
And from what I understand spam bots are mostly unaffected since they’re already rate limited for reads (but not posts).
Some math functions have slightly different results depending on architecture and OS, so they fuzz the results a little. Here’s a tor issue discussing the problem: https://gitlab.torproject.org/legacy/trac/-/issues/13018