skeezix
Internal Development
Probably supposed to be 0a three times but sometimes it gets a typo version due to .. Sunspots
Jeffphone
Jeffphone
Probably supposed to be 0a three times but sometimes it gets a typo version due to .. Sunspots
Jeffphone
And the ages old issue that you end on an error page when going to http://apps.openpandora.org and directly click "New Uploads" still ain't fixed. A workaround is first clicking in the top left corner when going to apps.openpandora.org. Though this is really not nice, since a plain apache redirect on apps.openpandora.org itself (when going there) would solve this issue!
The page you end at is: http://apps.openpandora.org/latestapps.shtml
The correct page you *should* end at would be: http://apps.openpandora.org/apps/latestapps.shtml
BTW a comment regarding a 100% wrong entry: http://apps.open-pandora.org/cgi-bin/viewapp.pl?/Emulator/snes9x4d4p.inf
The license is NOT gplv2! It is a "as-is non-commercial" kind of license.
Appears on my Linux desktop in Firefox 3.6.15, and on my Pandora in Firefox, Chromium, and Midori, and even on my BeagleBoard.
It's a hex sequence 0x0AA0 (which is an invalid unicode encoding, hence the �) followed by 0x0A, which is just a line feed. That's the one in the very top left. It appears even before DOCTYPE element, so almost definitely a server problem I think.
The second one is basically the same. It's 3 line feeds (0x0A) followed by this invalid unicode encoding (0xAA0) and another line feed.
Check your source, delete all the blank lines that appear before "<div id="apptitle">" and see if that helps.
wget -O /dev/stdout -q 'http://apps.open-pandora.org/' | perl -e 'while(<STDIN>) { print unpack("H*",$_) }'
And all three of them would disappear if Craig wrapped the http://twitter.com/PandoraApps link in quotes.
<a href="http://twitter.com/PandoraApps">Click to follow Pandora Apps on twitter</a>
So long as it doesn't contain any special characters, such as a forward slash, you are correct. The standard doesn't require there be quotes around everything, just some things with the potential for ambiguous parsing.I don't succumb to that stuff. It's meaningless. It makes absolutely no difference. Only pedants notice
What's the sort order? It kinda looks like most recent first. If that's just an illusion, perhaps it should be an option.
So long as it doesn't contain any special characters, such as a forward slash, you are correct. The standard doesn't require there be quotes around everything, just some things with the potential for ambiguous parsing.I don't succumb to that stuff. It's meaningless. It makes absolutely no difference. Only pedants notice
People blatantly ignoring the standard is why Microsoft had to write so many hacks into IE, which ultimately lead to so many very-wrong websites not working in browsers that tried to do things right.
Seriously, 3 errors away from being 100% compliant, and all 3 are the result of not wrapping a single anchor href in quotes. Two characters, that's all, is keeping your site from getting a 100% rating.