NoteWorthy has been up and running on a live server for the better part of two weeks and, in that time, I've been able to squash a number of bugs that were hidden deep within the pockets of my ignorance. However, as more people come to see the website in action, one of the most common questions is this: When can I download it?
How many wires do you typically work with on a daily basis? In my case, the number is way too high for what I actually try to accomplish. On any given day I lug my tiny notebook with me to work. The batteries currently hold a charge for about 28 minutes on a good day if nothing is plugged in to the USB ports1, so that means I need to carry around at least the power cord and brick. In addition to this, there is no WiFi at any of the work offices (all five of them), so a 5m long network cable is mandatory. The notebook has a 128GB SSD, and my iTunes library is 200+ GB, so this means an external USB HDD is brought from place to place. There is also the USB to Apple 30-pin connector, a USB to SoftBank cell phone adapter, and a USB to mUSB cable to round things out should I find myself in a pinch. To make matters worse, yet another cable is used to connect an external monitor to the notebook when working at home.
Yesterday I spent the majority of the day working on the Noteworthy API, and the blog post creation code was the primary focus. One of the goals I've been working towards is to have the entire blogging engine (both the API and the Web front end), run well on a cheap Linux-based web server using a first generation 166MHz Pentuim processor with 32MB RAM. At the moment the code will run on a 200MHz system with 64MB, but that's not good enough. It has to run on servers nobody in the first world would ever want to use. The reason is simple: I want this to be the blogging platform used in developing nations and people who don't want to spend more than $2 a month for server space. So, in order to reach this goal, Noteworthy needs to be able to run without a MySQL, Postgress, or any other database back-end.
Like many other people who are always trying new software tools, I was among the early adopters who downloaded, installed, and used Evernote while the rest of the world continued using the tools they've been comfortable with. Evernote is, for many people, just a solution looking for a problem. This perception is exemplified by the number of people who often ask me why they would want to use the tool when they've been getting by with slips of paper, dedicated notebooks, and a plethora of other record-keeping options1. What exactly is Evernote good for, and why have I been promoting it so much?
It seems that every few weeks there's yet another blog platform released to the world that promises to revolutionize how people communicate online and take market share away from the long-entrenched players that have dominated the market for years. So what makes Noteworthy any different, and why would anyone want to use it? This seems to be a common question people have for me whenever they hear about this little project I've taken upon myself, and it's a fair thing to ask. The answer, though, is somewhat something most people don't expect to hear: it publishes your Evernote posts from one (or more) notebooks to the web, and you probably don't want to use it (yet).