Re:All you need to know:
on
R.I.P. FTP
·
· Score: 5, Insightful
This assumes your "known good" backup is really clean. If you can't tell whether your current system is clean after removing the malware, how can you know whether your last backup was clean?
I usually design web password thingies like that with minimal requirements: password must be at least four characters, cannot be all lower-case letters (but all caps or all numbers is fine), cannot be all the same character repeated and cannot be entirely sequential like "12345" or "ABCDE" (but these are valid substrings as long as there's something else too). Oh, and I hadn't realized I'd done this, but apparently the character set is limited to \x20 to \x7e; no control characters, upper ASCII, or Unicode. I'm not sure why I put that restriction in, but it shouldn't be an issue for most English-speaking people.
Perl 6 may be a better language than Perl 5, but it won't address any of the issues that make people prefer Python. One of the goals of Perl 6 is to make sure that it's "still Perl", but the entire Perl philosophy is incompatible with what businesses are looking for. Java has it, Python has it, Perl doesn't. Perl kicks their ass for anything one person is going to write, but for large projects maintained by a team, you need structure, and Perl doesn't force one on you.
When Perl 6 comes out, there will be a tsunami of developers falling over themselves to abandon everything else and port everything over to the new uber scripting language.
No, there won't. Few people, outside the inner circle who are actually developing the language and building its tools, care about Perl 6 at all. Once it's released in a stable form, some people will switch to Perl 6, but other people will switch to other languages (since existing code won't be entirely compatible anyway). Many will just continue using Perl 5, because it's good enough. And of course, most people who are using other languages will continue to do so.
As a Perl lover it really pains me to say it, but Python appears to be really taking off. You're going to start seeing Python used by businesses in the same way that they've been using Java over the past decade.
Yeah, saying that nothing but Exchange has the features we want is not the same as saying we can't be bothered to learn how to use something else.
Somebody else mentioned that sharing a folder (with subfolders) is a pain in the ass with GMail. That's a great example. I've done it with Outlook/Exchange; at an ISP I used to work for, the abuse@ mail came to a shared inbox that several people had access to, and we could do things like mark messages as read/unread, create temporary folders to sort certain messages into, etc. and everyone on my team could see what everyone else was doing. This is really simple functionality; how easy is it to set that up with your mail server?
I suspect a lot of people who complain that Windows isn't a real operating system haven't really used it that much in the past eight years or so, so they're simply unaware that it isn't the steaming pile of crap that Win98 used to be. After all, people defended Win98 back then, the same way they're defending XP now, so how would an outsider know that it's actually completely different?
I think flag burning is symbolic of an idea that is so alien to many of us that we don't really comprehend the symbol.
If you had never studied history, would you know that burning a cross on someone's front lawn is a racist symbol? I've heard of cross burning and probably seen it portrayed in a movie somewhere, but it doesn't really hold any particular significance for me, since I'm not aware that anyone I know is a racist or the victim of that kind of racism. Flag burning doesn't hold any particular significance for me either, probably for the same reason. I understand it's done in protest of.. something, but I don't really get it.
Google isn't designed to answer questions, it's designed to find web sites. People get this confused, because quite often when you search for a question, Google will find a page that contains the answer, but as you've demonstrated, for a lot of question types that's not going to be the case.
But of course, that's why this sort of experiment is good: by logging all the questions, we can see how people want to use a service like this, and can see that providing access to people who are knowledgeable about agriculture and health care will be much more useful than providing access to Google. That's good to know. Next step: do that.
Of course, but the only useful information it contains is the date the photo was taken, and iPhoto doesn't have any equivalent to iTunes' Browse feature as far as I'm aware.
I just checked; none of my Linux boxes have "ncal". What is it, and why should OSX have it?
What apps expect you to use Mail, and don't respect your preference to use something else for mailto: links? Moving this setting into the application instead of System Preferences was retarded, but all apps should respect it. I don't remember having a problem when I used Thunderbird.
The app-centric database works great for MP3 files that have searchable and browseable metadata. The problem with iPhoto is that my pictures don't have this sort of metadata, so I have to organize them into albums myself, and it works about as well as organizing MP3s into playlists in iTunes without being able to search or browse, which would completely suck.
Ah. So would you also "interpret" a predictable voicemail number and default PIN as an "invitation" ?
I have no way to know it's a default PIN unless I attempt to gain access. Requiring a PIN (and not telling me what it is) is an indication that I am not welcome, whether I could guess the PIN or not.
If the voicemail greeting included the PIN in the message, that would be comparable to including a WPA key in an SSID: "Hi, thanks for calling. I'm not home right now, but the PIN for this voicemail box is '1379'. Feel free to poke around!"
Using anything that belongs to other people without asking is "impolite".
Not if they've already indicated that it's OK. Bothering them by asking would then be impolite.
Not for the software my mom wants to use with her music students, there isn't. Sure, you can cobble something together that is technically capable of running the application, but unless the timing of both the sound and video is perfect, it's completely useless.
Pay close attention to the security warning your SSH client gives you the first time you try to connect. It's usually safe to assume that your session isn't being hijacked the first time you connect, but if you ever see that warning again, double-check the hostname you entered, and if you haven't obviously done something silly, it's time to make a phone call.
Fortunately, SSL thwarts this sort of thing. Newer browsers show SSL EV certificate information more prominently in the address bar as well as highlighting the domain name portion of the URL; users who bother to look at both of these will be secure. Users who don't are screwed, though, until DNSSEC becomes the norm (maybe in a decade or so?).
No, typosquatting is registering a domain name similar to a popular domain, e.g. goggle.com, so that when someone makes that particular typo when trying to reach the popular web site, they'll end up at your site instead. The key here is that typosquatting involves registering a domain name, thus preventing anyone else from registering the same domain for their own legitimate purposes (e.g. selling swim-related accessories), hence the "squatting" part.
This is completely different. Comcast isn't registering any additional domains; they're not preventing anyone else from registering whatever domains are available. What Comcast is doing is configuring their DNS servers so that for any domain that doesn't exist, instead of returning a "this doesn't exist" message (NXDOMAIN), they're returning the IP address of their own web site. This is similar to typosquatting in that the end user could end up an a web site they weren't expecting if they make a typo while entering a URL, seeing a page of advertising instead of just getting an error message. However, while typosquatting is merely annoying, what Comcast is doing breaks things.
The simple explanation is that the Internet is not the World Wide Web. Domain names are used for other things besides web sites, and getting an IP address back for a domain that doesn't exist causes all sorts of technical problems. For example, to cut down on spam, my e-mail server automatically rejects any incoming e-mail where the "From" address is at a domain that doesn't exist, but if my DNS servers lie to me, my e-mail server will think that all domains exist, and it won't reject anything.
As long as your ISP makes it clear what they're doing, and provides a simple way to opt out, this shouldn't be a huge problem. It was a huge problem when Verisign tried to do it, because they're not an ISP; they operate the Registry for all.com/.net domain names, so they are the authoritative source that everyone has to rely on. You don't have to use your own ISP's DNS servers, though (unless they firewall port 53, but that's not common).
I interpret their SSID broadcast and lack of encryption to be an invitation. If they had the SSID broadcast turned off, or if they had encryption turned on (and didn't deliberately make the key available to me, e.g. by putting it in the SSID, or posting it on the wall) then I would assume I wasn't invited. Gaining access by monitoring encrypted traffic and doing a brute-force crack on the encryption key would be impolite.
The trouble was, when users complained about Flash-related performance or stability problems, Mozilla developers would typically respond "try disabling plugins and extensions, and if the problem goes away, the matter is resolved." This is a common problem of open source: users and developers don't have the same kinds of problems, and developers aren't especially interested in meeting the needs of the users, preferring instead to continue to meet the needs of the developers.
Of course, if Flash were open-source, it might be possible to improve the performance and stability, so users wouldn't complain to Mozilla. Adobe obviously isn't going to do it. Since that's not happening, we need to expect plugins to be buggy and unstable, and work around the problem instead of hoping the problem gets fixed.
In fact, I remember hearing that professional photographers were buying iPods, ripping them apart, and removing the hard drives, because the iPod was selling for less than the market value of 5GB 1.8" CF hard drives (which could be used in a digital camera).
The point being, I think, that if you feed a browser bad XHTML it won't render at all, and thus you're not relying on the web developer being clueful enough to validate their HTML.
That might be true if you set the MIME type to application/xhtml+xml, but since that breaks Internet Explorer, nobody does that. If you set the MIME type to text/html, browsers will just ignore your extra slashes and treat bad XHTML exactly like bad HTML, and neither the web developer nor the user will ever know there's a problem with the code.
Broken XHTML does not make people write valid code. Validation makes people write valid code.
Of course, some people became aware of the W3C's validation service at the same time they became aware of XHTML, so they began writing XHTML and validating it. XHTML is not the key here.
Yes, that's what the "Extrans" option does. What Slashdot calls "Plain Text" is something else entirely. This is a labeling problem, not a technical problem.
Slashdot Mirror
This assumes your "known good" backup is really clean. If you can't tell whether your current system is clean after removing the malware, how can you know whether your last backup was clean?
I usually design web password thingies like that with minimal requirements: password must be at least four characters, cannot be all lower-case letters (but all caps or all numbers is fine), cannot be all the same character repeated and cannot be entirely sequential like "12345" or "ABCDE" (but these are valid substrings as long as there's something else too). Oh, and I hadn't realized I'd done this, but apparently the character set is limited to \x20 to \x7e; no control characters, upper ASCII, or Unicode. I'm not sure why I put that restriction in, but it shouldn't be an issue for most English-speaking people.
Perl 6 may be a better language than Perl 5, but it won't address any of the issues that make people prefer Python. One of the goals of Perl 6 is to make sure that it's "still Perl", but the entire Perl philosophy is incompatible with what businesses are looking for. Java has it, Python has it, Perl doesn't. Perl kicks their ass for anything one person is going to write, but for large projects maintained by a team, you need structure, and Perl doesn't force one on you.
When Perl 6 comes out, there will be a tsunami of developers falling over themselves to abandon everything else and port everything over to the new uber scripting language.
No, there won't. Few people, outside the inner circle who are actually developing the language and building its tools, care about Perl 6 at all. Once it's released in a stable form, some people will switch to Perl 6, but other people will switch to other languages (since existing code won't be entirely compatible anyway). Many will just continue using Perl 5, because it's good enough. And of course, most people who are using other languages will continue to do so.
As a Perl lover it really pains me to say it, but Python appears to be really taking off. You're going to start seeing Python used by businesses in the same way that they've been using Java over the past decade.
Yeah, saying that nothing but Exchange has the features we want is not the same as saying we can't be bothered to learn how to use something else.
Somebody else mentioned that sharing a folder (with subfolders) is a pain in the ass with GMail. That's a great example. I've done it with Outlook/Exchange; at an ISP I used to work for, the abuse@ mail came to a shared inbox that several people had access to, and we could do things like mark messages as read/unread, create temporary folders to sort certain messages into, etc. and everyone on my team could see what everyone else was doing. This is really simple functionality; how easy is it to set that up with your mail server?
I suspect a lot of people who complain that Windows isn't a real operating system haven't really used it that much in the past eight years or so, so they're simply unaware that it isn't the steaming pile of crap that Win98 used to be. After all, people defended Win98 back then, the same way they're defending XP now, so how would an outsider know that it's actually completely different?
Maybe this simply demonstrates that the type of people who would choose a neutral word to say are likely to have a lower tolerance for pain?
"Torch" in British English = "Flashlight" in American English.
I think flag burning is symbolic of an idea that is so alien to many of us that we don't really comprehend the symbol.
If you had never studied history, would you know that burning a cross on someone's front lawn is a racist symbol? I've heard of cross burning and probably seen it portrayed in a movie somewhere, but it doesn't really hold any particular significance for me, since I'm not aware that anyone I know is a racist or the victim of that kind of racism. Flag burning doesn't hold any particular significance for me either, probably for the same reason. I understand it's done in protest of.. something, but I don't really get it.
Google isn't designed to answer questions, it's designed to find web sites. People get this confused, because quite often when you search for a question, Google will find a page that contains the answer, but as you've demonstrated, for a lot of question types that's not going to be the case.
But of course, that's why this sort of experiment is good: by logging all the questions, we can see how people want to use a service like this, and can see that providing access to people who are knowledgeable about agriculture and health care will be much more useful than providing access to Google. That's good to know. Next step: do that.
Of course, but the only useful information it contains is the date the photo was taken, and iPhoto doesn't have any equivalent to iTunes' Browse feature as far as I'm aware.
I just checked; none of my Linux boxes have "ncal". What is it, and why should OSX have it?
What apps expect you to use Mail, and don't respect your preference to use something else for mailto: links? Moving this setting into the application instead of System Preferences was retarded, but all apps should respect it. I don't remember having a problem when I used Thunderbird.
The app-centric database works great for MP3 files that have searchable and browseable metadata. The problem with iPhoto is that my pictures don't have this sort of metadata, so I have to organize them into albums myself, and it works about as well as organizing MP3s into playlists in iTunes without being able to search or browse, which would completely suck.
Ah. So would you also "interpret" a predictable voicemail number and default PIN as an "invitation" ?
I have no way to know it's a default PIN unless I attempt to gain access. Requiring a PIN (and not telling me what it is) is an indication that I am not welcome, whether I could guess the PIN or not.
If the voicemail greeting included the PIN in the message, that would be comparable to including a WPA key in an SSID: "Hi, thanks for calling. I'm not home right now, but the PIN for this voicemail box is '1379'. Feel free to poke around!"
Using anything that belongs to other people without asking is "impolite".
Not if they've already indicated that it's OK. Bothering them by asking would then be impolite.
Not for the software my mom wants to use with her music students, there isn't. Sure, you can cobble something together that is technically capable of running the application, but unless the timing of both the sound and video is perfect, it's completely useless.
So, does anyone know of a KVM switch that works with Dual-Link DVI?
Pay close attention to the security warning your SSH client gives you the first time you try to connect. It's usually safe to assume that your session isn't being hijacked the first time you connect, but if you ever see that warning again, double-check the hostname you entered, and if you haven't obviously done something silly, it's time to make a phone call.
Fortunately, SSL thwarts this sort of thing. Newer browsers show SSL EV certificate information more prominently in the address bar as well as highlighting the domain name portion of the URL; users who bother to look at both of these will be secure. Users who don't are screwed, though, until DNSSEC becomes the norm (maybe in a decade or so?).
No, typosquatting is registering a domain name similar to a popular domain, e.g. goggle.com, so that when someone makes that particular typo when trying to reach the popular web site, they'll end up at your site instead. The key here is that typosquatting involves registering a domain name, thus preventing anyone else from registering the same domain for their own legitimate purposes (e.g. selling swim-related accessories), hence the "squatting" part.
This is completely different. Comcast isn't registering any additional domains; they're not preventing anyone else from registering whatever domains are available. What Comcast is doing is configuring their DNS servers so that for any domain that doesn't exist, instead of returning a "this doesn't exist" message (NXDOMAIN), they're returning the IP address of their own web site. This is similar to typosquatting in that the end user could end up an a web site they weren't expecting if they make a typo while entering a URL, seeing a page of advertising instead of just getting an error message. However, while typosquatting is merely annoying, what Comcast is doing breaks things.
The simple explanation is that the Internet is not the World Wide Web. Domain names are used for other things besides web sites, and getting an IP address back for a domain that doesn't exist causes all sorts of technical problems. For example, to cut down on spam, my e-mail server automatically rejects any incoming e-mail where the "From" address is at a domain that doesn't exist, but if my DNS servers lie to me, my e-mail server will think that all domains exist, and it won't reject anything.
As long as your ISP makes it clear what they're doing, and provides a simple way to opt out, this shouldn't be a huge problem. It was a huge problem when Verisign tried to do it, because they're not an ISP; they operate the Registry for all .com/.net domain names, so they are the authoritative source that everyone has to rely on. You don't have to use your own ISP's DNS servers, though (unless they firewall port 53, but that's not common).
I interpret their SSID broadcast and lack of encryption to be an invitation. If they had the SSID broadcast turned off, or if they had encryption turned on (and didn't deliberately make the key available to me, e.g. by putting it in the SSID, or posting it on the wall) then I would assume I wasn't invited. Gaining access by monitoring encrypted traffic and doing a brute-force crack on the encryption key would be impolite.
The trouble was, when users complained about Flash-related performance or stability problems, Mozilla developers would typically respond "try disabling plugins and extensions, and if the problem goes away, the matter is resolved." This is a common problem of open source: users and developers don't have the same kinds of problems, and developers aren't especially interested in meeting the needs of the users, preferring instead to continue to meet the needs of the developers.
Of course, if Flash were open-source, it might be possible to improve the performance and stability, so users wouldn't complain to Mozilla. Adobe obviously isn't going to do it. Since that's not happening, we need to expect plugins to be buggy and unstable, and work around the problem instead of hoping the problem gets fixed.
In fact, I remember hearing that professional photographers were buying iPods, ripping them apart, and removing the hard drives, because the iPod was selling for less than the market value of 5GB 1.8" CF hard drives (which could be used in a digital camera).
The point being, I think, that if you feed a browser bad XHTML it won't render at all, and thus you're not relying on the web developer being clueful enough to validate their HTML.
That might be true if you set the MIME type to application/xhtml+xml, but since that breaks Internet Explorer, nobody does that. If you set the MIME type to text/html, browsers will just ignore your extra slashes and treat bad XHTML exactly like bad HTML, and neither the web developer nor the user will ever know there's a problem with the code.
Broken XHTML does not make people write valid code. Validation makes people write valid code.
Of course, some people became aware of the W3C's validation service at the same time they became aware of XHTML, so they began writing XHTML and validating it. XHTML is not the key here.
Yes, that's what the "Extrans" option does. What Slashdot calls "Plain Text" is something else entirely. This is a labeling problem, not a technical problem.