The first thing that will happen immediately is that when you install your new Windows Anti-Virus software the vendor will implement their own and just add their notary to the list.
Let me guess the OEM will add it's own notary as well ?
This all seems like a bad idea.
I don't know, maybe I'm just in a negative mood:-)
Forgot about that, you can turn off the cache. I don't currently use it, I was actually looking at the source on github.:-)
Anyway, I keep wondering how it will scale in general, like how would the general public who knows nothing about these settings and how it works or how to use it.
For example let's say you have many, many people using the same notary as a default in the browser, you could never ever turn it off.
Here is a rundown of what it looks like: Step 1: someone has an idea Step 2: a possible API is discussed on the w3c mailinglist Step 3: an API is drafted Step 4: 1 or 2 browsermakers implement it in their browser, do use a 'vendor' prefix Step 5: people look at how well it works, discuss it on the w3c mailinglist. Step 6: Webpage authors are encouraged to try it out (and use it in production) with the vendor prefix. Step 7: proposals for a standard are made Step 8: I think people vote on it Step 9: standards are approved and it is a standard. An actually "industry standard" too. Because pretty much everyone agrees on the standard. Step 10: browser vendors change their browsers and people can use it without the browser-prefix
I'm sure sometimes step 2 and/or step 3 are skipped.
You can see a video of a coneference which explains it in detail:
Summary: browsers implement what they want and when everyone agrees about the API it .
While the process looks kind of weird from the outside. But the idea is that what becomes the standard should be stable, so it can be set in stone and works like everyone wants.
They are probably just using some kind of dummy corporation.
They don't get them from a hosting provider, they buy them and route it themselfs. They are their own hosting provider. Like any ISP would do with their own IP-block.
I'm sure it is possible to find at least a few cases where it might be the cause.
But that doesn't justify stopping with vaccines.
The vaccines safe a lot of lives.
If there is one thing people can do is to find a gen which helps predict the cause of these cases and test for the gen before vaccination.
Re:The big issue is lots of people are being repla
on
The Cult of DevOps
·
· Score: 1
It could also be that we end up being a lot more effective. That is after all the whole point of IT. I've never made much sence to me why people did the 'manual labor' in IT.
But if I look at education in my home country: the Netherlands in Europe, I can tell you there aren't even enough people studing programming to fulfill the available positions (well, I don't know the real numbers, but that is what they keep telling us in the local IT-press and looking at the people that get hired I'm not all that surprised).
So maybe there is room for people to be retrained.
I don't know, we'll see.
Re:The big issue is lots of people are being repla
on
The Cult of DevOps
·
· Score: 1
Personally I think the biggest problem with browsers like IE9 and Chrome is, their timeout settings are so short that pages don't even always load properly.
It doesn't say how they test though. All it says is 'load 40 tabs', not how many times they did that and if they cleared the browser cache and so on like DNS-cache.
Re:The big issue is lots of people are being repla
on
The Cult of DevOps
·
· Score: 1
I don't want to be an asshole.
But if you don't adapt, you might loose your job. Especially in IT.
Now that I think about, getting back to what the article is about.
I think the point of the article is: know the environment where your code gets deployed and have some idea of how it will probably get used and actually monitor that so you can better adjust.
An other thing I got from the article is that this does not really fit with the idea of cloud computing.
Most people would have no idea how the environment looks where their code will run if it 'runs in the cloud'.
You can not predict everything and you can't generate all possible testloads.
There is always friction between: - adding features - lowering operational expenses - trying to predict what part will fail first under load, increasing scalability - deploying quick fixes because you did not anticipate something - deploying real fixes for quick fixes
I read the article, I think the title is basically talking about:
'he thinks Google gets this right. “We go to great lengths to hire people with engineering skills, put engineers in operational roles and give them power and accountability."'
Don't expect Microsoft to do things for technical reasons.
I think it might be something like this: 1. Because it is something they can tick on the list of hype. Lots of hype around HTML5. 2. Because it appeals to a different kind of developer and they want to lock them in too. 3. Because they can tell people they support a platform-independent system.
Slashdot Mirror
Something like:
"RFC 5006 - IPv6 Router Advertisement Option for DNS Configuration"
Does not work for you ?
I know on Debian based distributions you can install 'rdnssd' for that.
Actually quite a few people make their living on YouTube. For some it is their only job. Many of them life in L.A.
Just look up YouTube Partner program. These are people who get a large cut from the ad revenue of the ads on the videos they produce.
Obviously thse are people who get millions of views and produce new videos atleast 2 times a week.
Something else I'm thinking.
If this gets introduced to the general public.
The first thing that will happen immediately is that when you install your new Windows Anti-Virus software the vendor will implement their own and just add their notary to the list.
Let me guess the OEM will add it's own notary as well ?
This all seems like a bad idea.
I don't know, maybe I'm just in a negative mood :-)
Forgot about that, you can turn off the cache. I don't currently use it, I was actually looking at the source on github. :-)
Anyway, I keep wondering how it will scale in general, like how would the general public who knows nothing about these settings and how it works or how to use it.
For example let's say you have many, many people using the same notary as a default in the browser, you could never ever turn it off.
No revocation lists are usually huge, like 200MB+ so pretty much useless.
But you don't need a revocation list to revoke a certificate in any moden browser. It usually supports OCSP.
I believe browsers don't cache OCSP-responses longer than the browsing session (for as long as the browser is open) ?
So if you enable "When an OCSP server connection fails, treat the connection as invalid" you will be 'safe'.
Next time you start the browser OCSP is checked, thus if the certificate is revoked you would get a proper error.
I would have liked it more if the notaries are checked more often, instead of just ones per certificate (thus: ones and never again) as it is now.
Which obviously might be a scalability problem.
While I really like the concept, I'm not sure how well this will work in practise scale.
The thing I like least about it is that it caches known certs for as long as the cert is valid.
How do people revoke certs of compromised keys in that model ?
So tell me how does am access provider get a cert signed for a site/domain they don't host.
If you really, really do want it.
You can help write the draft, it costs nothing to join the w3c mailinglists.
Yes, let's port the JVM to nodejs. So you can run Java on the server.. ;-)
You misunderstand the process and many do.
Here is a rundown of what it looks like:
Step 1: someone has an idea
Step 2: a possible API is discussed on the w3c mailinglist
Step 3: an API is drafted
Step 4: 1 or 2 browsermakers implement it in their browser, do use a 'vendor' prefix
Step 5: people look at how well it works, discuss it on the w3c mailinglist.
Step 6: Webpage authors are encouraged to try it out (and use it in production) with the vendor prefix.
Step 7: proposals for a standard are made
Step 8: I think people vote on it
Step 9: standards are approved and it is a standard. An actually "industry standard" too. Because pretty much everyone agrees on the standard.
Step 10: browser vendors change their browsers and people can use it without the browser-prefix
I'm sure sometimes step 2 and/or step 3 are skipped.
You can see a video of a coneference which explains it in detail:
http://vimeo.com/16326857 from 20:36 till 32:00
Summary: browsers implement what they want and when everyone agrees about the API it .
While the process looks kind of weird from the outside. But the idea is that what becomes the standard should be stable, so it can be set in stone and works like everyone wants.
People are already doing that, by running piping the results from kinect to nodejs and have the webinterface use nodejs as it's server:
http://www.youtube.com/watch?v=UMBWYBH3TKg
This has no demo, but read the text and see the result:
http://kinect.dashhacks.com/kinect-news/2011/07/12/kinect-web-animation-using-html5-and-animatable
http://typefolly.com/css-tricks/
An other:
http://www.youtube.com/watch?feature=player_embedded&v=p36xoBZVQ8c
While there is such a thing as a "legitimate trading and auction sites,"
While I'm not aware of any auction sites, I do believe it is possible to do trading in Asia/Pacific region:
"APNIC transfer, merger, acquisition, and takeover policy"
http://www.apnic.net/policy/transfer-policy
Which came from this:
"prop-050: IPv4 address transfers"
"Current status Implemented on 10 February 2010"
http://www.apnic.net/policy/proposals/prop-050
And I know there is a proposal for doing simialir things in Europe:
"Post-depletion IPv4 address recycling"
"Current Phase:
Concluding Phase: Awaiting Decision from Working Group Chairs"
http://www.ripe.net/ripe/policies/proposals/2011-03
They are probably just using some kind of dummy corporation.
They don't get them from a hosting provider, they buy them and route it themselfs. They are their own hosting provider. Like any ISP would do with their own IP-block.
Aww, do these youngsters not have Google or Bing ? ;-)
Here, to make it easier:
http://en.wikipedia.org/wiki/NO_CARRIER
Do you think the joke works better with "disconnected by peer" ?
I'm sure it is possible to find at least a few cases where it might be the cause.
But that doesn't justify stopping with vaccines.
The vaccines safe a lot of lives.
If there is one thing people can do is to find a gen which helps predict the cause of these cases and test for the gen before vaccination.
It could also be that we end up being a lot more effective. That is after all the whole point of IT. I've never made much sence to me why people did the 'manual labor' in IT.
But if I look at education in my home country: the Netherlands in Europe, I can tell you there aren't even enough people studing programming to fulfill the available positions (well, I don't know the real numbers, but that is what they keep telling us in the local IT-press and looking at the people that get hired I'm not all that surprised).
So maybe there is room for people to be retrained.
I don't know, we'll see.
Sorry, English is not my first language
Sure it can.
Personally I think the biggest problem with browsers like IE9 and Chrome is, their timeout settings are so short that pages don't even always load properly.
If you look at the article, you'll see problems with that:
http://www.tomshardware.com/reviews/firefox-7-web-browser,3037-13.html
http://www.tomshardware.com/reviews/web-browser-performance-standard-html5,3013-13.html
Firefox did better, although slipping ?
It doesn't say how they test though. All it says is 'load 40 tabs', not how many times they did that and if they cleared the browser cache and so on like DNS-cache.
I don't want to be an asshole.
But if you don't adapt, you might loose your job. Especially in IT.
Is that something people are surprised about ?
Probably uses the same type of batteries as the iDevices too ;-)
It is a website. They changed it so that the website depends on a not-widely deployed plugin.
That really should not be needed, people can just use open standards HTML/JS/CSS.
Now that I think about, getting back to what the article is about.
I think the point of the article is: know the environment where your code gets deployed and have some idea of how it will probably get used and actually monitor that so you can better adjust.
An other thing I got from the article is that this does not really fit with the idea of cloud computing.
Most people would have no idea how the environment looks where their code will run if it 'runs in the cloud'.
These problems will always exists.
You can not predict everything and you can't generate all possible testloads.
There is always friction between:
- adding features
- lowering operational expenses
- trying to predict what part will fail first under load, increasing scalability
- deploying quick fixes because you did not anticipate something
- deploying real fixes for quick fixes
I could be wrong of course :-)
I read the article, I think the title is basically talking about:
'he thinks Google gets this right. “We go to great lengths to hire people with engineering skills, put engineers in operational roles and give them power and accountability."'
Don't expect Microsoft to do things for technical reasons.
I think it might be something like this:
1. Because it is something they can tick on the list of hype. Lots of hype around HTML5.
2. Because it appeals to a different kind of developer and they want to lock them in too.
3. Because they can tell people they support a platform-independent system.