News for hackers. Stuff that matters.
Re:Extracting the SuperFish certificate by coldpie on Thursday February 19, 2015 @11:41AM (#9074967)
Thank you. IRDUTPOTOA (I really don't understand the point of these obscure acronyms).
Re:Extracting the SuperFish certificate by philh on Thursday February 19, 2015 @01:01PM (#9075629)
They're faster to type, and I suspect I find them more pleasant to read (this is hard to test). AIUI, IIRC and similar are good disclaimers to make, but they're basically boilerplate, and don't need to take up lots of space.

Similarly, compare "(c) 2015 philh" to "this post is copyrighted by philh, as of 2015".

Re:Extracting the SuperFish certificate by sib on Thursday February 19, 2015 @07:11PM (#9078102)
<trivia> Interestingly enough, (c) 2015 philh does not meet the requirement. You need either the word, copyright, or the actual copyright symbol. </trivia>
Re:Extracting the SuperFish certificate by heinrich5991 on Thursday February 19, 2015 @07:31PM (#9078190)
IIRC you don't need any of this, you will still hold copyright to what you have produced. This is just a friendly reminder to your readership.
Re:Extracting the SuperFish certificate by Natsu on Thursday February 19, 2015 @08:48PM (#9078451)
Correct. The Berne Convention did away with 'formalities' like having to register your copyrights in order to hold them. You still need to have a registered copyright to sue for statutory damages in the USA, though.
Re:Extracting the SuperFish certificate by colinbartlett on Thursday February 19, 2015 @08:02PM (#9078284)
IANAL but I believe you are correct although you get some extra legal protections by including the notice (which only need include the word or symbol and the name and year). Namely, an infringer cannot claim they did so accidentally... or something like that. FWIW.
Re:Extracting the SuperFish certificate by InclinedPlane on Thursday February 19, 2015 @10:13PM (#9078696)
No, you do not. Any work you do is automatically under copyright as long as that is a reasonable expectation (given a site's TOU, etc.)
Re:Extracting the SuperFish certificate by Afton on Thursday February 19, 2015 @11:50AM (#9075039)
That's because you find them obscure. If your community used them more frequently you would just read them in place, like people do with IANAL, LGTM, AFAIK, etc.

Incidentally, I didn't understand this one, but I don't blame OP (oops, I mean 'original poster') for misunderstanding the linguistic norms of HN (hacker news).

Re:Extracting the SuperFish certificate by TeMPOraL on Thursday February 19, 2015 @02:32PM (#9076371)
I agree. Nowdays I read things like "IANAL" or "AFAIK" as words, not acronyms. When one reaches this point, such acronyms are pretty convenient.
Re:Extracting the SuperFish certificate by lione on Thursday February 19, 2015 @12:08PM (#9075191)
Incidentally, first time I've seem LGTM, had to google it.
Re:Extracting the SuperFish certificate by vacri on Thursday February 19, 2015 @06:38PM (#9077942)
.lgbt as a gTLD? LGTM.
Re:Extracting the SuperFish certificate by sigzero on Thursday February 19, 2015 @12:03PM (#9075147)
Just spell it out!
Re:Extracting the SuperFish certificate by hamburglar on Thursday February 19, 2015 @04:15PM (#9077110)
They're a significant indicator that you're reading a message from someone who doesn't mind inconveniencing an unknown number of people to gain a negligible benefit for themselves. :) Or, at least, this is what I remind myself when I catch myself using them. Typing is not a hardship. I spend time trying to come up with the absolute clearest way of writing what I'm trying to say, so why would I then take a step backwards (potentially) in clarity just to save myself three seconds of typing?
Re:Extracting the SuperFish certificate by plaguuuuuu on Thursday February 19, 2015 @07:06PM (#9078075)
fgsfds!