The IRC channel I'm in most of the time has a karma system.
#pdxtech:someone> donpdonp++ #pdxtech:karmabot> donpdonp has 13 karma
With the rise of dogecoin, its a useful experimentation platform. There are way more coins and they cost next to nothing so its simple to experiment with micropayments in whole.
The giving of karma remains the same. A new bot talks to a dogecoind process to get the pool total and issue payments. There are a variety of systems to allocate payment. What I am going with is to calculate each user's karma percentage of the total, then use that percentage against a daily payout total.
Karma is payed out every night, also if a payment happens, that user's karma is cut in half. The goal is to provide some kick-back for a short amount of time, then reduce to zero until the next karma is earned.
LittleBird. Rails contracting.Apr/ May / Jun/ Jul/ Aug/ Sep
CoinThink scripting.Nov/ Dec
- temp <wunderground station name>
display the last temperature reading for this station. also monitors the temp of a default portland station every 10 minutes and alerts when the temperature goes below freezing. also remember last-used station on a per-user basis to report the best station for that user with just 'temp'.
- noaa <zone name>
display any published alerts for this zone
- temp <wunderground station name>
coindesk pulls in the rss feed via this handy google rss to json service
watches the mtgox price for swings larger than 5% inside 60 minutes (10 min poll)
query the spacepeople api every 10 minutes for changes to the list of people in space
monitor the github status json url and publish any change notices
search calagator for matching events
monitor the conversation for long urls and post a shortened one via is.gd
You receive an unexpected, non-descript box in the mail.
In the box is a card and a set of instructions that enable membership in a special group of coders. Coders that work around the world and are backed by a foundation that allows for travel and project experimentation.
The card is a creditcard sized device with 'codename' on the front. An embedded NFC chip holds an encryption key. The instruction sheet has a URL that will load an Android app which can read the card and use the key.
One of the instruction steps is to order a debit card from the Google Wallet service. Deposits to your wallet from the foundation enable you to work from remote locations by paying for airfare, lodging, and food.
In the most official act yet for cointhink.com, a post was made to the bitcointalk forums. This is the culmination of 7 months of effort on this project. Cointhink was built to bring automation to bitcoin market customers. A variety of trading algorithms can be evaluated based on profitability using live market data (MtGox).
After given each script an initial purse and implementing simulated trades, the next logical step was a leaderboard. This adds an element of gamification to the scripts. The best-performing scripts show up at the top of the leaderboard. The usual BTC/USD arbitrage chart is still there, too.
In July 2011, I started an irc bot (donpdonp/neuronirc) because irc provides a simple yet powerful human-to-human and human-to-computer interface. It was built on the principle of loosely coupled, coordinated processes.
The foundation of the coordination is the redis pub/sub mechanism. Messages encoded in JSON are sent over pub/sub channels to interested listeners. There is redis support for nearly every language, therefore an extension to the bot can exist in nearly any language even though the core of the bot is in ruby.
This setup was working well but didn't go quite far enough. While new functionality or 'modules' was now possible in any language, the creation of and launching of new modules required significant administrator intervention. The users or participants in the channel could surely contribute their own useful code to the irc bot and I wanted a way to capture those contributions easily, without administrator intervention
Users in an irc chatroom could now give code to the bot to extend its functionalities. I started to use it all the time because it was simple and fast to add a new command to the bot's inventory. Some script management commands were added to make it easier to list your scripts, delete one of them, and create a script from the contents of a url (usualy a github gist). Script complexity ranged from simple to complex.
Now that there are 20-something scripts inside the neuronbot (called zrobo on #pdxtech/freenode), I forget about scripts that I've wrote in the past. Many of them are periodically executing. That starts to feel like sci-fi. I can read and understand any single script, but the entire system is starting to grow beyond my ability to comprehend.
Scripts listen for messages and messages have types. Most often the type is a new line of text from an irc chatroom. That has a particular type. It was a huge leap forward when a new type of message started to be emitted once a minute. Thats a message indicating a change in time, which enables scripts to run periodically. This month scripts have the ability to emit their own messages. This lets complexity be distributed across multiple scripts. One script can be dedicated to monitoring a feed of some sort, such as the weather or a bitcoin marketplace. When conditions are right, a signal is emitted and another script can take action based on that.
Another area of exploration is to standardize the message format amongst different irc bots, and use an irc channel as a bus for messages between bots.
Modern websites are web services with an html front end. Web services need to be easy to manage and easy to scale. The variety of ways to architect these features is a never ending playground of possibilities. Below is a description of features and current thinking on how to achieve those features.
Easily scale up or down the group of virtual machines that provides the service. Any one server should be able to be removed without affecting the service. tool: libcloud Add more compute nodes programatically, even across different VPS providers.
Rather than handling an HTTP request, the request goes into a queue. Workers on different VMs pull jobs off the queue. Different VMs are united by access to a common distributed datastore. tools: redis, mozilla circus
The bitcoin blockchain experienced a fork due to a subtle bug in the pre-0.8 bitcoin app. The 0.8 version was being used by a majority of the miners. After it had been suggested to increase the maximum blocksize, a large block (#225430) was generated by miners on 0.8. This large block was not processable by pre-0.8 apps. There was a significant percentage of miners on pre-0.8 and that brings us to the first, and core problem - how pre-0.8 handled the error.
Fix 1) Block 225430 was a valid block. It was the error handling of the bitcoin client that caused the problem. The hash was valid for its contents and for its place in the blockchain. The client should have been able to verify that before iteration over the transactions. It was the number of transactions that causes bdb to fail. The client should be changed to compartmentalize an exception that happens after the validity of the block is determined. When this valid block caused an error in processing after validation, the client should treat that as an irrecoverable internal error. The pre-0.8 miners and clients would have shut down and the chain would not have forked.
Fix 2) It is my understanding that all the forks exist in each client's blockchain. If so, put up a large warning that a fork exists and things may not be what they seem. The greatest let-down of this blockchain fork event is that the great promise to merchants was invalidated. Since I've been using bitcoin, the mantra has been that after 3, and at most 6, confirmations, it was statistically impossible to get a false-positive on a transaction. Thats true for a single chain. The large, now infamous, payment made on the 0.8fork that was simply un-done out of thin air when the pre-0.8 chain achieved the most length, showed that iron-clad agreement to be false. If the app could warn the user of the existence of a fork, then they'd have a chance to investigate further.
The future makerspace/coworking place has a name: Base16. The word 'base' is a good description of the purpose of the place. Base 16 is a nice pun/computer reference to hexidecimal.
Its primarily a coworking place. Software-development oriented. With space for the other exciting parts of the tech world currently - microcontrollers, 3d printers, quantified self projects, copter projects. It'll have a couple large dashboard displays. There will be jungle-gym features throughout the space. Movement such as pullups and climbing will be integrated into daily activity.