I know there have been severe problems with DNS (provided for free by http://xname.org) as well as web server overloads so I have finally setup deployment using Amazon’s S3 service for reliability and stability. The link on the download page has been updated to reflect that change. If you have a working copy of the download, it is not required that you uninstall and reinstall using that link, but it is recommended so that you automatically get future updates.
I would also like to note that as of now: http://xname.org DNS is now back in sync with all three of their DNS servers so my domains are routing correctly now. The plan is to eventually setup cname records to push out a new update (or two) with a seamless transition for user back to the install.rohankapoor.com install domain while still hosting on Amazon’s S3 platform. This should be seamless with an estimated 3 updates to the Custom Paper Deployment Tool. If you have not downloaded the new version since I changed the url, it is recommended that you do so, so as to not miss the updates.
Recently I’ve talked about a new tool I’ve released for Livescribe Smartpens, my Custom Paper Deployment Tool, which allows users (running Windows) to deploy any of my custom papers (and soon any other custom paper) to any Livescribe Smartpen now that the Development Program has officially ended and Livescribe will no longer support Custom Paper and third-party development.
I’ve noticed that many users are having problems connecting to the download page (http://install.rohankapoor.com) and have traced the problem with it. The DNS servers I use, run by http://xname.org are having a replication problem and the primary DNS server is serving the correct data while the secondary DNS server is serving incorrect data that is two months out of date. As far as I know, XName is aware of the problem and will hopefully have a fix soon. I’ve also noticed much higher load on my web-server as the download files are quite large and the demand is quite high.
The solution appears to be providing an alternate download location (which I will probably use Amazon’s S3 service for). Unfortunately, I am currently quite far from the my development computer and will be unable to modify the manifest file to change that location until I return. I can recommend trying to use Google’s DNS (126.96.36.199) until I am able to resolve this as it is bringing more accurate results. I apologize for the delay.
With the end of Livescribe’s Development Program, it is no longer possible for end users (or even developers) to download the SDK and deploy any of the numerous Custom Paper Products made by developers such as myself (among others). For a while now, I have been discussing the possibility of Livescribe creating and releasing a tool that installs third party Custom Paper Products to their smartpens. For various reasons, none of which will be discussed here, Livescribe did not release such a tool. I have been toying with the idea of building one myself for the last year, however I have not done so assuming that Livescribe will at some point do so. At this point, with Livescribe closing their Developer Program, it is obvious that they will not be releasing such a tool now.
The other reason I was hesitating with building this tool was that it would be coded in C# which I have had zero experience coding in before. I’m primarily a Java programmer with experience with both C++ and PHP (all of which use very similar syntax). Seeing no tool forthcoming from Livescribe and not wanting Custom Paper Products to be a product of the past (no pun intended), I finally dove right into it! I During this process, I learned that C# is nowhere near as complicated as I feared and most of the Syntax still applies from C++. With minimal googling, I was able to build a fully functional Custom Paper Deployment Tool using Microsoft Visual Studio 2010 as my Integrated Development Environment (IDE).
Please note that the Custom Paper Deployment Tool is not supported by Livescribe in any way, shape or form. As the Developer Program has ended, this tool is not associated with it at all. There is no warranty (either explicit or implicit) on the tool. I do not take any responsibility if anything adverse were to happen to your smartpen because of my tool. By going to the bottom of the page and clicking-through to the installer page, you agree to the terms and conditions listed above. This tool is available freely to all users by following the download link at the bottom of the page.
You can download the current version (188.8.131.52) from the Custom Paper Deployment Tool homepage. Further information regarding Custom Paper Deployment Tool is available there. Along with the Custom Paper Deployment Tool, I am today releasing eight 150 page Lab Notebooks along with eight 25 page Unlined Notepads. Simultaneously, I have increased the number of all notepads to eight of each type. Stay tuned for their individual release pages coming up along with individual download links. The download for Custom Paper Deployment Tool includes all of the files needed to deploy and print all 32 of these Notepads so there is no need to download them individually anymore! As with all of my Livescribe related downloads, Custom Paper Deployment Tool is compatible with both Echo and Pulse Smartpens.
I’ve already released 4 50 page notepads of lined notepads for Livescribe. Download: https://rohankapoor.com/projects/livescribe/lined-notepads-1-4/ . This gives a total of 200 unique printable usable pages before one has to archive to use them again. I’ve had several requests from people for more lined notepads. I have considered making them for my own use as well. I decided it would be best to take a public poll and see how many people actually would find additional lined notepads useful. If more people want them than not, I will be quite happy to create and license another 2 for now. If/when more are needed, they can be added as well. I have my original templates for the lined notepads so with a few modifications to the vector graphics files and a new paper project with the SDK, it will be fairly simple to generate the needed notepads.
My other projects for the Livescribe Smartpens are available here.
I just got around to uploading my lined notepads for Livescribe’s Smartpens. They are 50 pages a piece and there are four of them. The plan is to release two more of them soon. They are deployed via the standard deployment process (which I have outlined numerous times).
A couple of weeks ago WordPress (the software that powers this site), popped up a notification that version 3.0 Thelonius was ready to download and install. I held off on the upgrade for a while because of many problems I have had upgrading from version to version with WordPress. I have to admit though I was very pleasantly surprised with the ease of the installation. I simply hit upgrade, entered my ftp information and waited for it to think. A little less than a minute later, I was running WordPress 3.0. It was absolutely amazing, there were no problems, it just worked. This was a great change from version upgrades before, many times they have broken compatibility with lots of plugins (WordPress 2.8 for example) and broken the theme. This time, all of my plugins worked, the theme worked and there was absolutely nothing that needed changing at all. What I found incredible is that they were able to combine WordPress Multiple User directly into WordPress 3.0. On my one internal testing site (on localhost), I was able to update directly from WPMU to WP 3.0 also with no problems.
WordPress 3.0 ships with a new theme called TwentyTen. Kubrick (which has been the default theme for a while) has finally been replaced with something that is fully compliant with Web 2.0 standards and looks amazing. The only reason that I’m not using it myself is because while it is an amazing theme, it isn’t “techie” enough for my liking. It’s still a great theme, but I probably won’t be using it, at least not for this site.
However, as amazing as WordPress 3.0 is; it still (like everything) has it shortcomings. Namely compatibility with BuddyPress 184.108.40.206. While the basic install of BuddyPress is still as easy as ever, the combination with bbPress is broken again. Now attempting to enable the bbPress portion of BuddyPress results in a bb-config.php being created, no database tables being created, and an overall total mess. Basically the forums function is completely broken and this makes a large portion of BuddyPress and by extension WordPress useless. This is a rather large bug and whether it is with WordPress 3.0, BuddyPress 220.127.116.11 or with the version of bbPress included in the BuddyPress install, it needs to be found and fixed quickly.
Automattic is rather good at putting out bugfixes and I’m sure that once they know about it, they and the full team of Open Source Developers behind WordPress, BuddyPress, and bbPress will patch this bug and everything will be working again. It will just take a little bit (more) time!
Previously, I wrote Why Intense Debate Still Isn’t Ready for WordPress Use!Since then, my view on Intense Debate has changed. As I mentioned earlier, I’ve always been a big fan of Automattic’s attempts to combine user accounts between various services allowing us as blog holders to simplify the number of logins we need to remember. Nearly two months back, Intense Debate attempted to add themselves to the Autommatic “account combined” list.
It had mixed success because while it allowed those of us with WordPress.com accounts to comment through Intense Debate, we still had two profiles. There was an Intense Debate profile and a WordPress.com profile. This created confusion because we now had two accounts instead of just the one that we were supposed to. The intentions were to fix this soon, but it still hasn’t happened. Here’s why it affected me:
I decided to try out Intense Debate myself to see if it would fit the needs of this site. I ended up creating a new Intense Debate account, not realizing that I could just sign on with my WordPress.com login and password. I linked this site to and my comments synced perfectly with Intense Debate. Then of course, I read this post and decided that I wanted my Intense Debate profile to be the same as my WordPress.com one. Of course, I deleted my Intense Debate account and then reset the plugin. I tried to connect it to my “new” account but of course, it wouldn’t let me do that. It seems that you need to disconnect your WordPress blog from Intense Debate before deleting or switching accounts. Now I’m stuck, without Intense Debate. My hope is, that when the merger goes through properly, they will realize that my orphaned blog belongs to my WordPress.com account and attach the two together. That would save a lot of hassle for all of us who don’t read directions properly before beginning.
Since then, Intense Debate support have looked into my accounts and have combined the two of them under my wordpress.com account and I no longer have two accounts, They believe that all other accounts should be combined by the end of the year, which with the volume of accounts they have is understandable.
So, here I am: running Intense Debate again except this time with only 1 account!