365 karma · joined June 9, 2011
My Bitrated profile: https://www.bitrated.com/simondlr/
But what happens to the mining reward, I don't know. Anyone?
To me that means 2 things: seeking out and creating opportunities. Build stuff, meet people, take risks and chances. This increases the chances of opportunities (luck) happening: Meeting that perfect co-founder, stumbling onto a brilliant idea, finding the right investors, etc.
Then secondly, you have to practice to be open-minded enough to realise that when an opportunity actually arrives, you know it is one! You might seek and create opportunities as much you want, as most of it ends up being luck, but if you don't realise that luck, you've missed the boat.
1) Halving of supply. Block rewards halved end of 2012. 2) SatoshiDice continues to become more popular. 3) Big names supporting it: Reddit, Mega, Namecheap. 4) Along with the above that would bring about a general rise in prices, is the speculators that will try to game it.
My bet is there will be a correction again soon.
Going to be interesting to see what happens, especially due to Y-Combinator being rather a unique case in this regard.
Soon after the security of the listserv was fixed.
Sell a piece of land a few kilometres in for a lot of money, citing it's major benefit as future beachfront property (put ads in local paper, etc). If anyone actually decides to buy it at that price, cover your losses and donate the rest to WWF or Charity:Water.
Currently, I'm okay in paying $50 to get access to a great community of early adopters (lets admit, it is mostly tech people). I'm not naive to expect it won't change, but once killer apps start popping up on the ecosystem, more users will join which will bring back the value that the older social networks provided.
As a developer, I'm a lot more excited about it. I backed mainly because I was so excited about an API that could've been what Twitter promised. I'm especially excited to see what annotations is going to emerge through it. To explain it in short: Any app can now embed any information in a post. This is big. To give a small example: Say people who allow IFTTT to post their music to app.net. IFTTT can decided to add meta information to it (adding song titles, artists, etc). Now anyone else can easily extract this information.
There is a whole underlying network waiting to be discovered. Anything can now live within in it. What if you wanted to do an instagram type app? Ask users with app.net accounts to log in. When they post a photo, add your own information to it (photo title, photo url, etc).
In the normal app.net (alpha) interface, you won't miss anything. You'll just see someone posting a photo. However, now this new instagram type app can extract this information from a user's feed, using app.net's infrastructure as their social backbone! Any social service can live on app.net's infrastructure now.
New users that join once critical mass has been reached, will be able to create their own graph and enjoy the social network in question equally to when a person joined it 4 years ago (given the site is still the same in terms of functionality). However, the person that joined 4 years will become bogged by an ever increasing graph of connections to pages, friends, groups, history etc that eventually undermine what made the site relevant to them in the first place (ie Dalton's experience with Orkut).
So, just as in the real life, social relationships come and ago, a natural decay has to happen that allows a person's graph to remain relavent. Currently Facebook (and to a certain Google+) are doing it right. They filter. Heavily. If you don't interact with the people from 4 years ago, you just don't see them anymore on it.
I liked juxtaposition between the room being overwhelmed with virtual items, but in real life actually being rather empty and dull.
The most interesting challenge about these interfaces is the question of UX and norms. For mainstream adoption, the interface is going to be the most interesting facet.
ie, with scan, although more resource expensive than query, you can add filters on any keys, but you can't sort any of the data. With query you can, but only on the range key you specify, which is 1 per table. Also: it can't be changed after the table is created.
Seems like difficult problems to sort out for an ORM wrapper.