Hi Folks, It's your regular neighborhood troll magic maverick , and I've got a small couple of requests for you. 1. In the firehose, vote down as offtopic anything that isn't related to the beta. Vote up anything that is related to the beta. 2. Join the boycott from 10th to 17th Feb. Demonstrate that without the commentators,/. will obviously die.
Cheers, Now back to your regular scheduled trolling.
The reason so many people are "spamming" the comments section is to highlight how much comments actually matter to this website. At the moment people are coming and posting, but posting anti-beta stuff. Next week, well, with many fewer comments, the management ("no smoking or spitting") can compare and contrast the numbers. Perhaps they'll realize that it is actually the commentators that make the site, and not the "editors" (who can't edit for shit).
Dear Bruce, Of all the/. commentators that I've seen discussing alternatives to/., you are probably the most trustworthy (not to say that the others aren't, but they don't have the profile that you have). Please make a/. alternative that takes all the best bits of/. (threaded comments, moderation and meta moderation, user accounts, but also anonymous posting, etc. etc.), throw out the crap (the troll posts that are basically the repeat of each other, perhaps something that can just compare a comment against another comment and say "this comment is too similar", try again), and add some goodies (e.g. Unicode), and done. I'll come and join your site. I'll even donate to make it happen.
Yours sincerely,/. user since at least 2004 (third or fourth user account): magic maverick
If the comment system doesn't even load comments even with nothing blocked, then it is crap and should be replaced. Despite all the bad things one might say about D2, at least I can load the fucking comments. Which I can't do with your new shit. Just a FYI. (And as others keep saying, without comments, there is literally no point in coming back.)
That's what I think about the new Slashdot Beta. It's awful. "There's simply nothing I like about [Slashdot Beta]. [It] need[s] to disappear, not get passed on to the next unfortunate recipient." In all the important ways it is unusable. It won't even load comments for me! It just says something silly like nah ah. WTF? So much for professionalism.
Oh, and I have JavaScript enabled for slashdot.org and fsdn.com so that shouldn't be a problem. (Unless they want me to whitelist some random other domains. Well, fuck that. I'd rather just leave.)
And without comments,/. is nothing. The comments are the only reason to bother coming here.
Go to Kobo <http://kobobooks.com>. Search for the title you want to buy. See that it says "Adobe DRM EPUB" or "EPUB (DRM-Free)". Don't pick any title with DRM. Pick the other titles. (For an example of an author with both DRMed and non-DRMed files, see Charles Stross.)
And don't feel bad. It too me a while as well.
Also, I remember reading that Tor USA titles everywhere should be DRM-free. If you get one that isn't, you can email them and they'll send you a copy that is DRM-free (perhaps).
Adobe Digital Editions and Adobe DRM is used by virtually all publishers (that actually use DRM) and device makers except Amazon. I.e. it is everywhere (sort of like how ePub is used by virtually everyone except Amazon). But, you don't have to use it. No device that I know of requires that an ePub file has DRM.
Two publishers in the SF/F field that don't use any DRM at all are Tor and Baen Books. Baen Books is excellent for other reasons, including their Free Library (you can download and read the first book in most of their series'). Tor is just part of one of the Big Six, and so otherwise has nothing to distinguish them from any other publisher.
I don't buy DRMed shit. I do buy titles from Baen Books and Tor, but they aren't infested with digital restrictions management. If I want a title, and I can't find it from a publisher that doesn't use DRM, I just pop over to my favorite torrent website. And normally I'll find what I'm looking for. (If I don't, I'll find it at my second favorite torrent site, easy.)
I.e. DRM doesn't work. Moreover, it has the opposite effect, rather than preventing copying, it encourages more copying!
(I might buy DRM infested titles, if Adobe made their software work on */Linux. But probably not. But considering I don't run anything else, there is no point in my forking over money for something I can't read or use.)
Oh, and ignoring all the above: why should I have to update the firmware or software on my ebook reader? It's an appliance. I don't expect to update the firmware on my TV, microwave or rice cooker. Why should I? It works now.
Progressive enhancement means making sure that the basic stuff (content) works before adding the presentation and other layers (CSS and JavaScript). So, who cares if your fancy CSS doesn't work in MSIE 6? So long as your basic HTML is alright, then it'll be alright. OK, so MSIE 6 doesn't understand certain HTML 5 elements. In which case, you can use some JS to make it understand (a shiv or a shim).
Graceful degradation has almost the same result. First you make the page, and you make it all fancy. Then you make sure it gracefully degrades (and can still be seen in) older browsers.
Basically, in both cases, you don't care if people using older browsers get your fancy shit. Just so long as they get your writing. And you can still use (the as yet unfinished) HTML 5, and the fancy CSS etc.
Yes. Don't trust one website's stats. Always look at your own stats before deciding you can afford to not support a particular browser. Of course, you should always use progressive enhancement, so that even if people do insist on using ancient browsers, they should still be able to get the basic content. (It's a pity more people don't take the view, but considering the web was intended to be a universal, regardless of machine or software, medium, it's the view that is more inline with the intention of the web.)
There is no updated version of CSS. CSS 3 is not actually a thing. Instead, there are what are called modules. CSS 2 is a good starting point, because the basics are all in one place. And it's still all valid.
HTML 5 isn't finalized. Moreover, learning HTML 4.01 (strict) and XHTML 1.1 will (as I pointed out in my post...) teach good habits. (And make a person appreciate the really good parts of HTML 5, like the new form parts.) Oh, and they are still valid...
Unlike with something like PHP 3 and 4, there is no security risk in using the older versions of HTML and CSS. Moreover, unlike older versions of PHP, knowing the older versions of HTML and CSS can directly translate to knowing the newer versions. (A valid HTML 4.01 strict document is also, with a different doctype, basically a valid HTML 5 document.) PHP has deprecated loads of stuff, and has thrown out a lot of the bad ways of doing things in the later versions. Later versions of PHP are much more coherent than older versions. But CSS 2 is still excellent, if that's all you need.
Oh, and I should have mentioned (and others have already), you also should learn at least the basics of the various protocols. You should be able to recognize the various parts of a HTTP message, and know what most of the verbs (e.g. PUT, POST, GET) and codes (e.g. 200, 404, 408) mean. You should know how HTTPS works (and for bonus points, know at least two major flaws with it). And you should know what TCP/IP means (and if you're really good, how they work), what DNS and DHCP are, and so on.
If you are already a programmer, or even if you're not, then there are three technologies that you should attempt to learn (or at least recognize and be able to say "yeah, OK, this makes a sorta sense"). These are HTML, CSS and JavaScript. HTML is the basis for web pages. It is what they are built upon. I suggest starting with HTML 4.01 (strict) and XHTML 1.1 (there are major differences that may not look like being major), and then moving onto HTML 5 (yet to be fully finalized). The older HTML should teach you some good habits, as should the XHTML (and while you're looking at XHTML, learn what XML is, and why XHTML exists). Then you need some style to make your pages look pretty. That means CSS. CSS is broad, and you can just learn the basics and pick up the more complicated stuff as you go along. (That basically means start with CSS 2, and learn "CSS 3" modules as and when you need them.) CSS is capable of doing a lot of stuff that previously required JavaScript.
JavaScript is not an essential. But you should know the basics. And most importantly, you should know two things, when not to use JavaScript, and what progressive enhancement is. (Progressive enhancement might also be called graceful degradation. It's basically the same thing, in the way that Open Source Source and Free Software are basically the same thing. There are philosophical differences, but they still do mostly the same thing.) --- And that's the web. Finished. You can go home now.
Oh, still with me? Yes, there is still more to learn. Learn PHP. "But I heard it's awful" you cry. And it may well be. But it's also probably the most popular backend web language. It's what major and widespread software is written in. WordPress, MediaWiki, Drupal, and others are all written in PHP. But, like with JavaScript, unless you want a job, you don't need to learn more than the basics. There are great docs that can help you with almost anything.
Similarly, learn SQL if you don't already. If you're learning PHP from scratch, use the PDO functions, then you can easily switch databases (and not be stuck on MySQL). Also, learn how to wrangle an Apache.htaccess file, and especially redirects.
Next, I hear Ruby is getting a lot of press. Maybe learn some of that, and Ruby on Rails. ---
Finally, and this is more important than Ruby on Rails, make sure you don't get hung up on pages looking the same in every browser. But do learn the fuck out of how to test in different browsers, and on different devices. And test the fuck out of your pages in different browsers. If you're page isn't readable in Lynx, maybe you need to do some reconsidering.
That would be an interesting point. However, there is no method currently in BitCoin to prevent seized bitcoins from being "spent" (transfered to another address). Nor, as far as I know, is there any wallet that would highlight that a particular bitcoin is "bad". So, if the gov. does it sensibly, they could easily sell off these bitcoins for cash. Hell, they could even just hold an auction rather than going through an exchange. They probably will do that. And they'll find someone willing to pay at least $10 a bitcoin (which is like 1% of the current value) because once they bitcoins have changed hands, they are easy to launder (or "mix") if not to just spend.
If God had wanted us to see far away things he would have given us telescopic eyes. This sinner is now burning in hell for allowing anyone to see the far away places that God had made off-limits.</troll>
It works with hot fusion. Unfortunately, when you fly too close to the power source all the wax melts and your wings fall apart. This happened in beta-testing, and the tester died:(.
Quite. This is merely a concept, not an actual working product.
It's certainly interesting, and I was all excited for a little bit, but there is no product here. There is no revolutionary scuba mask. (And if it is, I can mock up some pictures of a "revolutionary 'bird-wings'" that allows people to merely flap their arms and fly! Oh, on Earth.)
You're a cunt for linking to a URL shortener instead of the article directly. You're as bad as the shithead editors. If you're worried about goatse or similar, don't use some shit URL shortener.
The sun never sets on the British Empire! It also never sets on the French Empire. I'm sure you could argue that it doesn't set on the Americunt Empire for that matter.
Personally, I make sure the sun never sets on me, and therefore there never is a sun rise, by fleeing west ahead of it. My birthday shall never end!
Funny, I thought much the same about Bzr. Bzr has at least one GUI (bzr-gtk), is better supported on more than just Linux-based systems, is also written in Python, etc.
Unfortunately, Bzr development has apparently stalled (hence the email from esr suggesting moving off bzr to git -- he notes that he would prefer hg, but that Git has basically won). But, bzr does everything I ask of it. I'll be continuing to use it, so long as it continues to work. When it stops, I guess I'll have to find a tool to convert all my shit to Git or whatever, and find replacements for the various tools that I use (e.g. integration into Gedit).
Slashdot Mirror
LOL someone is butthurtz about my post and modded it off topic. I guess I'm going to need a bigger shotgun.
I only want to be the best that I can.
My mouth is stained.
Ah fuck it, you know what? Fuck you and your mother, I'm not getting paid enough to post this shit.
Hi Folks, /. will obviously die.
It's your regular neighborhood troll magic maverick , and I've got a small couple of requests for you.
1. In the firehose, vote down as offtopic anything that isn't related to the beta. Vote up anything that is related to the beta.
2. Join the boycott from 10th to 17th Feb. Demonstrate that without the commentators,
Cheers,
Now back to your regular scheduled trolling.
The reason so many people are "spamming" the comments section is to highlight how much comments actually matter to this website. At the moment people are coming and posting, but posting anti-beta stuff. Next week, well, with many fewer comments, the management ("no smoking or spitting") can compare and contrast the numbers. Perhaps they'll realize that it is actually the commentators that make the site, and not the "editors" (who can't edit for shit).
Dear Bruce, /. commentators that I've seen discussing alternatives to /., you are probably the most trustworthy (not to say that the others aren't, but they don't have the profile that you have). Please make a /. alternative that takes all the best bits of /. (threaded comments, moderation and meta moderation, user accounts, but also anonymous posting, etc. etc.), throw out the crap (the troll posts that are basically the repeat of each other, perhaps something that can just compare a comment against another comment and say "this comment is too similar", try again), and add some goodies (e.g. Unicode), and done. I'll come and join your site. I'll even donate to make it happen.
Of all the
Yours sincerely, /. user since at least 2004 (third or fourth user account): magic maverick
If the comment system doesn't even load comments even with nothing blocked, then it is crap and should be replaced. Despite all the bad things one might say about D2, at least I can load the fucking comments. Which I can't do with your new shit. Just a FYI. (And as others keep saying, without comments, there is literally no point in coming back.)
That's what I think about the new Slashdot Beta. It's awful. "There's simply nothing I like about [Slashdot Beta]. [It] need[s] to disappear, not get passed on to the next unfortunate recipient." In all the important ways it is unusable. It won't even load comments for me! It just says something silly like nah ah. WTF? So much for professionalism.
Oh, and I have JavaScript enabled for slashdot.org and fsdn.com so that shouldn't be a problem. (Unless they want me to whitelist some random other domains. Well, fuck that. I'd rather just leave.)
And without comments, /. is nothing. The comments are the only reason to bother coming here.
Go to Kobo <http://kobobooks.com>. Search for the title you want to buy. See that it says "Adobe DRM EPUB" or "EPUB (DRM-Free)". Don't pick any title with DRM. Pick the other titles. (For an example of an author with both DRMed and non-DRMed files, see Charles Stross.)
And don't feel bad. It too me a while as well.
Also, I remember reading that Tor USA titles everywhere should be DRM-free. If you get one that isn't, you can email them and they'll send you a copy that is DRM-free (perhaps).
Adobe Digital Editions and Adobe DRM is used by virtually all publishers (that actually use DRM) and device makers except Amazon. I.e. it is everywhere (sort of like how ePub is used by virtually everyone except Amazon). But, you don't have to use it. No device that I know of requires that an ePub file has DRM.
Two publishers in the SF/F field that don't use any DRM at all are Tor and Baen Books. Baen Books is excellent for other reasons, including their Free Library (you can download and read the first book in most of their series'). Tor is just part of one of the Big Six, and so otherwise has nothing to distinguish them from any other publisher.
I don't buy DRMed shit. I do buy titles from Baen Books and Tor, but they aren't infested with digital restrictions management. If I want a title, and I can't find it from a publisher that doesn't use DRM, I just pop over to my favorite torrent website. And normally I'll find what I'm looking for. (If I don't, I'll find it at my second favorite torrent site, easy.)
I.e. DRM doesn't work. Moreover, it has the opposite effect, rather than preventing copying, it encourages more copying!
(I might buy DRM infested titles, if Adobe made their software work on */Linux. But probably not. But considering I don't run anything else, there is no point in my forking over money for something I can't read or use.)
Oh, and ignoring all the above: why should I have to update the firmware or software on my ebook reader? It's an appliance. I don't expect to update the firmware on my TV, microwave or rice cooker. Why should I? It works now.
Progressive enhancement means making sure that the basic stuff (content) works before adding the presentation and other layers (CSS and JavaScript). So, who cares if your fancy CSS doesn't work in MSIE 6? So long as your basic HTML is alright, then it'll be alright. OK, so MSIE 6 doesn't understand certain HTML 5 elements. In which case, you can use some JS to make it understand (a shiv or a shim).
Graceful degradation has almost the same result. First you make the page, and you make it all fancy. Then you make sure it gracefully degrades (and can still be seen in) older browsers.
Basically, in both cases, you don't care if people using older browsers get your fancy shit. Just so long as they get your writing. And you can still use (the as yet unfinished) HTML 5, and the fancy CSS etc.
Yes. Don't trust one website's stats. Always look at your own stats before deciding you can afford to not support a particular browser. Of course, you should always use progressive enhancement, so that even if people do insist on using ancient browsers, they should still be able to get the basic content. (It's a pity more people don't take the view, but considering the web was intended to be a universal, regardless of machine or software, medium, it's the view that is more inline with the intention of the web.)
There is no updated version of CSS. CSS 3 is not actually a thing. Instead, there are what are called modules. CSS 2 is a good starting point, because the basics are all in one place. And it's still all valid.
HTML 5 isn't finalized. Moreover, learning HTML 4.01 (strict) and XHTML 1.1 will (as I pointed out in my post...) teach good habits. (And make a person appreciate the really good parts of HTML 5, like the new form parts.) Oh, and they are still valid...
Unlike with something like PHP 3 and 4, there is no security risk in using the older versions of HTML and CSS. Moreover, unlike older versions of PHP, knowing the older versions of HTML and CSS can directly translate to knowing the newer versions. (A valid HTML 4.01 strict document is also, with a different doctype, basically a valid HTML 5 document.) PHP has deprecated loads of stuff, and has thrown out a lot of the bad ways of doing things in the later versions. Later versions of PHP are much more coherent than older versions. But CSS 2 is still excellent, if that's all you need.
Oh, and I should have mentioned (and others have already), you also should learn at least the basics of the various protocols. You should be able to recognize the various parts of a HTTP message, and know what most of the verbs (e.g. PUT, POST, GET) and codes (e.g. 200, 404, 408) mean. You should know how HTTPS works (and for bonus points, know at least two major flaws with it). And you should know what TCP/IP means (and if you're really good, how they work), what DNS and DHCP are, and so on.
Good luck.
If you are already a programmer, or even if you're not, then there are three technologies that you should attempt to learn (or at least recognize and be able to say "yeah, OK, this makes a sorta sense"). These are HTML, CSS and JavaScript. HTML is the basis for web pages. It is what they are built upon. I suggest starting with HTML 4.01 (strict) and XHTML 1.1 (there are major differences that may not look like being major), and then moving onto HTML 5 (yet to be fully finalized). The older HTML should teach you some good habits, as should the XHTML (and while you're looking at XHTML, learn what XML is, and why XHTML exists). Then you need some style to make your pages look pretty. That means CSS. CSS is broad, and you can just learn the basics and pick up the more complicated stuff as you go along. (That basically means start with CSS 2, and learn "CSS 3" modules as and when you need them.) CSS is capable of doing a lot of stuff that previously required JavaScript.
JavaScript is not an essential. But you should know the basics. And most importantly, you should know two things, when not to use JavaScript, and what progressive enhancement is. (Progressive enhancement might also be called graceful degradation. It's basically the same thing, in the way that Open Source Source and Free Software are basically the same thing. There are philosophical differences, but they still do mostly the same thing.)
---
And that's the web. Finished. You can go home now.
Oh, still with me? Yes, there is still more to learn. Learn PHP. "But I heard it's awful" you cry. And it may well be. But it's also probably the most popular backend web language. It's what major and widespread software is written in. WordPress, MediaWiki, Drupal, and others are all written in PHP. But, like with JavaScript, unless you want a job, you don't need to learn more than the basics. There are great docs that can help you with almost anything.
Similarly, learn SQL if you don't already. If you're learning PHP from scratch, use the PDO functions, then you can easily switch databases (and not be stuck on MySQL). .htaccess file, and especially redirects.
Also, learn how to wrangle an Apache
Next, I hear Ruby is getting a lot of press. Maybe learn some of that, and Ruby on Rails.
---
Finally, and this is more important than Ruby on Rails, make sure you don't get hung up on pages looking the same in every browser. But do learn the fuck out of how to test in different browsers, and on different devices. And test the fuck out of your pages in different browsers. If you're page isn't readable in Lynx, maybe you need to do some reconsidering.
That would be an interesting point. However, there is no method currently in BitCoin to prevent seized bitcoins from being "spent" (transfered to another address). Nor, as far as I know, is there any wallet that would highlight that a particular bitcoin is "bad". So, if the gov. does it sensibly, they could easily sell off these bitcoins for cash. Hell, they could even just hold an auction rather than going through an exchange. They probably will do that. And they'll find someone willing to pay at least $10 a bitcoin (which is like 1% of the current value) because once they bitcoins have changed hands, they are easy to launder (or "mix") if not to just spend.
If God had wanted us to see far away things he would have given us telescopic eyes. This sinner is now burning in hell for allowing anyone to see the far away places that God had made off-limits.</troll>
It works with hot fusion. Unfortunately, when you fly too close to the power source all the wax melts and your wings fall apart. This happened in beta-testing, and the tester died :(.
Quite. This is merely a concept, not an actual working product.
It's certainly interesting, and I was all excited for a little bit, but there is no product here. There is no revolutionary scuba mask. (And if it is, I can mock up some pictures of a "revolutionary 'bird-wings'" that allows people to merely flap their arms and fly! Oh, on Earth.)
You're a cunt for linking to a URL shortener instead of the article directly. You're as bad as the shithead editors. If you're worried about goatse or similar, don't use some shit URL shortener.
http://aclweb.org/anthology/D/D13/D13-1181.pdf
There. Easy. Why couldn't you have done that you high-horsed cunt?
The sun never sets on the British Empire! It also never sets on the French Empire. I'm sure you could argue that it doesn't set on the Americunt Empire for that matter.
Personally, I make sure the sun never sets on me, and therefore there never is a sun rise, by fleeing west ahead of it. My birthday shall never end!
I hope all you Americunts do die of cold. Save the rest of us some heart-ache and suffering.
Bring the frozen USA!
And you're a cunt. But that's just my opinion, and if you thought about your opinion a little bit more, maybe I wouldn't have called you that.
Funny, I thought much the same about Bzr. Bzr has at least one GUI (bzr-gtk), is better supported on more than just Linux-based systems, is also written in Python, etc.
Unfortunately, Bzr development has apparently stalled (hence the email from esr suggesting moving off bzr to git -- he notes that he would prefer hg, but that Git has basically won). But, bzr does everything I ask of it. I'll be continuing to use it, so long as it continues to work. When it stops, I guess I'll have to find a tool to convert all my shit to Git or whatever, and find replacements for the various tools that I use (e.g. integration into Gedit).
Hi.
My name is Johan Smith, and I live at 1600 Pennsylvania Avenue NW, Washington DC.
I just logged in to say, you're all a bunch of cunts. Soulskill is a cunt. The mods are all cunts. And this article was written by a cunt.
Anyone who thinks that non-anonymous commentating will drive away the trolls, and the hacks, and the flamebaiters, is insane, and/or a cunt.
Also, anyone who thinks that people are using their real names on the Internet is probably wrong.