I've actually chosen an ISP that provides IPv6 (Free.fr) over a very slightly cheaper one that doesn't.
It's not that I actually need native IPv6 (Miredo works just fine), but providing native IPv6 indicates that the ISP is likely to be less clueless than its competitors when IPv4 addresses actually start running out. The assurance that they'll still be around next year is well worth the couple Euros I'm paying extra.
That's 14.57 square kilometers, the size of a small to medium-sized town, maybe 20000 to 50000 inhabitants.
According to Wikipedia, the Mojave desert is 65,000 km2, which is more than twice the surface of Belgium, or roughly one tenth the surface of France. (Yeah, America is big.)
A more interesting statistic is the amount of power produced by this installation, 400 MW, which is about 1/4 of a nuclear reactor, or one large wind farm.
both the sender and the receiver support the STARTTLS extension; and
the receiver has been configured with a certificate (even a self-signed one).
All modern mail servers support STARTTLS, and most ISPs have configured a certificate in their MX. To see if yours has, do the following:
$ host -t mx google.com
google.com mail is handled by 50 alt4.aspmx.l.google.com.
google.com mail is handled by 30 alt2.aspmx.l.google.com.
google.com mail is handled by 40 alt3.aspmx.l.google.com.
google.com mail is handled by 10 aspmx.l.google.com.
google.com mail is handled by 20 alt1.aspmx.l.google.com.
$ telnet aspmx.l.google.com smtp
Trying...
Connected to aspmx.l.google.com.
Escape character is '^]'.
220 mx.google.com ESMTP
EHLO localhost
250-mx.google.com at your service
250-SIZE 35882577
250-8BITMIME
250-STARTTLS
250 ENHANCEDSTATUSCODES
QUIT/blockquote
Email is inherently insecure, since it is transmitted in clear text
Most mail nowadays is transmitted over SSL. Yes, that's still vulnerable to MITM-ing, but it's no longer a simple matter of passive snooping.
If you're relying on the law to keep your email private, you've already lost.
Please. Strong privacy laws won't prevent ISPs from occasionally snooping on their users, granted. With no privacy laws, howver, expect your ISP to routinely spy on you, and sell the data to advertising companies.
Microsoft banned the GPL, not open source overall.
No, Microsoft banned all open source:
It would appear that Microsoft banned all copyleft licenses, notably all versions of the (L)GPL. It did not ban non-copyleft Free Software licenses, such as BSD or MIT/X11.
The test suite of Darcs needs a domain that doesn't exist. It used to use example.com for that purpose, which now fails:
Sat Jan 29 16:18:53 CET 2011 Ganesh Sittampalam
* switch test to use a URL we can make sure will fail
Seems like the behaviour of http://example.com/ changed to start serving
pages at all URLs...
We're not speaking about switching to pure IPv6. We're speaking of making Yahoo accessible over both IPv4 and IPv6.
Pure IPv4 ("legacy") sites will have no problem, they'll just contact Yahoo over IPv4. Properly configured dual-stack sites will have no problem, they'll have a choice between IPv4 and IPv6. It's only mis-configured clients that might have problems.
The article claims that 0.05% of Yahoo's customers are mis-configured. These 0.05% will need to either disable IPv6, or fix their systems.
--jch
You still need to develop almost all of your UI in Java, but the core functionality can be written in C or a subset of C++; Android is no longer for Java only.
Of course not; the goal is not to build a new network, but to make sure that the Internet can continue to grow. So what you get over IPv6 is just the current Internet, but with a good chance that it'll be still around in ten years.
Ah, the OSI model [sic, recte suite], [...] having never been implemented!
Saying that the full OSI suite has never been implemented is like saying that nobody implements the full set of standard track RFCs -- which is true, since some standard track RFCs are mis-designed or even contradict other standard-track RFCs.
Large parts of the OSI suite have been implemented, and some are still running today. For example, IS-IS over CLNP is commonly used for routing IP and IPv6 traffic on operators' backbones. (I was about to mention LDAP and X.509 before I realised they are not necessarily the best-designed parts of OSI.)
Where you are right, though, is that large parts of OSI are morasses of complexity that have only been implemented due to government mandate and have since been rightly abandoned.
Network neutrality is about the network being neutral w.r.t. the content it carries.
This is about content providers being neutral, not about network neutrality. Please do not try to confuse the network neutrality discussion by mixing it up with other, unrelated debates.
Beware what you wish for. Once people get used to ISPs being allowed to cut users off, it will become trivial to generalise the policy to other circumstances (such as censoring p2p traffic).
While it may be difficult to write a Windows app without Microsoft's tools, there's nobody telling me what applications I'm allowed to write, and restricting me from distributing an already-written application unless it fits their idea of what is right.
There's just two medium-tech tools that I use for my courses:
the course's web page, where I publish my lecture notes (PDFs) and any useful information (including project deadlines);
the per-course mailing list, open to the lecturers, the TAs and the students. This is used both for official announcements (the lecturer is hung-over and won't be able to come), for unofficial announcements (some students are going for beer tonight, everyone is welcome), and for class-related discussion (does anyone understand what's written on page 27 of the lecture notes?).
Two years ago I stopped printing and distributing the lecture notes, since they are available on the web page. Nobody complained -- some students print them out on their own, but most of them are happy to just consult them online.
The next version of popular torrent software should think about hashing the file names also... then the only request / response passing through the tracker will be "Hash 0x345fed017 is located at IP 1.2.3.4".
That's already the case -- the tracker only ever sees the info-hash, which is a SHA-1 hash of one part of the.torrent file. The filenames only appear in the.torrent file.
Of course, finding the filename corresponding to an info-hash is usually just a web search away.
Actually, the preferred way for a website to default to a language should be based on the browser indicated preference.
The Accept-Language header is designed for people speaking just one language, and is pretty useless for most of the world. It doesn't allow me to specify that I generally prefer Polish to English, but that I prefer an English original to a Polish (mis-)translation.
Please don't use HTTP content negotiation for user-visible attributes, such as language; reserve it to technical aspects, such as image formats.
Slashdot Mirror
Are YOU willing to pay an extra $5/mo for IPV6
I've actually chosen an ISP that provides IPv6 (Free.fr) over a very slightly cheaper one that doesn't.
It's not that I actually need native IPv6 (Miredo works just fine), but providing native IPv6 indicates that the ISP is likely to be less clueless than its competitors when IPv4 addresses actually start running out. The assurance that they'll still be around next year is well worth the couple Euros I'm paying extra.
That's 14.57 square kilometers, the size of a small to medium-sized town, maybe 20000 to 50000 inhabitants.
According to Wikipedia, the Mojave desert is 65,000 km2, which is more than twice the surface of Belgium, or roughly one tenth the surface of France. (Yeah, America is big.)
A more interesting statistic is the amount of power produced by this installation, 400 MW, which is about 1/4 of a nuclear reactor, or one large wind farm.
-- jch
All modern mail servers support STARTTLS, and most ISPs have configured a certificate in their MX. To see if yours has, do the following:
Email is inherently insecure, since it is transmitted in clear text
Most mail nowadays is transmitted over SSL. Yes, that's still vulnerable to MITM-ing, but it's no longer a simple matter of passive snooping.
If you're relying on the law to keep your email private, you've already lost.
Please. Strong privacy laws won't prevent ISPs from occasionally snooping on their users, granted. With no privacy laws, howver, expect your ISP to routinely spy on you, and sell the data to advertising companies.
-- jch
Hanlon's razor.
--jch
Microsoft banned the GPL, not open source overall.
No, Microsoft banned all open source:
It would appear that Microsoft banned all copyleft licenses, notably all versions of the (L)GPL. It did not ban non-copyleft Free Software licenses, such as BSD or MIT/X11.
as a chronic on-again-off-again Catholic
I understand. I have the same problem with smoking.
--jch
If you need a dns entry that doesn't exist, pick one that you are authoritative for and make sure it doesn't exist.
That's exactly what they did:
I think you're missing the point.
We're not speaking about switching to pure IPv6. We're speaking of making Yahoo accessible over both IPv4 and IPv6.
Pure IPv4 ("legacy") sites will have no problem, they'll just contact Yahoo over IPv4. Properly configured dual-stack sites will have no problem, they'll have a choice between IPv4 and IPv6. It's only mis-configured clients that might have problems.
The article claims that 0.05% of Yahoo's customers are mis-configured. These 0.05% will need to either disable IPv6, or fix their systems. --jch
Android NDK.
If they want their CPU platform to only be thought of as useful for running Android java apps
Note that since Android 1.5, there is a native development kit.
You still need to develop almost all of your UI in Java, but the core functionality can be written in C or a subset of C++; Android is no longer for Java only.
What's stopping Google from using code in the MeeGo base?
There's no GPL code in the Android userspace.
What is there different to see or do? Not much.
Of course not; the goal is not to build a new network, but to make sure that the Internet can continue to grow. So what you get over IPv6 is just the current Internet, but with a good chance that it'll be still around in ten years.
The IPv6 Mess.
FTP: needs two connections.
Which makes a lot of sense if you want to be able to send commands while a file transfer is going on.
SMTP: You can't send a line with the word "From" as the first word?
Yes you can. It's only the Berkeley implementation of SMTP that cannot.
Ah, the OSI model [sic, recte suite], [...] having never been implemented!
Saying that the full OSI suite has never been implemented is like saying that nobody implements the full set of standard track RFCs -- which is true, since some standard track RFCs are mis-designed or even contradict other standard-track RFCs.
Large parts of the OSI suite have been implemented, and some are still running today. For example, IS-IS over CLNP is commonly used for routing IP and IPv6 traffic on operators' backbones. (I was about to mention LDAP and X.509 before I realised they are not necessarily the best-designed parts of OSI.)
Where you are right, though, is that large parts of OSI are morasses of complexity that have only been implemented due to government mandate and have since been rightly abandoned.
Network neutrality is about the network being neutral w.r.t. the content it carries.
This is about content providers being neutral, not about network neutrality. Please do not try to confuse the network neutrality discussion by mixing it up with other, unrelated debates.
Should ISPs Cut Off Bot-infected Users? Yes.
Beware what you wish for. Once people get used to ISPs being allowed to cut users off, it will become trivial to generalise the policy to other circumstances (such as censoring p2p traffic).
Try writing a decent Windows app using gcc...
I think you may be missing the parent's point.
While it may be difficult to write a Windows app without Microsoft's tools, there's nobody telling me what applications I'm allowed to write, and restricting me from distributing an already-written application unless it fits their idea of what is right.
There's just two medium-tech tools that I use for my courses:
Two years ago I stopped printing and distributing the lecture notes, since they are available on the web page. Nobody complained -- some students print them out on their own, but most of them are happy to just consult them online.
The next version of popular torrent software should think about hashing the file names also ... then the only request / response passing through the tracker will be "Hash 0x345fed017 is located at IP 1.2.3.4".
That's already the case -- the tracker only ever sees the info-hash, which is a SHA-1 hash of one part of the .torrent file. The filenames only appear in the .torrent file.
Of course, finding the filename corresponding to an info-hash is usually just a web search away.
Could somebody who reads Russian please check the original text from the Komsomolskaya Pravda?
Actually, the preferred way for a website to default to a language should be based on the browser indicated preference.
The Accept-Language header is designed for people speaking just one language, and is pretty useless for most of the world. It doesn't allow me to specify that I generally prefer Polish to English, but that I prefer an English original to a Polish (mis-)translation.
Please don't use HTTP content negotiation for user-visible attributes, such as language; reserve it to technical aspects, such as image formats.