With recent Bitcoin coverage in the news and media, I’ve picked up playing around with it again. One thing that came to mind was something that would make it easier to make payments to addresses found on the web. My first thought was doing the same thing as a MailTo link on the web, click the link and the client opens up with the details in place. Granted copying and pasting the address isn’t that big of a deal, but this makes it easier to send or donate to a website.
Now I have to be honest I wasn’t sure what the correct name for the MailTo link was called. One quick Google search led me to the MailTo URI Scheme Wikipedia page. Another Google search for “Bitcoin URI Scheme” led me to this page with a technical write up of a URI Scheme for sending Bitcoin payments. Lo and behold, the samples on that page work just like I’d expect by opening the local client on my computer with the address filled in. The only problem I can see is that most sites aren’t using this already. I would imagine that this would be a no brainer, where anything that makes it easier to send you money is always a good idea. So here’s my plea to other sites to add the code needed for the bitcoin link.
Just in case anyone needs a refresher, it’s done with the <a> tag and in it’s simplest form would look like this.
<a href="bitcoin:PutPaymentAddressHere">Link text goes here</a>
[googleplusauthor]
So I’m working on a project at work to evaluate and implement a source control system to replace a fairly non-existent use of Visual SourceSafe. It has been a while since I’ve looked really in depth at any version control software and I have to say that I’m impressed with the advancements around them. Not necessarily in the version control systems specifically, but in a lot of the auxiliary functionality that they can offer either natively or as with easy add-on. Things like automated builds and continuous integration are things that weren’t even on the map last time I looked at this in any depth.
At my work we decided to evaluate three types of version control; Team Foundation Server (TFS), Subversion, and Git. I’m most familiar with Subversion since that’s what I’ve used in the past and TFS is a fairly obvious choice for us since we are mostly a Microsoft shop with the tools we use. Git however was a bit of a research project for me and I have to say that we fairly quickly decided that it wasn’t for us. Don’t get me wrong it has it’s use cases where it shines, particularly in development environments where the development team is widely dispersed geographically and not necessarily always network connected. In these cases Git seems really ideal which is probably why it has taken off and is so popular in open source projects, but this is completely different from our primary development environment and the downsides outweigh these benefits.
I don’t know which way we’ll end up going at my job. We’re wanting something simple that will be easy to use and we’re just implementing source control as part of the project. This is why I’m starting to think that we might go with Subversion because TFS can be such a bear to administrate and after getting them installed and starting to set them up, I can understand.
[googleplusauthor]
Instructions for DIY Projects and Technology Chatter