Yes, your bike may look impressive and be good for pulling the ladies, but can it pull a caravan? No! Can you put fourteen crates of beer in the back? No!
1. Expense (at least traditionally) of SSL Certificates. Although today that's not such a big issue, and an SSL certificate costs about the same as your domain registration. However, if you have multiple subdomains you still need a more expensive certificate.
2. Complication. It can be a highly confusing process for someone who's not an expert to do the certificate request process and the associated installation of the certificate. I know the first time I tried to do it, it went horribly wrong and I spent a day trying to sort it out.
3. Client Performance: SSL websites are slower than non-SSL websites. Not such a big deal again these days, but I remember when I had to wait it would seem forever for the images on my online banking site to load, cursing them every time for such a graphically-intensive SSL site.
4. IP addresses: This is a big one, if you host multiple websites on your server, and you only have a single IP address, you can't host more than one SSL certificate. So you need more IP addresses (which is not easy nowdays). Big deal for small company hosted websites, which are often on shared IPs.
5. Server Performance: A server that can cope with one million users per day using HTTP will not be able to cope with anywhere near that number of connections over HTTPS for obvious reasons. So you not only need a certificate, you potentially need a whole new server architecture to deal with it. Scale this up for a big business like Twitter or Facebook and you're talking implementation costs in high millions of dollars.
or ST-506 interface drives if you are just about to tell me that MFM is an encoding method rather than an interface. But they were called that back then. I remember!
Seawater contains 3.3 parts per billion of uranium, which according to wikipedia means there are about 4.5 billion tonnes of uranium in the world's oceans.
One leaky reactor isn't going to make a spot of difference.
Do they suffer from bit-rot, and have some kind of half-life?
I understand that eventually apps will fail to be supported by the developers, won't potentially work on more modern operating systems, and in some cases require updating in order to be able to work correctly with the rest of the world.
But it's a bit disingenuous to call this "degradation". The app continues to do what it always did. You're just wanting more out of it than you did before. The app didn't change, you did.
Wow. So there's a x in ten million chance (where x is the number of contacts you have minus 1) that it'll go to the wrong person. *
Stupid, but I don't think this is the problem being seen by so many people.
* - Or something like this. assuming entirely random distribution of numbers and all number combinations being valid and all phone numbers being same length.
Hate to say this, but your new iPhone is going to have a different UDID anyway. As long as your old phone is backed up and your new phone authorized to your itunes account, you shouldn't have any problems either way.
There's no reason why iOS have to send the genuine UDIDs to the app developer. If the app requests a UDID for the device, iOS should generate a key that is unique for that device AND THAT DEVELOPER.
So a developer can see if a user has (for example) used the previous 'free' version of their paid app, but these keys would be meaningless to other developers.
It may still be possible for developers to find out the UDID through unauthorized means, but then the developer would clearly be breaking Apple rules and is at risk of being kicked out of the appstore.
I should also point out for the sake of completeness that I do have google ads on my site as well, but to be honest they're proving pretty ineffective as a way of generating revenue, and I'll probably drop them.
> If the ads get too annoying I will tell my computer not to fetch them (blocking tools).
The honest thing to do, if you find the ads on a website too annoying, is not to visit that website again. If you continue to want to use the website in question but block the adverts, you're using a service they provide to you (at their cost) without in effect paying for it.
But publishers have to realise they can get what they want without intrusive advertising. It's only an arms race between advertisers to grab your attention if you give in to one advertiser's demands for uber-distracting animated crap, then all the other advertisers on your site will have to do the same. Sometimes you just have to say "No" to an advertising deal in order to do the right thing.
On my website which is supported by advertising, I'm pretty strict about how things work, small JPEG banners only (so no animation, flash, javascript or anything else), served from my server so no 3rd party tracking, and no adverts at all on the most important information pages. I could probably earn double what I earn now if I were to all the more intrusive type of adverts on my site. But only until my audience leave, which won't be long.
When the balance between advertisers and visitors is done right (which is what as a site publisher I've aimed for) you shouldn't get complaints about adverts, and people won't want to block them.
"The FBI believes that one third of the world's spam messages are being generated by one 23-year-old Russian man. Oleg Nikolaenko, also known by his alias Julian Assange, is being blamed for operating the Mega D botnet that sent spam emails from over 500,000 infected computers."
Slashdot Mirror
> if the shit really hits the fan,
Shit hitting the fan won't matter so much if the fan isn't spinning.
Print out your porn.
Probably.
That's all we need here. Gamma nazis
You mean lower than they were in, say, 1776?
"My used car is better than your new motorbike!"
Yes, your bike may look impressive and be good for pulling the ladies, but can it pull a caravan? No! Can you put fourteen crates of beer in the back? No!
Ok... In reverse order of significance:
1. Expense (at least traditionally) of SSL Certificates. Although today that's not such a big issue, and an SSL certificate costs about the same as your domain registration. However, if you have multiple subdomains you still need a more expensive certificate.
2. Complication. It can be a highly confusing process for someone who's not an expert to do the certificate request process and the associated installation of the certificate. I know the first time I tried to do it, it went horribly wrong and I spent a day trying to sort it out.
3. Client Performance: SSL websites are slower than non-SSL websites. Not such a big deal again these days, but I remember when I had to wait it would seem forever for the images on my online banking site to load, cursing them every time for such a graphically-intensive SSL site.
4. IP addresses: This is a big one, if you host multiple websites on your server, and you only have a single IP address, you can't host more than one SSL certificate. So you need more IP addresses (which is not easy nowdays). Big deal for small company hosted websites, which are often on shared IPs.
5. Server Performance: A server that can cope with one million users per day using HTTP will not be able to cope with anywhere near that number of connections over HTTPS for obvious reasons. So you not only need a certificate, you potentially need a whole new server architecture to deal with it. Scale this up for a big business like Twitter or Facebook and you're talking implementation costs in high millions of dollars.
Well, seeing as it's going to be a major INCREMENT of the X-Box family, I'd suggest the name Xcrement
Truism of the internet. The more crackpot your ideas are, the larger you have to set your HTML border widths on your table elements.
Who can accept an award on behalf of the Internet?
Al Gore, of course!
or ST-506 interface drives if you are just about to tell me that MFM is an encoding method rather than an interface. But they were called that back then. I remember!
Well, I guess this vindicates my decision to stick with MFM hard disks.
Seawater contains 3.3 parts per billion of uranium, which according to wikipedia means there are about 4.5 billion tonnes of uranium in the world's oceans.
One leaky reactor isn't going to make a spot of difference.
I'm not sure animals would find it any easier to solve the captchas than we do :)
I was disappointed that the article wasn't split onto 8 different sub-pages needing me to hunt for the "print" option" to read it without adverts.
Mass Hysteria, Dogs and Cats living together, etc.
How, exactly, do enterprise apps degrade?
Do they suffer from bit-rot, and have some kind of half-life?
I understand that eventually apps will fail to be supported by the developers, won't potentially work on more modern operating systems, and in some cases require updating in order to be able to work correctly with the rest of the world.
But it's a bit disingenuous to call this "degradation". The app continues to do what it always did. You're just wanting more out of it than you did before. The app didn't change, you did.
I, for one, do NOT welcome our cloud-based overlords.
Don't worry. Every cloud has a silver lining.
Wow. So there's a x in ten million chance (where x is the number of contacts you have minus 1) that it'll go to the wrong person. *
Stupid, but I don't think this is the problem being seen by so many people.
* - Or something like this. assuming entirely random distribution of numbers and all number combinations being valid and all phone numbers being same length.
Hate to say this, but your new iPhone is going to have a different UDID anyway. As long as your old phone is backed up and your new phone authorized to your itunes account, you shouldn't have any problems either way.
There's no reason why iOS have to send the genuine UDIDs to the app developer. If the app requests a UDID for the device, iOS should generate a key that is unique for that device AND THAT DEVELOPER.
So a developer can see if a user has (for example) used the previous 'free' version of their paid app, but these keys would be meaningless to other developers.
It may still be possible for developers to find out the UDID through unauthorized means, but then the developer would clearly be breaking Apple rules and is at risk of being kicked out of the appstore.
Jolyon
I should also point out for the sake of completeness that I do have google ads on my site as well, but to be honest they're proving pretty ineffective as a way of generating revenue, and I'll probably drop them.
> If the ads get too annoying I will tell my computer not to fetch them (blocking tools).
The honest thing to do, if you find the ads on a website too annoying, is not to visit that website again. If you continue to want to use the website in question but block the adverts, you're using a service they provide to you (at their cost) without in effect paying for it.
But publishers have to realise they can get what they want without intrusive advertising. It's only an arms race between advertisers to grab your attention if you give in to one advertiser's demands for uber-distracting animated crap, then all the other advertisers on your site will have to do the same. Sometimes you just have to say "No" to an advertising deal in order to do the right thing.
On my website which is supported by advertising, I'm pretty strict about how things work, small JPEG banners only (so no animation, flash, javascript or anything else), served from my server so no 3rd party tracking, and no adverts at all on the most important information pages. I could probably earn double what I earn now if I were to all the more intrusive type of adverts on my site. But only until my audience leave, which won't be long.
When the balance between advertisers and visitors is done right (which is what as a site publisher I've aimed for) you shouldn't get complaints about adverts, and people won't want to block them.
> Seriously, this is turning into a bad Oliver Stone movie.
As opposed to what other type of Oliver Stone movie, exactly?
>somebody should kill the bastard
Let me help fix the article for your benefit:
"The FBI believes that one third of the world's spam messages are being generated by one 23-year-old Russian man. Oleg Nikolaenko, also known by his alias Julian Assange, is being blamed for operating the Mega D botnet that sent spam emails from over 500,000 infected computers."