Comment Re:QR codes don't all have destinations (Score 1) 234
I kinda did in my next sentence, but whatever..
I kinda did in my next sentence, but whatever..
But every implementation I've seen of a QR code reader in Android and IOS also gives you the option to inspect the content visually before acting on it. They ask if you want to proceed.
Of course one could argue the click-thru generation does not know enough to evaluate the content, but then these are the same people that no amount of malware/antivirus software can protect.
Is the confirmation something like OK/Cancel? I also tend to click OK buttons without hardly even reading them. That's why potentially security sensitive questions shouldn't have such simple buttons, but rather two (radio?) buttons that require you to read (and hopefully understand) what you're doing, such as: "Replace network settings from QR" and "Keep the existing network settings".
Yes, there are some advantages to using SQL database, like I said.. But I highly doubt "huge speed advantage" is one of them, unless you compare to a really badly set up system. I know people have switched from DBMail to Dovecot simply because Dovecot is so much faster..
Email isn't stored in SQL, because typically it's rather pointless. Full text search indexing doesn't require SQL, and it's more efficient without SQL anyway. There are some good use cases for storing emails in SQL database, but efficiency isn't one of them.
I wasn't planning on fixing all of security problems, but the typical case of clicking open random email attachments or running random programs from internet should and could be made safe, while still keeping the user interface user friendly. Those are the reasons for most of today's security problems.
SELinux doesn't address the problem. I agree with grandparent, although I think the focus should be more about on the UI side. The really low level implementation could perhaps be addressed with SELinux, but it's not a practical solution for any GUI app currently. For example how would you prevent Open Office from deleting everything in your home dir with SELinux, while still allowing it to read and write arbitrary documents? Yeah, you can't unless you manually go changing the labels every time you want to write somewhere.
I thought about how to implement an actually secure operating system in 2004, where you could safely just run any random program from internet, but no one cared to listen and I moved on.
The first thing that popped out as I glanced through the post was:
"They can cross oceans.... Slowly. They only move at 1-2 knots, which is a great speed for data collection."
And I thought to myself, "slowly?
I lose interest to code after even a single beer. Beer makes me want to talk to other people (even about coding). It makes me enjoy some TV shows/movies more. But what's the point of coding drunk? Seems like a waste of beer.
And this surprises you exactly
The apps can tell the firewall to open up a port for a period of time and then shut it back down.
I mean, it sounds almost like they could listen() a specific port, and once they're done with it, they could close() it! If all applications could always do this automatically, I think we could actually get rid of manual firewall configuration entirely!
So
Oh, just read 0olong's comment. That explains it then. Only native english people and dutch have this problem.
Obvious non native English speakers do not understand that "then" is a form of time and "than" is a form of consequence.
I'm pretty sure it's the native speakers who have the most trouble with this. Many foreign countries teach English primarily by reading and writing it. Then the than/then difference is obvious. It's only when you learn English by listening that you have trouble with this. I only started having these kind of accidents once I started thinking/speaking fluently in English (not just then/than, but things like file/fail).
Oh yes, I am a native Dutch speaker.
Maybe they teach you English differently down there than in Finland
TFA and the original source (press release from Forum Nokia, http://blogs.forum.nokia.com/blog/nokia-developer-news/2011/03/25/open-letter-to-developer-community ) reveal that:
Over the past weeks we have been evaluating our Symbian roadmap and now feel confident we will have a strong portfolio of new products during our transition period - i.e. 2011 and 2012.
And further
Iâ(TM)ve been asked many times how long we will support Symbian and Iâ(TM)m sure for many of you it feels we have been avoiding the question. The truth is, it is very difficult to provide a single answer. We hope to bring devices based on Windows Phone to market as quickly as possible, but Windows Phone will not have all language and all localization capabilities from day one. [...] That is why we cannot give you the date when Symbian will no longer be supported.
Finally it is stated:
What I can promise you is that we will not just abandon Symbian users or developers. As a very minimum, we have a legal obligation, varying in length between countries, to support users for a period of time after the last product has been sold.
So there's nothing saying that Nokia will suddenly stop supporting Symbian in 2012. It'll just fade out gradually, and even they don't admit knowing when it will fade out completely.
Look at the first "Look and feel" dialog. What the hell is that "cancel" button doing in there? There are two choices. One of them is already selected, but the OK button is greyed out. I think, since I've never used Vista.. Even if that greying out means it's simply not focused, what is the purpose of the OK/Cancel there? Does the cancel mean the same as the second option? Does it mean it's going to ask you again the next time? It should be clearly said there, not left to user's guesstimation. I guess it's an improvement, but that page is definitely not something that should be pointed to as an example of good UI design.
If all else fails, lower your standards.
