you seem to be confusing law with freedom of speech, which is limitless. that's what freedom means. if you're not free to say something, you dont have complete freedom of speech. it doesnt matter what you're saying.
in addition, i'd like them to ship me the liner notes, along with a physical copy of the music on some sort of portable media that's compatibile with my car stereo. and some kind of case to put the media in.
it will have to be more complex than that, unless they're not trying to block P2P. that would only work for stuff like http and ftp, and i imagine most of the "problem" is with p2p.
on a more serious note, with its very different license, i imagine it'd be more likely to get support from those outside the FOSS community. whether or not that's a good this is a matter of opinion.
mmm, but as is often brought up (though i'm not an expert on the matter), producing new cars to replace gas-guzzlers may expell more emissions and/or use more energy than the gas-guzzlers did in the first place. a better solution might be to get people to stop buying new cars every 2 years, and instead fix up the older, high-MPG ones.
couldnt we do the same thing? have the dead-guy furnace fueled by burning dead-guys? seems like that would work until we run out of dead-guys. we'd have to keep making more dead-guys.
And, no, I don't consider replacing all "<"s with a lt; is the right answer, either, since sometimes you really do need to accept markup from the user.
true, but i think the first step is identifying when you do and dont want to accept markup. when you dont, the solution is cut and dry, very easy: filter the output. you never have to worry about that part again.
you only need to focus on the parts that do accept user markup. depending on the context, it may be easy, maybe not. webmail for example, i dont see an easy solution there. XML parsing isnt adequate because it probably wont be in XHTML, and by the time your server gets the email it's too late to tell the user to fix the markup.
but, for something like a blog post where the user is composing the markup on your server, that's when XML parsing shines. you can use the user's browser to parse their markup into a DOM structure, then have a function that goes through the DOM and creates a valid XML document string. upload that XML document string to the server and do the XML parsing and reformatting server-side.
one way to do it: only allow 100% valid XHTML (and thus, XML). when it's being uploaded, send it into an XML parser, then it's quite easy to find malicious tags (like script or iframe). just iterate through the document tree. if everything's ok, print the XML document back out to a string again and save that copy, not the copy the user uploaded.
there is a very simple solution to XSS this that is rarely followed:
never, i repeat, never print out a user-editable string variable directly to a web page. send every single one through a function that, at the very least, replaces all '<' and '>' to '<' and >
well, the best way to explain the oddities here: you can never move at the speed of light, so you dont really have to understand what it would be like to do it. only the photon can, and presumably the photon isnt sentient, so no one/nothing ever experiences what it's light to move at the speed of light.
you can, however, move at 99.999999999% the speed of light. at that speed, you wouldnt notice anything weird about your time, but it would seem like the rest of the universe was passing by (in time) much faster than it should be. you could, for example, only be travelling at that speed for what felt like a few seconds, but when you're done most of the universe could have passed by many years.
yes, but you have to factor in what percent of the population lives in podunk Montana. i'd be willing to best most of the US lives in areas where broadband is available.
sure thing, court. you supply us with the hard disk space to store any and everything that gets put on my RAM, and i'll get right on that. i presume you'd like full copies of every moment... so lets see... the front side bus is 800MHz and we have 16gigs of RAM, so we'll be needing 400 bajillion GBs of space.
Slashdot Mirror
i was thinking the same thing, but actually kdawson added that little tidbit, not d4a :)
yes, because no one says that when they actually mean it.
you're new to the internets, arent you?
i think the point is that criminals are already being monitored, but no one's monitoring the cops.
no, all 9 are patched. 0 unpatched.
you seem to be confusing law with freedom of speech, which is limitless. that's what freedom means. if you're not free to say something, you dont have complete freedom of speech. it doesnt matter what you're saying.
I store photos in SVG, you insensitive clod!
and who draws the line as to what does and doesnt encroach on other people's rights, freedoms, and safety?
i agree.
in addition, i'd like them to ship me the liner notes, along with a physical copy of the music on some sort of portable media that's compatibile with my car stereo. and some kind of case to put the media in.
yeah, that'll never happen.
holy crap, these are damn good prices. any info on linux compatibility with the hardware? care to share your experiences?
it will have to be more complex than that, unless they're not trying to block P2P. that would only work for stuff like http and ftp, and i imagine most of the "problem" is with p2p.
twice the leetness!
on a more serious note, with its very different license, i imagine it'd be more likely to get support from those outside the FOSS community. whether or not that's a good this is a matter of opinion.
mmm, but as is often brought up (though i'm not an expert on the matter), producing new cars to replace gas-guzzlers may expell more emissions and/or use more energy than the gas-guzzlers did in the first place. a better solution might be to get people to stop buying new cars every 2 years, and instead fix up the older, high-MPG ones.
couldnt we do the same thing? have the dead-guy furnace fueled by burning dead-guys? seems like that would work until we run out of dead-guys. we'd have to keep making more dead-guys.
this is getting a big crass.
hemp.
what were we talking about again?
you only need to focus on the parts that do accept user markup. depending on the context, it may be easy, maybe not. webmail for example, i dont see an easy solution there. XML parsing isnt adequate because it probably wont be in XHTML, and by the time your server gets the email it's too late to tell the user to fix the markup.
but, for something like a blog post where the user is composing the markup on your server, that's when XML parsing shines. you can use the user's browser to parse their markup into a DOM structure, then have a function that goes through the DOM and creates a valid XML document string. upload that XML document string to the server and do the XML parsing and reformatting server-side.
gah, guess i should have RTFA. didnt realize we were talking about webmail.
i actually wrote code in C# that does just this (and gets rid of/replaces unallowed tags), but unfortunately my employer owns it :-/
one way to do it: only allow 100% valid XHTML (and thus, XML). when it's being uploaded, send it into an XML parser, then it's quite easy to find malicious tags (like script or iframe). just iterate through the document tree. if everything's ok, print the XML document back out to a string again and save that copy, not the copy the user uploaded.
there is a very simple solution to XSS this that is rarely followed:
never, i repeat, never print out a user-editable string variable directly to a web page. send every single one through a function that, at the very least, replaces all '<' and '>' to '<' and >
well, the best way to explain the oddities here: you can never move at the speed of light, so you dont really have to understand what it would be like to do it. only the photon can, and presumably the photon isnt sentient, so no one/nothing ever experiences what it's light to move at the speed of light.
you can, however, move at 99.999999999% the speed of light. at that speed, you wouldnt notice anything weird about your time, but it would seem like the rest of the universe was passing by (in time) much faster than it should be. you could, for example, only be travelling at that speed for what felt like a few seconds, but when you're done most of the universe could have passed by many years.
yes, but you have to factor in what percent of the population lives in podunk Montana. i'd be willing to best most of the US lives in areas where broadband is available.
sure thing, court. you supply us with the hard disk space to store any and everything that gets put on my RAM, and i'll get right on that. i presume you'd like full copies of every moment... so lets see... the front side bus is 800MHz and we have 16gigs of RAM, so we'll be needing 400 bajillion GBs of space.