jeeceebees

By this logic no photographer is an artist either. They just 'selected' a composition they liked. They didn't work to create any of their subjects, just walked up and took a picture.

Slowly coaxing a desired result out of a computer by painstakingly tweaking an algorithm over the course of hours or days doesn't sound like work to you? The computer wouldn't have just done it on its own if an artist didn't tell it what to do.

I think your definition of art is narrow-minded. Who are you to tell someone their work isn't art. Art is (and always has been) in the eye of the beholder.

The contract code is immutable. The code that you agree to can be pretty complicated though and might not do exactly what you think it does.

In this case, by some stupid mistake the contract allowed anyone at all to change who was considered an owner of a wallet.

The code wasn't changed; one of the functions it specified was used to change a variable.

The exploit allowed anyone to reinitialize a multisig contract with themselves as an owner because the constructor was a public function. These contracts weren't "fixed" like they were supposed to be.

The white hats will deploy a new contract without the faulty constructor with the old owners reinstated. These newly deployed contracts will have all the same information the old ones did but won't be exploitable.

Just a couple months ago geth clients were crashing due to a memory overload, the fix? Use parity until geth was patched.

Using core implementations is no guaruntee that you won't get burned. The only difference between official software and third party open source software is the dev team behind it. The official devs can make mostakes just like anyone else.

What kind of QOS adjustments would be made impossible by assuming the above definition of net neutrality?

Genuinely curious.

Wouldn't this imply that all hash functions (other than one-to-one mappings) must have collisions?

Why does the pigeonhole principle hold?

Another integration I'd like to see is with Facebook events. Really the only reason I have a Facebook account is to keep track of concerts I'm going to. All the info and tickets are in the same place and I can follow certain events / groups and get notifications when new concerts pop up. If the events I'm "going" to could automatically be added to my Showlist I'd be completely sold!

Also I've noticed that this is geared toward there being 1 artist/band at each show. This might be different for different genres, but here in NL the Drum & Bass scene has like 5-6 names playing at each event so it is a bit tedious to have to enter each one manually. Again I think Facebook event integration would be a great solution to this issue because the official events have all the information about the concert if you can manage to recognize the relevant information in each post.

I think Facebook probably has the most complete summary of events across all genres if you can find a way to parse out the non-concert related events. This is probably pretty hard to implement well, but might work out with a smart enough spider crawling Facebook.

https://showlist.io/@JeeCeeBees :)

I think one of the important things is that people have learned the need for backups in smart contracts. There will always be bugs, but if people build in failsafes to catch them then situations like the DAO draining can be avoided.

Here's a nice post about schemes for fault tolerance: https://medium.com/@peterborah/we-need-fault-tolerant-smart-...

IPFS works over tor! The implementation is pretty rudimentary at this point, though.

I guess the main issue is actually distributing the tracker.

I think very many IPFS use cases do need / benefit from blockchains.

The future is an IPFS mirror where the entire magnet list and web frontend are peer to peer. When everyone can host the site individually on their own computer there won't be a way for authorities to seize servers or domains.