I think you do not understand what Mozilla does. (paraphrasing) The mission of Mozilla is to keep the internet and web free of proprietary API and patent problems. To make sure every protocol and system is open and to keep it 'innovative' and prevent lock-in.
They do this by creating 'products' that people use, as long as the open specifications are the standard (as in widely deploy, industry practices) they are fulfilling their mission.
In the mobile space, their is very little currently using open specifications. Just think of the problems Google is having with Dalvik/Oracle or the Apple App Store. So they want to get into that space.
I wouldn't bet on Twitter remaining for long either. They are operating at a loss and venture capital is the only thing keeping it going right now. For years they literally said they didn't know if they even had a business model.
Is Twitter is to big to fail ? After all it is 4 times as big as MySpace (and supposedly it failed).
The people that invested in Skype did get their money back, Microsoft probably won't directly. Maybe indirectly, we don't know.
I would guess that this is only if you want to use the installer. If you have some way of updating the dll's all on the computers from a central location. It would be fine ?
Building datacenters in different climates doesn't really help.
The reason companies like Google have as many datacenters isn't just about redudancy. But the biggest reason is the latency between the user and the server. Datacenters need to be close to the user to get the data to the user quickly.
That is why many companies use CDN's and one of the reasons why Google started the SPDY project (because of TCP-slowstart, SPDY tries to make HTTP faster by re-using TCP-connections).
Luckily Microsoft released IE9 to make life easier... euh... well, not so much. But atleast they will release IE10 with Windows 8. Which means an other new version to support. Should be 'fun'
Actually, if people think OpenBSD's release schedule is a good thing, then I have no idea why people would complain about Mozilla trying to mold their release cycle in a similair fashing.
Because OpenBSD has been doing what Chrome did from the start: a timed release cycle. Take the features that are done and only release those.
The Mozilla folks still need to learn a bit I'm sure. They'll probably get the hang of it soon.
* the normal stuff to handle email: - like a domain - like an incoming/outgoing mail server, probably spamfiltering - probably a IMAP/POP-server - or maybe a webserver for webmail - and the a webmail program
If you want to implement the Verified Email Protocol, this adds:
You need a webserver for your domain which has a http://example.com/.well-known/host-meta file which points to an URL where the public-key-information can be queried.
That is all this adds.
If you want to set this up for users, you probably would want an extra settings page in the webmail-app for setting up the public key.
Yes and no. This project has been in the works for over 2 years at Mozilla in different forms, among being based around OpenID and other systems.
The Verified Email Protocol specification has been in the works for a while now too.
The biggest problem was, I think, that they still needed to solve that not all email-providers would (immediately) implement this, so that is what the BrowserID project is for.
I think the private key in the browser is used to generate a key per site, which can be used to verify you own the public key which is related to your email-address.
Slashdot Mirror
I think you do not understand what Mozilla does. (paraphrasing) The mission of Mozilla is to keep the internet and web free of proprietary API and patent problems. To make sure every protocol and system is open and to keep it 'innovative' and prevent lock-in.
They do this by creating 'products' that people use, as long as the open specifications are the standard (as in widely deploy, industry practices) they are fulfilling their mission.
In the mobile space, their is very little currently using open specifications. Just think of the problems Google is having with Dalvik/Oracle or the Apple App Store. So they want to get into that space.
And some of the 'biggest people on Twitter' also post on Facebook. It did not make Twitter irrelevant.
I wouldn't bet on Twitter remaining for long either. They are operating at a loss and venture capital is the only thing keeping it going right now. For years they literally said they didn't know if they even had a business model.
Is Twitter is to big to fail ? After all it is 4 times as big as MySpace (and supposedly it failed).
The people that invested in Skype did get their money back, Microsoft probably won't directly. Maybe indirectly, we don't know.
Please tell people to install Chrome, not Comodo Dragon. Comodo uses it to block certain competing SSL-provider products they think are 'unsafe'.
Maybe just embarrassing ?
"...and many people participating in the double blind listening test'
Maybe that is why it ended up on slashdot ?
I do think he got the basic idea right:
The end product of the scientist is the output of the program and the conclusions he/she derives from that.
The end product of the professional programmer is the program and it will very probably need to be changed again at a later time.
Well, that has 2 sides: it would be good to get many apps on the devices.
But on the other side we have patens. Considering how Google now is already in court with Oracle over that same Dalvik.
I would guess that this is only if you want to use the installer. If you have some way of updating the dll's all on the computers from a central location. It would be fine ?
Building datacenters in different climates doesn't really help.
The reason companies like Google have as many datacenters isn't just about redudancy. But the biggest reason is the latency between the user and the server. Datacenters need to be close to the user to get the data to the user quickly.
That is why many companies use CDN's and one of the reasons why Google started the SPDY project (because of TCP-slowstart, SPDY tries to make HTTP faster by re-using TCP-connections).
In the Netherlands there is already a project with datacenters and greenhouses.
And what about the VM's ?
Or do you have a cluster with OpenVZ (they do not have their own kernel) ?
Not so much, thet use encryption instead.
Just say it, corporate users want: security-only updates.
Luckily Microsoft released IE9 to make life easier... euh... well, not so much. But atleast they will release IE10 with Windows 8. Which means an other new version to support. Should be 'fun'
Actually, if people think OpenBSD's release schedule is a good thing, then I have no idea why people would complain about Mozilla trying to mold their release cycle in a similair fashing.
Because OpenBSD has been doing what Chrome did from the start: a timed release cycle. Take the features that are done and only release those.
The Mozilla folks still need to learn a bit I'm sure. They'll probably get the hang of it soon.
I thought it was mostly Windows XP without some SP's with also do not support activation and thus have no IE7 or IE8.
IE6 does support IPv6, if you install IPv6 in Windows XP.
I've atleast see it send AAAA DNS -queries.
You probably mean something else, because SSL v2 is much older and very insecure:
'version 2.0 was released in February 1995 but "contained a number of security flaws which ultimately led to the design of SSL version 3.0"'
http://en.wikipedia.org/wiki/Transport_Layer_Security
With I had mod points. Totally right.
Hell, even Microsoft will try it with Windows 8...?
You need:
* the normal stuff to handle email:
- like a domain
- like an incoming/outgoing mail server, probably spamfiltering
- probably a IMAP/POP-server
- or maybe a webserver for webmail
- and the a webmail program
If you want to implement the Verified Email Protocol, this adds:
You need a webserver for your domain which has a http://example.com/.well-known/host-meta file which points to an URL where the public-key-information can be queried.
That is all this adds.
If you want to set this up for users, you probably would want an extra settings page in the webmail-app for setting up the public key.
You don't need to open/close the browser.
There will be a UI for that, where you choose what identity you want to use for the site you are looking at.
Yes and no. This project has been in the works for over 2 years at Mozilla in different forms, among being based around OpenID and other systems.
The Verified Email Protocol specification has been in the works for a while now too.
The biggest problem was, I think, that they still needed to solve that not all email-providers would (immediately) implement this, so that is what the BrowserID project is for.
I think the private key in the browser is used to generate a key per site, which can be used to verify you own the public key which is related to your email-address.
But I could be wrong. :-)
Which is depends on a whole lot of big protocols which are much more complicated than need be.
Have a look at the specification:
https://wiki.mozilla.org/Labs/Identity/VerifiedEmailProtocol
https://wiki.mozilla.org/Identity/Verified_Email_Protocol/Latest
Encrypt all the passwords and keys before storing them on disk and have the user provide a passprase before using the browser.
I expect that is how it will work.