Show HN: %%30%30: A Game

You probably want to make it more clear that you're supposed to mouse over the dark lollipops and avoid the blue trees. I assumed the dark chars were the walls I shouldn't touch and just about gave up on it after it was constantly crashing. Then I read the description after the fold and figured it out.

Also why not just implement the game in javascript using mouse position events and a canvas for drawing?

szhu9• 11 years ago

Dark lollipops? Blue trees? What operating system are you using? I'm on a Mac and the lollipops are pink and the trees dark green. I'm considering making a text-only version for people who have weird or no emoji support.

Of course I could implement the game in javascript, with nice graphics and all, and perhaps gameplay that works in all browsers and doesn't crash Chrome, but wouldn't that defeat the point of the game? :)

Happy to take PRs though!

staz• 11 years ago

I'm on Chromium on Ubuntu. Also have Dark lollipops and Blue trees, guest it depends on the font or something.

https://imgur.com/Ffc3zcx

tokenizerrr• 11 years ago

That is how they appear on windows.

nness• 11 years ago

Lime green lollipops and dark green trees on Chrome for Android.

mikepalmer• 11 years ago

what?? you're crazy, mine are white and gold!!

strangecasts2• 11 years ago

It's a shame <marquee> is gone, otherwise you could've put in moving barriers ;)

ikeboy2• 11 years ago

Windows 10, Chrome, https://i.imgur.com/fMrRYPN.png

leni5362• 11 years ago

The trees inherit #4078c0 from "a" on chrome. The lollipops are #333 inherited from "body". I see exactly that on linux, I have GNU unifont installed. I guess since Mac's are using colorful bitmap emoticons they simply disregard the color property.

edit:

weird or no emoji support.

I think Apple's emoji support is the weird one. It's a font glyph, it should respect the color property.

szhu9• 11 years ago

Here's a suggestion that replaces the lollipops with something else. Please comment on the PR if you prefer it instead— https://github.com/szhu/3030/pull/2

theon144• 11 years ago

Also why not just implement the game in javascript using mouse position events and a canvas for drawing?

Sorry for being blunt, but is this sarcasm, or did you absolutely miss the point of the "game"?

branchan• 11 years ago

Whoosh?

scott_hardy• 11 years ago

Amazing. I always love seeing these sorts of harmless, fun ways that bring attention to these strange edge/corner case bugs.

szhu9• 11 years ago

https://github.com/szhu/3030/issues/12

"harmless"

oops.

rigaspapas• 11 years ago

This game has free graphics upgrade if you use "Emoji Input by EmojiStuff.com" extension

ps4fanboy3• 11 years ago

http://github.com/%%30%30 pasting this in slack also crashes Slack.

szhu9• 11 years ago

I had to switch back from Atom to Sublime to make this, because Atom is based on Chromium :(

haddr2• 11 years ago

even hovering mouse over this link in the comment above crashes chrome

szhu9• 11 years ago

That's exactly how the game works!

fotcorn• 11 years ago

Funnily enough, opening this url gives a GitHub Server Error.

r3bl2• 11 years ago

Yup, opening this on my own website (hosted using GitHub's repositories) also gave me an error.

dshankar• 11 years ago

Explanation for why this is occurring:

Slack's desktop apps are HTML5 webapps wrapped inside native desktop wrappers. Specifically, Slack uses Github's Electron (formerly, Atom Shell) which is basically Chromium. The desktop app is a webpage inside Chromium.

JoeAltmaier• 11 years ago

Yeah, I strenuously object to the fad of calling wrapped web pages 'native apps'. They get zero benefits that would normally accrue to real native apps. They just launch 'as if' they were native.

userbinator3• 11 years ago

I wonder how many other apps will also have this bug due to being a webapp inside Chromium, and thus require updating when it's fixed. It's not Heartbleed-like criticality, but still seems rather unpleasant, not to mention the waste of keeping multiple copies of Chromium around (I'd guess the typical webapp is much smaller than the browser itself.)

eridius• 11 years ago

It's Chromium? Then why do the Slack folks keep saying the preferences UI bug is a Webkit bug? It can't be a Webkit bug if they're using Chromium.

ps4fanboy3• 11 years ago

If you paste the link in chrome and visit it, crashes the whole browser not just the tab.

cbd1984• 11 years ago

My little web client just prints this header with no body:

    HTTP/1.1 302 Found
    Connection: close
    Pragma: no-cache
    cache-control: no-cache
    Location: /%%30%30

Maybe the infinite loop is the real problem here.

0xCMP• 11 years ago

Hovering over this link also makes it crash like when you hover over the trees

userbinator3• 11 years ago

You know you've been working with ASCII for a long time when you can automatically unescape the title... and then pause, considering whether to unescape again.

I think reading the comments on that bug is also rather enlightening; points of note include a 62-level-deep stack trace, comments to the effect of "we don't know what the bug is/how this is supposed to work", and discussions about whether escaping multiple times is the solution (absolutely not!)

https://tools.ietf.org/html/rfc3986#section-2.4

Implementations must not percent-encode or decode the same string more than once, as decoding an already decoded string might lead to misinterpreting a percent data octet as the beginning of a percent-encoding, or vice versa in the case of percent-encoding an already percent-encoded string.

Seriously, I'm quite surprised that basic URL handling is still a problem. Making a game to bring this to the attention of a wider audience is certainly a good idea.

X-Istence• 11 years ago

Reading the bug report: https://code.google.com/p/chromium/issues/detail?id=533361 makes me sad. Recursing is definitely not the answer, yet it gets brought up a lot.

Also, %00 shouldn't cause the browser to crash, and the fixes suggested so far are just work-arounds :/

username223• 11 years ago

Recursing is definitely not the answer, yet it gets brought up a lot.

Speaking as someone with an apostrophe in his name, I'm not sure whether this makes me want to chuckle and reach for the popcorn, or bang my head against the desk. The answer to multiple (un-)escaping bugs is never recursion.

aaggarwal• 11 years ago

It's surprising that this issue was brought up multiple times as a bug, but wasn't taken seriously until it got special attention. This bug is definitely notorious, I wonder setting a similar URL as the homepage of Chrome will cause Chrome to continuously crash and make it useless.

userbinator3• 11 years ago

The crash was definitely not there in the beginning, since I happened to have Chromium 22 (from 2012 - when I first tried it), and although it doesn't crash with %%30%30, it also refuses to visit such a URL. Someone with suitable tools should be able to do some bisection to narrow down exactly when it was introduced.

Nitramp• 11 years ago

Seriously, I'm quite surprised that basic URL handling is still a problem. Making a game to bring this to the attention of a wider audience is certainly a good idea.

I think the problem is that a spec exists, but existing browser incorrectly implemented it (hello Netscape), and given their prevalence browsers are stuck with weird hacks so that existing websites continue to work.

In particular around percent escapes there's lots of trouble. Nothing really specs the encoding to be used for those percent escapes (the RFC only has some odd notes on encodings), and there's a whole bunch of odd behaviours, e.g. how characters are handled when pasting a URL into an address bar vs having it as an href on a web page.

andersonmvd• 11 years ago

Creative. Nice project.

fidz• 11 years ago

This is a beautiful experiment.

To OP: i wonder, how did you find this bug?

szhu9• 11 years ago

It's actually all over the news right now: https://www.google.com/search?q=chrome+url+bug

I found it because someone posted about it in a school Facebook group I am in.

bobajeff2• 11 years ago

This works in Chrome on Android as well. Of course it's way easier than on desktop.

ikeboy2• 11 years ago

Not for me: https://i.imgur.com/bzScUUn.png

bobajeff2• 11 years ago

Try it in landscape mode.

rjuyal• 11 years ago

Aw snap! Always.

deckar01• 11 years ago

My inspector even crashes when trying to hover over the link node!

spacesword• 11 years ago

Works with Opera 32 as well.

Mithaldu• 11 years ago

Of course. It is just a chrome fork with minimal changes.

kyberias• 11 years ago

Crashes my Chrome (Windows) when I move mouse pointer over the game area.

cosarara97• 11 years ago

That's the point.

cremno• 11 years ago

Poor CloudApp Support:

https://github.com/szhu/3030/issues/3#issuecomment-141854443

kodingana• 11 years ago

You can jump over the wall by scrolling your mouse! :D

zobzu• 11 years ago

hah, another chrome-only thing

infinita740• 11 years ago

The game doesn't "work" on microsoft edge but the brower doesnt recognize the Stanford links[0] , it is not possible to copy them by right clicking. Going directly to the page by copy/pasting the url doesn't even load the website. IE doesn't seem to understand the url as well.

The only brower I've tried that manages to get a page is firefox[1]

[0]http://www.stanford.edu/%%30%30

[1]http://i.imgur.com/nEDgBrq.png

vor0nwe• 11 years ago

Old Opera 12.17 (last version that still allows specifying a different proxy than the system one, afaics) shows the same page as Firefox. Elinks does as well.

scotty79• 11 years ago

Nice. It crashes my Chrome on hover over trees.

mrcncpt• 11 years ago

This weirdly makes my external monitor flash black when I open this tab. What's going on here?

https://vid.me/dWW7

k_bx• 11 years ago

I like how this crashes Twitter app's "preview" browser with app itself.

Show HN: %%30%30: A Game

Related Stories