Produce some copyrightable material (or commission some, if your company is the sort that claims everything you make)
Host it on HTTPS.
Access it from work.
... now they've circumvented your over-the-wire copy protection scheme.
Seems like a long way to go to avoid checking your luggage.
How much stuff do you need to use during a time frame measured in hours? Ever considered how much easier and more comfortable it would be to not have to sit around in all that crap?
Or print the key (ideally not passphrase-protected, or with a memorable password given to your executor) in ASCII and attach it to your lawyer's copy of your will. Use an OCR-friendly font, maybe throw in a copy on a USB drive. Once you've backed-up the private key and made sure it's accessible without your intervention, you won't need it so delete it.
Save a list of up-to-date passwords (or perhaps your keychain and it's password; which could be more automated) encrypted with the public key somewhere easily accessible (web storage? Google Docs?)
Logging out doesn't remove the cookie that tells them who you are when you visit a page with the FB 'like' button or similar on it; it just makes it invalid for the purpose of actually being logged in.
Even then, this has no practical consequence whatsoever. If you want to compute the circumference of the galaxy, to accuracy such that your answer is off by less than a nanometer, you still need only ~100 digits of pi.
... and a measurement of its radius to within a nanometer;-)
No, that is stealing because it's real property with distinct and unambiguous ownership.
I'm saying that if your car had a keypad immobiliser, and your mechanic wrote the code on a chalkboard behind the counter where anyone who looked could see it; you can't be angry at the people who look for knowing it.
In a similar situation, often referenced on/. - it would be the mechanic (AT&T) in trouble with the customers for 'making available' the information.
A variable that is pushed to the stack make a register that can be used for something else. Yes, common architectures do often only have two or three registers available, once you take into account calling conventions that you aren't going to get around in any language as expressive as C or more so.
Re-using registers is A Good Thing - it's not like you can make more of them.
What makes you think a shift is more efficient than a divide? Are you taking into account the encoded instruction size, alignment, and variable decode latency? Instruction and jump caching?
If you want to write assembly for everything you do, go for it - I kind of like being able to say "strlen(var);". I like "var.size();" a bit more - but it's your call if you wanna say "push edi; sub ecx, ecx; mov edi, [esp+8]; not ecx; sub al, al; cld; repne scasb; not ecx; pop edi; lea eax, [ecx-1]; ret"; or some variant thereof. Go for it. I'll be over here, writing features.
Which is precisely how the notion of sovereignty has always been upheld.
I don't support many (if any) of the USA's actions or policies where they extend to citizens of other nations (like myself) - I just understand that nobody is likely to stop them. They are empowered by their own citizens, who see them as bringing the Light of Democracy And Capitalism to the terrorists and communists that the USIans must be protected from.
Anyhow, I've exceeded my quota of replying to ACs already. If you want to continue this, put your handle against your words.
Why would any one not expect the laws of the country they're in to apply to them?
You travel, you look for a summary of the local laws and customs before you go; or you take your chance at either offending people that would otherwise help you, or getting thrown in jail or beheaded.
You get caught smuggling banned substances into Australia? Jail. Most anywhere in South-East Asia? Death. If you're unwilling to Google, call a travel hotline, or ask your government, you deserve everything you get.
As for kanji, Japanese users expect written homonyms to be distinct (as do we)
There is no equivalent situation in English. You could spell a word with kana or kanji, the same word, same reading, same meaning and everything, but different characters - the distinction is merely whether you're spelling it out by sound or in kanji - or in some cases there could be different kanji as well (and, yes, still the same reading and meaning - the same word in every sense except the writing) - I think equivalence becomes a difficult problem when you consider the international cases.
If I'm writing a file called 'sensor data', I don't expect it to conflict with 'censor data' (homonym), 'detector data', or 'sensor recordings' (synonyms) - while the words are interchangeable when spoken, or equivalent in meaning, they are not the same words. The same is true of alternate writings for Japanese kanji, especially in names.
If it has a different writing, it is a different word; complete with its own (although possibly equivalent) entry in the dictionary.
Half-width katakana (JIS) are generally only used as phonetics on systems that don't support UTF- or another native language character encoding; and can be transparently re-coded to the full-width equivalent for storage or transmission in systems that do.
As for kanji, Japanese users expect written homonyms to be distinct (as do we) - although some application interfaces provide search by particle or phonetic (furigana by dictionary or metadata) I haven't seen it used a great deal (not that I necessarily would, even when I was living in Japan I still used English-language tech nearly exclusively). It's been attempted in more platform-wide situations, but I think it has the same sort of stigma as voice-recognition in English; the matches are just too fuzzy to be useful.
To clarify, NTFS (like HFS+) is case-preserving in filenames - filesystem drivers are given the leeway to match case-sensitively or not, so as to interact well with the expectations of the platform they are running on. Windows software expects case-insensitivity, so it gets it.
HFS+ at least has a filesystem flag that indicates names should be matched only by binary comparison (case-sensitive). When the case-sensitivity option started to appear in the version of Disk Utility on the install CD, not all bundled software had the right case in some hard-coded paths - so installing the OS on a case-sensitive (marked) file system would have a bunch of unusable core services.
I think this issue is now fixed, but the flag remains off by default as an ease-of-use feature for most OS X users.
Slashdot Mirror
Produce some copyrightable material (or commission some, if your company is the sort that claims everything you make)
Host it on HTTPS.
Access it from work.
... now they've circumvented your over-the-wire copy protection scheme.
Brilliant! We can use electric vehicles to reduce that pesky off-peak usage in the suburbs and increase peak load in urban areas!
Seems like a long way to go to avoid checking your luggage.
How much stuff do you need to use during a time frame measured in hours? Ever considered how much easier and more comfortable it would be to not have to sit around in all that crap?
10 PRINT "Problem #1... actually is hosted on DOS"
20 GOTO 10
Even if you are in high orbit you can only see at most half of the planet at a time.
When you look at a tennis ball, do you remind yourself that you're only seeing half of it?
Often, yes. Is that just me?
You are not alone.
If I had to pay bottled water rates to drink water, I'd drink a lot less.
Or print the key (ideally not passphrase-protected, or with a memorable password given to your executor) in ASCII and attach it to your lawyer's copy of your will. Use an OCR-friendly font, maybe throw in a copy on a USB drive. Once you've backed-up the private key and made sure it's accessible without your intervention, you won't need it so delete it. Save a list of up-to-date passwords (or perhaps your keychain and it's password; which could be more automated) encrypted with the public key somewhere easily accessible (web storage? Google Docs?)
+1 Correct
Logging out doesn't remove the cookie that tells them who you are when you visit a page with the FB 'like' button or similar on it; it just makes it invalid for the purpose of actually being logged in.
Even then, this has no practical consequence whatsoever. If you want to compute the circumference of the galaxy, to accuracy such that your answer is off by less than a nanometer, you still need only ~100 digits of pi.
... and a measurement of its radius to within a nanometer ;-)
I think the argument is that people in other countries would say "The first of September, nineteen-ninety."
Which follows the conversational principle of adding relevant context in successively larger granularity.
You don't have to get on the plane; you can just carry weapons/drugs/whatever to a stash on the other side for pickup by a regular passenger.
No, that is stealing because it's real property with distinct and unambiguous ownership.
I'm saying that if your car had a keypad immobiliser, and your mechanic wrote the code on a chalkboard behind the counter where anyone who looked could see it; you can't be angry at the people who look for knowing it.
In a similar situation, often referenced on /. - it would be the mechanic (AT&T) in trouble with the customers for 'making available' the information.
I'd consider data on the Internet with no authorisation mechanism to be 'published'. A private residence is still personal property, though.
A variable that is pushed to the stack make a register that can be used for something else. Yes, common architectures do often only have two or three registers available, once you take into account calling conventions that you aren't going to get around in any language as expressive as C or more so.
Re-using registers is A Good Thing - it's not like you can make more of them.
What makes you think a shift is more efficient than a divide? Are you taking into account the encoded instruction size, alignment, and variable decode latency? Instruction and jump caching?
If you want to write assembly for everything you do, go for it - I kind of like being able to say "strlen(var);". I like "var.size();" a bit more - but it's your call if you wanna say "push edi; sub ecx, ecx; mov edi, [esp+8]; not ecx; sub al, al; cld; repne scasb; not ecx; pop edi; lea eax, [ecx-1]; ret"; or some variant thereof. Go for it. I'll be over here, writing features.
The capital energy cost of manufacturing can always be produced by clean, abundant nuclear power.
I've taken that as a well-intentioned (although possibly misguided) attempt to get people to read the comments they are replying to.
Which is precisely how the notion of sovereignty has always been upheld.
I don't support many (if any) of the USA's actions or policies where they extend to citizens of other nations (like myself) - I just understand that nobody is likely to stop them. They are empowered by their own citizens, who see them as bringing the Light of Democracy And Capitalism to the terrorists and communists that the USIans must be protected from.
Anyhow, I've exceeded my quota of replying to ACs already. If you want to continue this, put your handle against your words.
My point being that as far as I'm aware, Thailand has no such notion.
"I can speak my mind on any topic - for I am Free, and speech is protected under the constitution of my land."
"You are in my land now. Guards, hang him. Any one else care to speak their mind?"
... and their laws say that breaches committed outside of the country can have you punished when you return.
Why would any one not expect the laws of the country they're in to apply to them?
You travel, you look for a summary of the local laws and customs before you go; or you take your chance at either offending people that would otherwise help you, or getting thrown in jail or beheaded.
You get caught smuggling banned substances into Australia? Jail. Most anywhere in South-East Asia? Death. If you're unwilling to Google, call a travel hotline, or ask your government, you deserve everything you get.
As for kanji, Japanese users expect written homonyms to be distinct (as do we)
There is no equivalent situation in English. You could spell a word with kana or kanji, the same word, same reading, same meaning and everything, but different characters - the distinction is merely whether you're spelling it out by sound or in kanji - or in some cases there could be different kanji as well (and, yes, still the same reading and meaning - the same word in every sense except the writing) - I think equivalence becomes a difficult problem when you consider the international cases.
If I'm writing a file called 'sensor data', I don't expect it to conflict with 'censor data' (homonym), 'detector data', or 'sensor recordings' (synonyms) - while the words are interchangeable when spoken, or equivalent in meaning, they are not the same words. The same is true of alternate writings for Japanese kanji, especially in names.
If it has a different writing, it is a different word; complete with its own (although possibly equivalent) entry in the dictionary.
Half-width katakana (JIS) are generally only used as phonetics on systems that don't support UTF- or another native language character encoding; and can be transparently re-coded to the full-width equivalent for storage or transmission in systems that do.
As for kanji, Japanese users expect written homonyms to be distinct (as do we) - although some application interfaces provide search by particle or phonetic (furigana by dictionary or metadata) I haven't seen it used a great deal (not that I necessarily would, even when I was living in Japan I still used English-language tech nearly exclusively). It's been attempted in more platform-wide situations, but I think it has the same sort of stigma as voice-recognition in English; the matches are just too fuzzy to be useful.
To clarify, NTFS (like HFS+) is case-preserving in filenames - filesystem drivers are given the leeway to match case-sensitively or not, so as to interact well with the expectations of the platform they are running on. Windows software expects case-insensitivity, so it gets it.
HFS+ at least has a filesystem flag that indicates names should be matched only by binary comparison (case-sensitive). When the case-sensitivity option started to appear in the version of Disk Utility on the install CD, not all bundled software had the right case in some hard-coded paths - so installing the OS on a case-sensitive (marked) file system would have a bunch of unusable core services.
I think this issue is now fixed, but the flag remains off by default as an ease-of-use feature for most OS X users.