Live data from Hacker News

Show HN: %%30%30: A Game

github.com

21–30 of 100 posts

Re: Show HN: %%30%30: A Game

#23

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

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.

Re: Show HN: %%30%30: A Game

#26

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

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.

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.

Re: Show HN: %%30%30: A Game

#27
post #25
post #21

Earlier quoted context omitted.

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

That's exactly how the game works!

thanks, I got it, but didn't realize it was THAT simple :)

more details here on the bug in chromium here: https://code.google.com/p/chromium/issues/detail?id=533361

Re: Show HN: %%30%30: A Game

#28

Earlier quoted context omitted.

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.

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.

"They just launch 'as if' they were native." That's a pretty big benefit to most end-users.

Re: Show HN: %%30%30: A Game

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

Re: Show HN: %%30%30: A Game

#30

Earlier quoted context omitted.

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.

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.

Well, the benefits of Electron or NW.js compared to a Web App are things like filesystem access - as well as the entire Node JS ecosystem, which has many modules, some capable of performing native operations in a variety of different platforms.
Post reply on HN