I believe these devices are called "Otoro", because that is what it says on this page:
"Otoro
Otoro is a phone being used as a test and development platform as a low-to-midrange smartphone. Most core Firefox OS developers are working on Otoro."
Actually, you might not have noticed, but if you follow the rules then the last few years browsers have become more and more consistent across the board, yes proper cross browser support of more and more features, behaving the same way. Even the newer releases from IE. It is only the old IE-versions which are the biggest problems.
Also if you look at the HTML5 standard it now defines how bad HTML should be handled.
They have described very clearly how the parsing of HTML should be handled and how it should fail.
Opera, Firefox, Webkit: so Safari and Chrome all have got a HTML5 parser in that order, IE10 supposedly has one too. I haven't looked at that part at it yet though.
Really I don't think desktop market share of Firefox in the last few years matters all that much for mobile OS development. They share in the desktop market is big enough that many recognise the name.
They have backing from some large telcos in certain countries, we'll have to see if Mozilla and other developers can deliver.
If they do they'll have a cheaper phone with similair functionality than what others are delivering.
This is more about encrypting your data in the client and storing data encrypted on the server. So when a server compromise happends your data can't be easily stolen.
Which allows for more control on where code should be loaded from.
Actually I think having crypto as part of the browser is a bigger chance of success then just implementing the crypto in Javascript as some people clearly have already done. You don't want to implement a cryptographically secure pseudorandom number generator in Javascript it will never be secure.
Maybe the local generation is slightly more expensive than the grid. So you run that most of the time, but you don't to pay for a backup system which is sitting idle. The grid is the backup system.
Here is a list of what works and does not work with CGN:
What NAT444 Breaks
We are left with a number of applications (and application types) that currently break when Large Scale NAT is introduced. To avoid the doom and gloom feeling that is sure to follow a list of just the broken stuff, let’s start with a list of what isn’t broken by NAT444/LSN:
Web browsing
Email
FTP download
Small files
BitTorrent and Limewire
Leeching (download)
Skype video and voice calls
Instant messaging
Facebook and Twitter chat
Not too shabby really, all things considered. That is quite a bit of functionality for being behind a fairly large kludge. If that were the end of the story I wouldn’t have written this article though. So, without further adieu, here is the list you’ve been waiting for; what NAT444 breaks:
FTP download
Large files
BitTorrent and Limewire
Seeding (upload)
On-line gaming
Xbox
PlayStation
Etc.
Video streaming
Hulu
Netflix
Slingcatcher
Etc.
Webcam
Remote viewing
Tunneling
6to4
Teredo
Etc.
VPN & Encryption
IPSec
SSL
VoIP
Limited ALG/SIP support
All custom applications with the IP embedded
Lack of ALGs
Wow, is it just me or is that list a bit longer? There’s that doom and gloom feeling creeping up.
In Firefox 15 (the current version) already added support for Opus.
Opus is one of the 2 audio codecs which are mandatory-to-implement if a browser wants to support WebRTC (real time communication: video chat, voip from the browser and all that jazz).
Telco's are following at WebRTC really closely, some see it as an oppertunity. Other probably not.
So your smartphone might be getting support for it soon.
So will your fancy TV in the near future include a browser ? And a webcam (some already do) ? And because of it also support WebRTC ?
Pretty much every browser will probably support Opus, because the IETF WebRTC working group (real time communication like video chat) has made Opus it mandatory to implement for their specification.
As every mobile device, tv and desktop in the near future probably includes a browser... I think many devices will support it.
That is because Opus is still very new and any browser which wants to support WebRTC will need to support Opus, because Opus is mandatory-to-implement (real time communication: think video-streaming and voice calls and lots of other applications. Also includes peer2peer connection support between browsers with NAT-traversal and encryption).
But did you know you can download Skype with one of the two codecs on which Opus is based on and that it also includes WebM video ?
Yes, I missed that link the first time I watched it, thanks.
In the comments it says:
"the vast majority of these gotchas have been solved with SQL_MODE in MySQL 5.0. The SQL_MODE must be set in your configuration file once in then you're done."
Slashdot Mirror
I believe these devices are called "Otoro", because that is what it says on this page:
"Otoro
Otoro is a phone being used as a test and development platform as a low-to-midrange smartphone. Most core Firefox OS developers are working on Otoro."
https://developer.mozilla.org/en-US/docs/Mozilla/Boot_to_Gecko/B2G_build_prerequisites
Actually, you might not have noticed, but if you follow the rules then the last few years browsers have become more and more consistent across the board, yes proper cross browser support of more and more features, behaving the same way. Even the newer releases from IE. It is only the old IE-versions which are the biggest problems.
Also if you look at the HTML5 standard it now defines how bad HTML should be handled.
They have described very clearly how the parsing of HTML should be handled and how it should fail.
Opera, Firefox, Webkit: so Safari and Chrome all have got a HTML5 parser in that order, IE10 supposedly has one too. I haven't looked at that part at it yet though.
Really I don't think desktop market share of Firefox in the last few years matters all that much for mobile OS development. They share in the desktop market is big enough that many recognise the name.
They have backing from some large telcos in certain countries, we'll have to see if Mozilla and other developers can deliver.
If they do they'll have a cheaper phone with similair functionality than what others are delivering.
Then they might have a chance.
Even the page you pointed to has Chrome listed as supporting it.
Also Firefox will be rolling it out soon, as they are busy implementing WebRTC.
IE seems to be interrested in supporting WebRTC too, so they'll have to roll it out too.
And Apple is usually very quiet about what they will.
Yes and they check the faces against a database supplied by the US-authorities.
But I believe the image services of Yahoo, Bing and Google do the same.
These people are just being alarmist.
You can even do targetted ads without tracking:
https://air.mozilla.org/tracking-not-required/
And learning Python is also something you in a browser:
http://www.pythontutor.com/
This is more about encrypting your data in the client and storing data encrypted on the server. So when a server compromise happends your data can't be easily stolen.
I believe both Firefox and Chrome have support for:
http://www.w3.org/TR/CSP/
Which allows for more control on where code should be loaded from.
Actually I think having crypto as part of the browser is a bigger chance of success then just implementing the crypto in Javascript as some people clearly have already done. You don't want to implement a cryptographically secure pseudorandom number generator in Javascript it will never be secure.
I'm just waiting for bcache to be stable and part of the mainline Linux kernel.
That solves the problem if you ask me.
My guess is the 'TCO' is less ?
Maybe the local generation is slightly more expensive than the grid. So you run that most of the time, but you don't to pay for a backup system which is sitting idle. The grid is the backup system.
That is easy to explain, because in most cases you need to fight with, euh against, the software to do what you need it to do anyway.
If the existing product fits perfect for your needs, in that case it doesn't matter. But most organisations need software to fit their process.
OSS code just allows you to do it your way, you could ask/pay the vendor to change their code but that is an extra cost.
No, they will probably be selling them to the highest bidder.
Here is a list of what works and does not work with CGN:
What NAT444 Breaks
We are left with a number of applications (and application types) that currently break when Large Scale NAT is introduced. To avoid the doom and gloom feeling that is sure to follow a list of just the broken stuff, let’s start with a list of what isn’t broken by NAT444/LSN:
Web browsing
Email
FTP download
Small files
BitTorrent and Limewire
Leeching (download)
Skype video and voice calls
Instant messaging
Facebook and Twitter chat
Not too shabby really, all things considered. That is quite a bit of functionality for being behind a fairly large kludge. If that were the end of the story I wouldn’t have written this article though. So, without further adieu, here is the list you’ve been waiting for; what NAT444 breaks:
FTP download
Large files
BitTorrent and Limewire
Seeding (upload)
On-line gaming
Xbox
PlayStation
Etc.
Video streaming
Hulu
Netflix
Slingcatcher
Etc.
Webcam
Remote viewing
Tunneling
6to4
Teredo
Etc.
VPN & Encryption
IPSec
SSL
VoIP
Limited ALG/SIP support
All custom applications with the IP embedded
Lack of ALGs
Wow, is it just me or is that list a bit longer? There’s that doom and gloom feeling creeping up.
http://chrisgrundemann.com/index.php/2011/nat444-cgn-lsn-breaks/
Install an HTTP-proxy-server on the edge (a lot of those organisations already have one) and add IPv6 to that.
Done ?
Business of buying and selling of IPv4-addresses, you mean ?:
http://addrex.net/
http://tradeipv4.com/
http://www.ipaddressbroker.net/
But all it will do is slow down adoption:
http://it.slashdot.org/story/12/07/18/1852243/sale-of-ipv4-addresses-hindering-ipv6-adoption
https://ripe64.ripe.net/archives/video/28/
https://ripe64.ripe.net/presentations/24-2012-04-16-internet-futures-a.pdf
So what Intel has is "good enough" for 99.9% of the users, but AMD delivers the same thing but for less money ?
In Firefox 15 (the current version) already added support for Opus.
Opus is one of the 2 audio codecs which are mandatory-to-implement if a browser wants to support WebRTC (real time communication: video chat, voip from the browser and all that jazz).
Telco's are following at WebRTC really closely, some see it as an oppertunity. Other probably not.
So your smartphone might be getting support for it soon.
So will your fancy TV in the near future include a browser ? And a webcam (some already do) ? And because of it also support WebRTC ?
Pretty much every browser will probably support Opus, because the IETF WebRTC working group (real time communication like video chat) has made Opus it mandatory to implement for their specification.
As every mobile device, tv and desktop in the near future probably includes a browser... I think many devices will support it.
That is because Opus is still very new and any browser which wants to support WebRTC will need to support Opus, because Opus is mandatory-to-implement (real time communication: think video-streaming and voice calls and lots of other applications. Also includes peer2peer connection support between browsers with NAT-traversal and encryption).
But did you know you can download Skype with one of the two codecs on which Opus is based on and that it also includes WebM video ?
You might want to watch, euh listen, to the demo:
https://www.youtube.com/watch?v=iaAD71h9gDU#t=28m03s
I thought it was pretty impressive.
There is a lot of detail in the talk about Opus if you want to know more about it.
Yes, I missed that link the first time I watched it, thanks.
In the comments it says:
"the vast majority of these gotchas have been solved with SQL_MODE in MySQL 5.0. The SQL_MODE must be set in your configuration file once in then you're done."
So that's also interresting to know.
I believe they both improved.
PostgreSQL 7.x wasn't as much fun either which didn't have autovacuum and needed a lot of tuning.
I haven't tried something like Drizzle but it seems they ditched a lot of old code and problems.
Lots of people such, but it is just hard to trust your data to MySQL. Just a moment ago I posted a link above to this video which illustrates it:
http://www.youtube.com/watch?v=1PoFIohBSM4
MySQL has some nice replication built in I believe, I've never used them.
Other than that, I would thread lightly with MySQL:
"Why not MySQL"
http://www.youtube.com/watch?v=1PoFIohBSM4