To be fair, the Nexus wireless charging pads suck. Samsung's are better, as they tend to be phone-sized, which makes for much easier alignment. http://www.samsung.com/us/mobi...
That's interesting. Coding as a kid, I more or less came up with the same principle for my little programs. I also later figured that it was misguided to leave robustness up to the implementation, instead of the specification (or in my case the function definition).
API functions that have any reasonable expectations for default values should just define those defaults, not silently default to something seemly random and completely undocumented.
And I am a native Dutch speaker, and while (West) Flemish has its own ISO language code, they're really Dutch dialects and they are much more intelligible to me (and most Dutch) than West Frisian. West Frisian, now that is a language in its own right, even though it's spoken in Friesland, a Dutch province.
That's great, in theory. In reality it will just lead people to create very easy to remember passwords, since people are good at routine and not at things that change constantly. Those easy passwords, in turn, are much more easily cracked. How would you mitigate that risk, increasing the password change frequency?
I've worked with highly sensitive systems (*ahem* the Ogone payment system for one) that use silly policies like these, and yet are horribly unsafe. At one time when I tried to login with an expired password I got an error message saying that the password was not "completely" valid and that I should understand that the password is case-sensitive! Well, that message implies that they can do a case-insensitive check, which means they don't even hash passwords.
In my experience these policies just shift the responsibility for proper security to the end-user. Even though, in theory, it may act as a complementary security measure, in practice that's counterproductive for 99% of users. Also it is more often than not used as the only security measure (apart from the basic $input == $password).
Thank you. I've been saying this from the beginning and am very annoyed that every time people write about Heartbleed, it links to Codenomicon's site. Even if it was an independent discovery (which it wasn't) then it's still too much credit. People should just link to the official CVE...
What's more, if you are able to remember the details of the experiment, you are more than capable of remembering a few decimals of what is probably the most widely known constant in mathematics.
I am in fact a WhatsApp user, but I use it reluctantly. It has a history of security issues and in the end it's just a hack on top of XMPP standards. No to mention it is very centralized in nature.
Most of the others I mentioned use standards like XMPP and SIP, which means that you aren't tied to a single vendor or ISP. A jabber.org account can communicate perfectly with a jabme.org account, you just need an XMPP client and set your account. Granted, this sounds like a lot of work for the majority of lazy users, which is why I suggested Kontalk as an alternative. Which does use XMPP without ugly hacks on top of it, and yet uses the same concepts as WhatsApp.
I find it irritating when people fall for WhatsApp's propaganda that they are a "free" SMS replacement. They're not! You need an internet connection to use it just like any other internet messaging application. Newsflash; you pay a subscription fee for internet connections. And mobile internet connections come with quotas.
Granted, if you already pay for a mobile internet connection, IM will nearly always be cheaper than SMS. But that, too, goes for any IM app.
PS: I'm waiting for Kontalk to become usable before recommending it as the alternative to WhatsApp.
No, you are wrong. As I was talking about the iPhone (which has had 330 ppi ever since 2010), I am completely right. You suddenly include a completely different subject and then claim I was wrong. Way to go!
That chart doesn't really mean anything either, not in the least because we're talking about the low end of the spectrum here, which is near the base of that chart where it gets fuzzy. But let's have a look at something a bit more scientific, shall we.
Slashdot Mirror
Do you also see a huge bar at the bottom of the screen in Gnome 3? Or do you just not use Windows all that much
Hes
the cowards way out
Judging by their spelling, I'm absolutely positive they have a Slashdot account.
To be fair, the Nexus wireless charging pads suck. Samsung's are better, as they tend to be phone-sized, which makes for much easier alignment. http://www.samsung.com/us/mobi...
That's interesting. Coding as a kid, I more or less came up with the same principle for my little programs. I also later figured that it was misguided to leave robustness up to the implementation, instead of the specification (or in my case the function definition).
API functions that have any reasonable expectations for default values should just define those defaults, not silently default to something seemly random and completely undocumented.
And I am a native Dutch speaker, and while (West) Flemish has its own ISO language code, they're really Dutch dialects and they are much more intelligible to me (and most Dutch) than West Frisian. West Frisian, now that is a language in its own right, even though it's spoken in Friesland, a Dutch province.
You mean the "Vlamingen"?
To be fair, though, I like the Flemish dialect more than standard Dutch. More refined.
All of my old CDs will play will play, albeit with some skipping.
That's great, in theory. In reality it will just lead people to create very easy to remember passwords, since people are good at routine and not at things that change constantly. Those easy passwords, in turn, are much more easily cracked. How would you mitigate that risk, increasing the password change frequency?
I've worked with highly sensitive systems (*ahem* the Ogone payment system for one) that use silly policies like these, and yet are horribly unsafe. At one time when I tried to login with an expired password I got an error message saying that the password was not "completely" valid and that I should understand that the password is case-sensitive! Well, that message implies that they can do a case-insensitive check, which means they don't even hash passwords.
In my experience these policies just shift the responsibility for proper security to the end-user. Even though, in theory, it may act as a complementary security measure, in practice that's counterproductive for 99% of users. Also it is more often than not used as the only security measure (apart from the basic $input == $password).
Thank you. I've been saying this from the beginning and am very annoyed that every time people write about Heartbleed, it links to Codenomicon's site. Even if it was an independent discovery (which it wasn't) then it's still too much credit. People should just link to the official CVE...
What's more, if you are able to remember the details of the experiment, you are more than capable of remembering a few decimals of what is probably the most widely known constant in mathematics.
Except any Youtube downloader (including for mobile phones) have no trouble whatsoever downloading that video.
To be fair, they did release it in month 3 '14
(Replied to wrong comment at first)
To be fair, they did release it in month 3 '14
So would you prefer unstable software labeled "release quality" with a version number of 9.0?
To make matters worse we often see obnoxious theories introduced to confuse issues and maintain a status quot.
That's called muddying the waters and I frequently point that out to people I consider naive as well as people who exaggerate, IE the tinfoil hatters.
There are plenty of conspiracies and often the only conspiracy theory is the one where the conspirators are made out to be the victims.
With 200+ open tabs spread over 20 windows, personally I think I would crash long before the browser.
Not to mention flat.
I am in fact a WhatsApp user, but I use it reluctantly. It has a history of security issues and in the end it's just a hack on top of XMPP standards. No to mention it is very centralized in nature.
Most of the others I mentioned use standards like XMPP and SIP, which means that you aren't tied to a single vendor or ISP. A jabber.org account can communicate perfectly with a jabme.org account, you just need an XMPP client and set your account. Granted, this sounds like a lot of work for the majority of lazy users, which is why I suggested Kontalk as an alternative. Which does use XMPP without ugly hacks on top of it, and yet uses the same concepts as WhatsApp.
As are
- Hangouts
- Skype
- jabber.org
- jabme.de
- lightwitch.org
- ekiga.net
- antisip.com
- voipuser.org
- Tox (soon to be)
- Numerous others
In fact, all of the above are free of charge.
I'm sorry your Ubuntu install I thrashed, young Padawan.
I find it irritating when people fall for WhatsApp's propaganda that they are a "free" SMS replacement. They're not! You need an internet connection to use it just like any other internet messaging application. Newsflash; you pay a subscription fee for internet connections. And mobile internet connections come with quotas.
Granted, if you already pay for a mobile internet connection, IM will nearly always be cheaper than SMS. But that, too, goes for any IM app.
PS: I'm waiting for Kontalk to become usable before recommending it as the alternative to WhatsApp.
I wonder what company you are representing...
No, you are wrong. As I was talking about the iPhone (which has had 330 ppi ever since 2010), I am completely right. You suddenly include a completely different subject and then claim I was wrong. Way to go!
That chart doesn't really mean anything either, not in the least because we're talking about the low end of the spectrum here, which is near the base of that chart where it gets fuzzy. But let's have a look at something a bit more scientific, shall we.
So they basically bragged that they found the perfect pixel density @ 330 ppi... which is even worse.
In reality, they sticked with that pixel density because they have very strict (pixel-based) design constraints for their platform.
....Which proves my point