I'm pretty sure whoever designed this control usually makes gender selectors for websites...
Poly Bridge has a language SLIDER.
so they won without placing any bridge pieces? that sounds hard.
Sadly, no: they've moved to a much more sensible drop-down
name length: [slider 1-10]
letter 1: [slider a-z]
letter 2: [slider a-z]
letter 3: [slider a-z]
1. the leaderboard contains videos. these are just mp4 files of the game being played
2. the leaderboard contains the data for the bridge designs, and it's being rendered in-game
and even though people aren't hacking 0$ wins into the leaderboard now doesn't mean they aren't cheating. They just do it with physics, not RAM hacking
They made a "bridge" which is a bit of dense road that falls and crushes the car, but since cars can't "crush", the physics engine ends up squirting them out like a watermelon seed
1. it's talking to cloudflare
2. it's using TLS
3. it's probably about 750 kilobytes for one playback
and #1 and #3 mean it's probably just videos. tiny videos.
does it compress the videos in the client and upload them to the server?
or does it upload the solution to the server and let it render them?
More from foone
More from Software
As the year wrap's up, let's run through some of the worst public security mistakes and delays in fixes by AWS in 2020. A thread.
First, that time when an AWS employee posted confidential AWS customer information including including AWS access keys for those customer accounts to
Discovery by @SpenGietz that you can disable CloudTrail without triggering GuardDuty by using cloudtrail:PutEventSelectors to filter all events.
Amazon launched their bug bounty, but specifically excluded AWS, which has no bug bounty.
Repeated, over and over again examples of AWS having no change control over their Managed IAM policies, including the mistaken release of CheesepuffsServiceRolePolicy, AWSServiceRoleForThorInternalDevPolicy, AWSCodeArtifactReadOnlyAccess.json, AmazonCirrusGammaRoleForInstaller.
First, that time when an AWS employee posted confidential AWS customer information including including AWS access keys for those customer accounts to
Fresh data breach news-
— Chris Vickery (@VickerySec) January 23, 2020
Amazon AWS engineer exposes work-related keys, passwords, and documents marked "Amazon Confidential" via public Github repository: https://t.co/7gkIegnslx
Discovered within 30 minutes of exposure by my team at @UpGuard.
Discovery by @SpenGietz that you can disable CloudTrail without triggering GuardDuty by using cloudtrail:PutEventSelectors to filter all events.
"Disable" most #AWS #CloudTrail logging without triggering #GuardDuty:https://t.co/zVe4uSHog9
— Rhino Security Labs (@RhinoSecurity) April 23, 2020
Reported to AWS Security and it is not a bug.
Amazon launched their bug bounty, but specifically excluded AWS, which has no bug bounty.
Amazon Vulnerability Research Program - Doesn't include AWS D:https://t.co/stJHDG68pj#BugBounty #AWS
— Spencer Gietzen (@SpenGietz) April 22, 2020
Repeated, over and over again examples of AWS having no change control over their Managed IAM policies, including the mistaken release of CheesepuffsServiceRolePolicy, AWSServiceRoleForThorInternalDevPolicy, AWSCodeArtifactReadOnlyAccess.json, AmazonCirrusGammaRoleForInstaller.