That's actually kind of interresting. Technically you cannot patent the accurate data in a map. You can however copyright its presentation, and if the presentation is all that is given, that requires reverse-engineering maps into data (which can be very difficult depending on the format). You also run into copyright issues on inaccurate data. If a road exists where a map says it does, they cannot copyright that fact, as it is a fact. The problem is that EVERY commercial map company intetionally includes mistakes in their maps (mostly to identitfy who is copying them). The really fun part is that since those phantom roads DON'T actually exist, they are NOT facts, and thus subject to copyright since the company actually "creatively created" them. If you can tell which roads are wrong, you'll be fine copying everything else, but cthulhu help you in court if you copy a phantom/milabeled/typo'd road!
It's kind of pointless though if they aren't mandating ISP's to at least provide dual-stack support for both protocols. What's the point of government websites being IPv6 if the country is still stuck on IPv4?
Good point, lets wait for the ISP's to run out of IPv4 addresses and suddenly start mandating that people's homes be IPv6 ready out of the blue. We basically have 3 choices.
1) Wait until residents do need it and suddenly give them IPv6 only because there are no IPv4 addresses left. Phone support will have hour-long waiting periods, computer shops will be overloaded with "I need this upgrade tonight so I can submit my college thesus" support requests and a large percentage of Internet users will be SOL until they get their turn in the support line. There's also a VERY good chance we will simply run out of routers, as an alarminly large percentage of consumer (and some professional) routers STILL don't support it and all those people will need upgrades.
2) Wait until we need it and start NAT'ing everyone's internet connection. This may not affect facebook users, but will be a royal PITA for anyone using remote connections, peer2peer networking, etc. If this happens we may not see IPv6 for another 15 years at LEAST.
3) Roll it out NOW in dual-stack configuration world-wide so everyone can get their computers, routers and other devices working with IPv6. ISP's can send out regular (every 2-4 months) letters to consumers still using IPv4 only to warn them about the upcoming switch and give them enough warning to switch over (like they did with digital tv broadcasting). When we finally do run out of IPv4 addresses at the ISP level (and this is ALREADY happening in some areas such as mobile, etc), the ISP's can just disable IPv4 for new customers and/or those already fully using IPv4 and experience a truly smooth transition.
If the analog-2-digial transition for TV broadcasting has taught us anything, it's that consumers need a LONG time to transition between technologies. Considering the TV transition required nothing more than plugging in 1 box with 3 wires on it and IPv6 is going to require computer/OS and router replacement in many cases, we need to start the IPv6 transition on all ISP's about 2 years ago.
Others have already explained why you can, so I'll explain why you shouldn't
Unless you have 2 wireless connections, everything you do is ALSO transmitted unsecured over the air exposing you to packet sniffing. Even your internet connections (from one computer to the other over samba/shared folders/etc). BAD
Coffee shops typically have surveillance cameras in and round their building, so if someone uses the connection to steal CC numbers or upload child porn, the police have at least some leads as to its source.
Coffee shops institute throttling, if someone starts torrenting or downloading huge files, they etther get throttled or booted, if a neighbour did it to you, you'd probably have a hard time kicking them off without having to quicly set up passwords on all your machines (MAC only stops Joe).
If someone abuses a McDonald's connection, the police start looking at customers and employees. If someone abuses your internet connection, they start investigating YOU and that is not something you want to have to go through. You may win in court, but your name and reputation will be ruined and you'll probably lose a lot in court costs and personal costs (family, friends, job, etc).
So go ahead, keep that connection open, just don't post a "The police are harrassing me" bitch-fest ask-slashdot story when it bites you in the ass as you will get NO simpathy from me or the majority of the readers here.
On the key is known, then anyone can use it and it might as well be open. Even the individual key is not going to stop snooping.
You obviously don't understand anything about wireless security. If a connection is open (no encryption), anyone (even those not connected to the router) can stniff EVERYTHING sent over the connection (barring https and the like). With a password, even if every person in the world knows the password, nobody can sniff anyone else's packets. The passwords intiates a transaction where the router and your computer set up their own sessions keys which are used to encrypt everything else. so even though everyone used the same password, everyone is using different encryption keys, so everyone is protected (at the wireless level at least).
Oh of course, but if they've gotten to the hashes, chances are they've gotten to everything else already anyways. As long as you aren't using that same passphrase on other systems you should be fine.
A week? If it takes you a whole week to save the time required to "git init --bare; cp -r orig_code_location/*./; git add.; git commit -a -m 'initial commit'" you are doing something wrong.
They obviously have SOME kind of central server already that holds the code, just use that. Git doesn't need any special ports or protocols, it can work just fine at the filesystem level. Just create a bare git repo folder in a shared directory and push/pull to that, the server doesn't even need git installed, just the clients accessing it.
Even if they had no idea which number you had, it still allows vote buying and vote bullying. The idea of anonymous voting is that even YOU can prove who you voted for, so there is no way to prove to a vote buyer/bullyer that you complied.
And bar-codes are going to prevent that HOW? If they were able to register as a dead person, they could sure as hell get a bar-code as a dead person. And if you think it will allow them to discard the vote when they find out later, what makes you think they'll find out later if they missed it when they registered the dead person in the first fucking place?!?
...or stolen. The more parties have possession of sensitive data, the higher the chance it will be "lost" or stolen by those that WOULD use it against you.
That's a valid reason to not USE a password with certain characters, not a valid reason to not SUPPORT them. If a users chooses to put a character in their password they won't be able to type again (like using a computer they won't have further access to, etc), that's their OWN damned fault.
I have a 2000 word dictionary of words around 4-8 characters. Randomly generated you could easily fit 3 words which is 2000^3 == 32 bits of entropy. Not great, but still difficult to brute-force on a system that undoubtedly tracks (and responds to) failed login attempts.
Slashdot Mirror
No, according to the friendly copyright police, that would be illegal and they must purchase their own licenses.
If the person that agreed* to the EULA is no longer living, how can they possibly be in violation of said EULA?
* Nobody reads them anyways
That's actually kind of interresting. Technically you cannot patent the accurate data in a map. You can however copyright its presentation, and if the presentation is all that is given, that requires reverse-engineering maps into data (which can be very difficult depending on the format). You also run into copyright issues on inaccurate data. If a road exists where a map says it does, they cannot copyright that fact, as it is a fact. The problem is that EVERY commercial map company intetionally includes mistakes in their maps (mostly to identitfy who is copying them). The really fun part is that since those phantom roads DON'T actually exist, they are NOT facts, and thus subject to copyright since the company actually "creatively created" them. If you can tell which roads are wrong, you'll be fine copying everything else, but cthulhu help you in court if you copy a phantom/milabeled/typo'd road!
It's kind of pointless though if they aren't mandating ISP's to at least provide dual-stack support for both protocols. What's the point of government websites being IPv6 if the country is still stuck on IPv4?
Good point, lets wait for the ISP's to run out of IPv4 addresses and suddenly start mandating that people's homes be IPv6 ready out of the blue. We basically have 3 choices.
1) Wait until residents do need it and suddenly give them IPv6 only because there are no IPv4 addresses left. Phone support will have hour-long waiting periods, computer shops will be overloaded with "I need this upgrade tonight so I can submit my college thesus" support requests and a large percentage of Internet users will be SOL until they get their turn in the support line. There's also a VERY good chance we will simply run out of routers, as an alarminly large percentage of consumer (and some professional) routers STILL don't support it and all those people will need upgrades.
2) Wait until we need it and start NAT'ing everyone's internet connection. This may not affect facebook users, but will be a royal PITA for anyone using remote connections, peer2peer networking, etc. If this happens we may not see IPv6 for another 15 years at LEAST.
3) Roll it out NOW in dual-stack configuration world-wide so everyone can get their computers, routers and other devices working with IPv6. ISP's can send out regular (every 2-4 months) letters to consumers still using IPv4 only to warn them about the upcoming switch and give them enough warning to switch over (like they did with digital tv broadcasting). When we finally do run out of IPv4 addresses at the ISP level (and this is ALREADY happening in some areas such as mobile, etc), the ISP's can just disable IPv4 for new customers and/or those already fully using IPv4 and experience a truly smooth transition.
If the analog-2-digial transition for TV broadcasting has taught us anything, it's that consumers need a LONG time to transition between technologies. Considering the TV transition required nothing more than plugging in 1 box with 3 wires on it and IPv6 is going to require computer/OS and router replacement in many cases, we need to start the IPv6 transition on all ISP's about 2 years ago.
Others have already explained why you can, so I'll explain why you shouldn't
So go ahead, keep that connection open, just don't post a "The police are harrassing me" bitch-fest ask-slashdot story when it bites you in the ass as you will get NO simpathy from me or the majority of the readers here.
On the key is known, then anyone can use it and it might as well be open. Even the individual key is not going to stop snooping.
You obviously don't understand anything about wireless security. If a connection is open (no encryption), anyone (even those not connected to the router) can stniff EVERYTHING sent over the connection (barring https and the like). With a password, even if every person in the world knows the password, nobody can sniff anyone else's packets. The passwords intiates a transaction where the router and your computer set up their own sessions keys which are used to encrypt everything else. so even though everyone used the same password, everyone is using different encryption keys, so everyone is protected (at the wireless level at least).
Funny, I just click the "install mp3 codecs" checkbox at install time. If you didn't do that, just search "mp3" in software center.
The USPTO called, they want their patent returned.
Fines are issued by government for breaking laws and regulations. Penalties are issued by contractual partners for breaking contractual agreements.
So would I if there wasn't a monthly limit of 3 thoughts and a $400/thought overage fee.
Oh of course, but if they've gotten to the hashes, chances are they've gotten to everything else already anyways. As long as you aren't using that same passphrase on other systems you should be fine.
I think it's safe to assume the existing code is already stored on just such a server. git init --bare and copy the code in with a commit, DONE.
A week? If it takes you a whole week to save the time required to "git init --bare; cp -r orig_code_location/* ./; git add .; git commit -a -m 'initial commit'" you are doing something wrong.
They obviously have SOME kind of central server already that holds the code, just use that. Git doesn't need any special ports or protocols, it can work just fine at the filesystem level. Just create a bare git repo folder in a shared directory and push/pull to that, the server doesn't even need git installed, just the clients accessing it.
When a candle hits a hydrogen balloon it pops the balloon, quickly combining the hydrogen from inside the balloon with the oxygen outside the balloon.
Not if the uploader (the one who counter-claimed) is outside the US (which they are). He won't be suing youtube, he'll be suing the church.
Even if they had no idea which number you had, it still allows vote buying and vote bullying. The idea of anonymous voting is that even YOU can prove who you voted for, so there is no way to prove to a vote buyer/bullyer that you complied.
And bar-codes are going to prevent that HOW? If they were able to register as a dead person, they could sure as hell get a bar-code as a dead person. And if you think it will allow them to discard the vote when they find out later, what makes you think they'll find out later if they missed it when they registered the dead person in the first fucking place?!?
Which is fine for the above information, but in many places we have no choice but to use smart meters.
...or stolen. The more parties have possession of sensitive data, the higher the chance it will be "lost" or stolen by those that WOULD use it against you.
And hopefully you'll have changed your password by then.
That's a valid reason to not USE a password with certain characters, not a valid reason to not SUPPORT them. If a users chooses to put a character in their password they won't be able to type again (like using a computer they won't have further access to, etc), that's their OWN damned fault.
Or switch you to a $300/month internet+tv+phone+telepath plan and stick you with the bill.
I have a 2000 word dictionary of words around 4-8 characters. Randomly generated you could easily fit 3 words which is 2000^3 == 32 bits of entropy. Not great, but still difficult to brute-force on a system that undoubtedly tracks (and responds to) failed login attempts.