everconfused wrote:
dolphinling wrote:
Is it just me, or does this not do anything for non-premium yet? I've tested a bunch of things and it seems to be acting just the way it always did, checkbox checked or not.
If I understand what it is I think they're doing, though.. Gah. It's better than what they used to have—a lot better than what they used to have—but still not perfect.
I have not tried using this on my unpremium spare (I really need to log in there and feed my pets!), so I don't know if it's not doing anything or if your coding is good *shrug*.
If you get a chance, would you mind testing? I know my coding is good, but I was intentionally making it
bad to test, and it still didn't filter it.
everconfused wrote:
If what you think they're doing is trying to filter "bad" stuff and basically putting the responsibility on us, the players, then that is kind of what it is. No, it's not perfect - better, but not perfect. Don't think perfection is possible, is it? I do think the programmers should be going through the site and finding the holes that allow this stuff in the first place and fix them. And have this coding "pass" method.
Actually, filtering out bad stuff is what they used to do, and is why there were so many holes—it just doesn't work. What they're doing now is the exact opposite: filtering
in good stuff, and throwing everything else out.
That's much safer, because if there's something new you don't know about, it's automatically filtered away until you decide if it's safe or not. The only thing I'm concerned about is the specific way they're doing it. It
is possible to do it perfectly—in fact, it's possible to do it perfectly in a number of different ways, but some ways are more bug prone and a really clever hacker* might be able to exploit one unless they're careful, whereas other ways are much less likely to get bugs.
* By "really clever" I mean black-box testing a system to find a problem in the way it outputs things that can be exploited, not oops, here's a hole in the filter.
everconfused wrote:
I for one actually hope they don't allow music anymore. I know it was banned for awhile, then people found a code that worked around the filters for it. Don't like music, makes pages take way long to load or even freeze the browser and if I have my speakers on, it's like
sometimes.
Sound/music can be put in a page in three ways: <object>, which is the HTML standard way of doing it, <embed>, which is an old non-standard way of doing it, which basically identical to object except for syntax, and <bgsound>, which is a non-standard, IE-only way, which only works for sound.
Neopets never allowed <object>. <bgsound> is, as far as I know, still allowed. <embed> used to be allowed, and they would only allow you to link to files ending in .mid, .midi, or .mp3 so that you could only put sound in there and not, e.g., flash or javascript*. The problem, as I showed them, is that you can name a file one way and have it
be something else, so checking the filename doesn't work.
In fact, it's pretty much impossible for them to know ahead of time what kind of file is in an <embed>, so they have to disallow it completely.
* It's not possible to use javascript
directly through an <embed>, but you can set it up to work through something else.
Also, don't ask why they allowed <embed> and not <object> even though they're functionally identical... I have no idea.
Nabile pwns you...
...At Lenny Connundrum.