spongy or absorbant isn't all that bad of an idea actually, if you set the machine to leave a random length pad after a buffer (you would have to set a max possible length) then you would have protection from worms that require overwriting executable code, it wouldn't be any more secure against remote-crash exploits, but they are not nearly as dangerous as remote-control
I don't recall reading the act but i do vaguely remember reading about it, yes, it is to ensure that US troops are protected from prosecution by foreign governments resulting from their following orders, and i am pretty sure it does encompass the possibility of a special-forces strike if needed
There are ways of trapping spider bots.... servers can be configured to keep returning additional subdirectories effectively "catching" the particular bot forever (or alternatively setting up a trap directory that, when accessed, autobans that IP address from seeing the infringing material, since the "directory structure" of a server is virtual anyways it would be trivial to add a/a/a/a/ and/z/z/z/ directory to a server, you touch one of those directories and suddenly all the other directories become empty (or filled with an alternative file set that is random garbage) In fact having filesharing apps do somethuing similar (activated by the browse host command) where an alternative set of files would be shown..... rather than let the riaa know you are blocking them make them thing you have nothing to hide/forever directories are great...
yea, and then you have all of europe switching to FOSS providing the crack in MS's armor needed to start slitting open the US market, trust me, MS would rather five free copies of XP Pro/ Longhorn to everyone in th EU than withdraw from/be forced out of the EU market
whoever wants to, either the "group" would be alpha, in which case the computer would use it's programmed DNS settings for that group (ie ICANN' would just mean use the regular DNS setting, openNIC' would trigger a lookup of DNS servers listed under "openNIC" in the system configuration page) the network itself would NOT resolve what the foo' signify, rather it would be up to the sysadmin, OEM, or user to configure the foo' settings, it would basically be the same as setting an openNIC DNS server as your secondary/tertiary DNS server but without the risk of the primary server snagging the request for a.info page and say... bring up sitefinder etc.
The point is not to make the URL bulletproof against ANY name disputes, but rather to aknowledge that TLD disputes can and do occur and allow website designers to be able to set more explicit instuctions to avoid having your links go different places depending on a visitor's ISP, it would also make specialized TLD's that have not made it into the mainstream resolve faster due to not having to wait for your primary and secondary DNS servers to time out on.foo before your specialized DNS server kicks in.....
I believe your proposal is equal to or better than mine in terms of logic, it succedes in causing the URL resolution to fail in unaware systems (needed to prevent hijacks) and allows for either a mapped name or direct DNS server IP address, the only possible issue i could see arising putting the server at the end of the URL would be as a hijck attempt on users who do not regularly use alternative DNS addresses not noticing, for example,
"http://www.paypal.com!192.168.1.1"
as opposed to
"http://192.168.1.1!www.paypal.com"
thus I believe it may help curb scamming a bit to put the optional explicit DNS server in front of the rest of the URL.
Yes, the default would be ICANN`, the point of putting it in the differently than another TLD is that any browser not aware of the DNS setting would reject the URL rather than attempting to resolve it (such as resolving to the wrong DNS system could lead to hijacking of addresses by a users default DNS, while adding an object in the URL that makes the URL invalid to systems which do not recognize it would prevent such actions, also using a keyword notation like that would leave open the option to put a DNS server IP address instead ("http://127.0.0.1`slashdot.org")
I would rather it not have to get that far, but if we want the web to survive as a useful medium we need a way to signify what DNS group a link is meant to reference in the event that DNS does become heavily fractured.
Actually, now I have to wait until all the compatibility issues are figured out, THEN I'll finally get a DVD burner.
What have the DVD(-|+)R(W) manufacturers done to deserve a boycott?
in a R&D based environment like military spending 10x funding would mean >10x strength as some of the money i used to buy more, but also money is used in making equipment/weapons better
you fucking commie bastard, according to the church of the almighty dollar anyone unable to afford life-saving medicine should not benefit from said medicine. Survival of the fittest, anything else is blasphemy.
actually there already is a HHGttG movie out, it is old , long, and exactly how not to make a movie (4-5 hours long IIRC and it is almos line-for-line out of the books)
the unreal line of games have always scaled nicely to match the system, original UT was playable on a gateway astro 400celery with intel graphics and looked awesome if you put it on a nice system, 2k3 looks great on a radeon 9700pro 128meg agp but plays just fine on a gf2mx400 64meg pci.
it is because XviD would fucking own the competition so badly there is no point in testing it... XviD usually looks just as good as DVD but at 700 megs... I don't know about at lower data-rates but XviD is THE BEST format for DVD to CDR conversion (well the TMD releases are nice cause you fit two on a CD but they look like shit and are always in two parts)
Slashdot Mirror
spongy or absorbant isn't all that bad of an idea actually, if you set the machine to leave a random length pad after a buffer (you would have to set a max possible length) then you would have protection from worms that require overwriting executable code, it wouldn't be any more secure against remote-crash exploits, but they are not nearly as dangerous as remote-control
I don't recall reading the act but i do vaguely remember reading about it, yes, it is to ensure that US troops are protected from prosecution by foreign governments resulting from their following orders, and i am pretty sure it does encompass the possibility of a special-forces strike if needed
a nicer implementation:
while(concious()) { drink("guinness"); }
There are ways of trapping spider bots.... servers can be configured to keep returning additional subdirectories effectively "catching" the particular bot forever (or alternatively setting up a trap directory that, when accessed, autobans that IP address from seeing the infringing material, since the "directory structure" of a server is virtual anyways it would be trivial to add a /a/a/a/ and /z/z/z/ directory to a server, you touch one of those directories and suddenly all the other directories become empty (or filled with an alternative file set that is random garbage) In fact having filesharing apps do somethuing similar (activated by the browse host command) where an alternative set of files would be shown..... rather than let the riaa know you are blocking them make them thing you have nothing to hide /forever directories are great...
It works better if you rip first nd burn as data.... 6-10x more music
yea, and then you have all of europe switching to FOSS providing the crack in MS's armor needed to start slitting open the US market, trust me, MS would rather five free copies of XP Pro/ Longhorn to everyone in th EU than withdraw from/be forced out of the EU market
So does this mean i can download porn from my lamp yet?
whoever wants to, either the "group" would be alpha, in which case the computer would use it's programmed DNS settings for that group (ie ICANN' would just mean use the regular DNS setting, openNIC' would trigger a lookup of DNS servers listed under "openNIC" in the system configuration page) the network itself would NOT resolve what the foo' signify, rather it would be up to the sysadmin, OEM, or user to configure the foo' settings, it would basically be the same as setting an openNIC DNS server as your secondary/tertiary DNS server but without the risk of the primary server snagging the request for a .info page and say... bring up sitefinder etc.
The point is not to make the URL bulletproof against ANY name disputes, but rather to aknowledge that TLD disputes can and do occur and allow website designers to be able to set more explicit instuctions to avoid having your links go different places depending on a visitor's ISP, it would also make specialized TLD's that have not made it into the mainstream resolve faster due to not having to wait for your primary and secondary DNS servers to time out on .foo before your specialized DNS server kicks in.....
I believe your proposal is equal to or better than mine in terms of logic, it succedes in causing the URL resolution to fail in unaware systems (needed to prevent hijacks) and allows for either a mapped name or direct DNS server IP address, the only possible issue i could see arising putting the server at the end of the URL would be as a hijck attempt on users who do not regularly use alternative DNS addresses not noticing, for example,
"http://www.paypal.com!192.168.1.1"
as opposed to
"http://192.168.1.1!www.paypal.com"
thus I believe it may help curb scamming a bit to put the optional explicit DNS server in front of the rest of the URL.
Yes, the default would be ICANN`, the point of putting it in the differently than another TLD is that any browser not aware of the DNS setting would reject the URL rather than attempting to resolve it (such as resolving to the wrong DNS system could lead to hijacking of addresses by a users default DNS, while adding an object in the URL that makes the URL invalid to systems which do not recognize it would prevent such actions, also using a keyword notation like that would leave open the option to put a DNS server IP address instead ("http://127.0.0.1`slashdot.org")
I would rather it not have to get that far, but if we want the web to survive as a useful medium we need a way to signify what DNS group a link is meant to reference in the event that DNS does become heavily fractured.
Perhapse adding the DNS group as an optional component to URLS such as
//foo` being defined either in the HOSTS file or some other new system file
"http://ICANN`slashdot.org"
"http://OpenNIC`computers.geek"
With "foo" in
Actually, now I have to wait until all the compatibility issues are figured out, THEN I'll finally get a DVD burner.
What have the DVD(-|+)R(W) manufacturers done to deserve a boycott?
"have been waiting to buy a burner until such time as i could make a single disc backup of a full length dvd.
The time is now, apparently.
" XviD?
That is why we are working on laser missile defense and shit like that, so when we invade europe they can't nuke us back
in a R&D based environment like military spending 10x funding would mean >10x strength as some of the money i used to buy more, but also money is used in making equipment/weapons better
If you have the money get a Rio Karma, supports OGG and FLAC in addition to the standard mp3/wma support.
this is an obvious troll, please do not feed.
heh grandparent poster probably doesn't play any RTS games, you gotta keep all your workers busy all the time unless you wanna get owned
you fucking commie bastard, according to the church of the almighty dollar anyone unable to afford life-saving medicine should not benefit from said medicine. Survival of the fittest, anything else is blasphemy.
/Sarcasm
screw that gimme ID(K)FA!
actually i doubt that the scope of the mozilla trademark covers coffee anyways, coffee is far enough removed from Mozilla's products.
actually there already is a HHGttG movie out, it is old , long, and exactly how not to make a movie (4-5 hours long IIRC and it is almos line-for-line out of the books)
the unreal line of games have always scaled nicely to match the system, original UT was playable on a gateway astro 400celery with intel graphics and looked awesome if you put it on a nice system, 2k3 looks great on a radeon 9700pro 128meg agp but plays just fine on a gf2mx400 64meg pci.
it is because XviD would fucking own the competition so badly there is no point in testing it... XviD usually looks just as good as DVD but at 700 megs... I don't know about at lower data-rates but XviD is THE BEST format for DVD to CDR conversion (well the TMD releases are nice cause you fit two on a CD but they look like shit and are always in two parts)