1,389 karma · joined September 11, 2008
Like nullc my interest is in the area of types being used to enforce contracts and safetly (hence my interest in the ATS language).
Typesafe was my initial interest in Rust and I'd love to see examples of how this is being approached in Rust as it is now.
This means that sites that control playback speed using the HTML media API should work.
For detection sites should use the API "canPlayType" and similar functionality to detect if the browser supports playback.
- support for Linux via GStreamer landed but not built by default. It needs a bit more work.
- support for Windows 7 and above which the OP post is about
- Mac OS X is not yet underway but is planned.
- Hardware H.264 decoding on Android phones via libstagefright. Some phones supported and enabled by default. Some supported but disabled at the moment. Some unsupported.
- Hardware H.264 decoding on Firefox OS/B2G enabled by default, implemented via libstagefright. Phone vendors provide the binary blobs to do the decoding.
[1] http://www.vitanuova.com/inferno/ [2] http://www.bluishcoder.co.nz/2012/06/11/building-inferno-os-...
An example github issue discussing problems encountered: https://github.com/mozilla/rust/issues/1105
There's "PPCoin", a fork that adds "Proof of Stake" alongside "Proof of Work" in an attempt to reduce the energy consumption of the mining process.
There's others as well. Some bitcoin proponents consider these "scam" coins as they have limited use other than speculation, others consider them experiments in different approaches. But they do show that forking bitcoin is fairly easy.
Hard to believe they only had 25 million documents indexed then.
There's no "many sums to calculate" contributing towards a result. It's more a lottery - did my one calculation produce the right number.
If you could convince others to run your client then your network would get bigger. If it got >50% of the entire network then your blockchain would effectively be the main chain.
Since all clients implement the same algorithm, they all get the same difficulty value.
Metabug for Android decoding support: https://bugzilla.mozilla.org/show_bug.cgi?id=755364
Hardware decoding support using libstagefright on B2G: https://bugzilla.mozilla.org/show_bug.cgi?id=759506
In the case of desktop Mozilla could take the same approach (use system libraries, expect OS supplier to provide licensed decoders) but some platforms would miss out on support if the OS supplier doesn't provide the decoders.