mwilcox

They have chips dedicated to video encoding/decoding with the latest cards doing h265. Nvidia has an ffmpeg patch here https://developer.nvidia.com/ffmpeg

It's more similar to Blockstack: https://blockstack.org

Not quite. Ethereum's trie allows transaction paths like this to be clipped with almost no collateral damage to the rest of the data structure. Bitcoin's UTXO model makes it very difficult to roll back transactions since it would cause havoc on every other transaction on the network.

The generic privacy policy along with the free price concerns me. What is their plan for monetisation?

It's a reference to 21 million - Bitcoin's issuance limit

I believe Halide is limited to 2-dimensional (Image Processing) use cases? Either way, it's designed to make it easier to find optimal parallel implementations rather than write code that can fluidly execute across a CPU and GPU.

Yes tumbling is much more secure if your goal is to anonymise your money. MML is much more easily traceable as you just look at the guy who mined the block and send the authorities to go and speak with him. Especially if the large mining operations are well known.

The usefulness to a launderer seems more the simplicity of exchanging a large amount of coins for fiat currency in a single transaction, rather than going through an exchange or sending lots of complex small transactions through a mixer and figuring out how to exchange all of that back without going through an exchange w/ KYC

Ethereum gets a mention :-)

It's all based on the same book (Connectography). I highly recommend instead reading The Stack that just came out from MIT Press, which gives a much deeper analysis on the relationship between cities, software and geopolitics: http://thestack.org

I'd say those are features of agent-based systems as opposed to problems. But it depends on the application

Most of the application does not run on ethereum itself, but on the client. It's the business logic that does. User registration, transactions, etc. So it depends how resource intensive the business logic is.

They have a pretty good shot at owning customer relationships and becoming a channel for that structured data (a market sites can sell data through) if that does become the case

FLIF is based on context mixing so it's extremely slow but has an extremely high (lossless) compression ratio. It's designed for image archival and not for real-time streaming video. It does have some interlacing techniques for previewing the image in a lower resolution but really it's orders of magnitude slower than other image formats.

We already have one: Hacker News

Where does the money come from?

For disk, sure, but not for Flash / NVM

It's similar to the strategy they're running on Web Components with Polymer: http://polymer-project.org.

They have a number of Material Design web components that are very easy to integrate into your site but also more difficult for people to override.

Github is having issues at the moment https://status.github.com/

You would have to create a new contract, and broadcast to people that they should use the other contract. All these systems heavily rely on decentralised reputation - not just for users but for contracts as well.

depth sensors

The low expected production run for a custom handware development kit would be what drives the price up.

It's not actual blockchains they're finding useful. It's the reasonably robust framework that people are building around it, where they get a whole lot for free and just need to optimise that annoying blockchain bit in the middle. Rather than do all of the crypto, security R&D they would need to do by not using 'blockchain technology' they just turn off the mining and get it all for free.

the guide for bcache mentioned raid/erasure coding isn't implemented yet - anyone know if that is up to date and/or when it could be expected to be integrated?

Magic Leap?

It's called a 'SaaS marketplace' or 'API marketplace'

Yep. Godsend in comparison to AMD drivers

Xbox One literally runs Windows

"Public Cloud" and "Private Cloud" are pretty standard industry terms for using the same orchestration systems on your own data center vs. an outsourced one.

They're over their bandwidth. On a standard connection:

> The requested website is temporarily not available due to a resource limitation. The most common reasons for this are: