Posts Tagged ‘iknode’

iKnode and SOPA

// January 22nd, 2012 // Comments Off on iKnode and SOPA // iknode

After all the SOPA/PIPA protest, we are happy to see that our efforts did work effectively. SOPA is now dead. We at iKnode where really worried about the progress of the bill.

We just posted the iKnode’s team position on the SOPA outcome, you can read about it here.

It is good to see we can still make a difference.

Fly with the new Twitter

// December 9th, 2011 // Comments Off on Fly with the new Twitter // iknode

This morning I heard the news about the new Twitter UI, and got excited. I rushed to the new site created to explain the changes, and began reading. The design and effort put into this site is amazing. And it shows that this is not just another UI updated. This is a model change.This became obvious after I finished reading.

I enjoy Tweeter very much. I can’t say I fully understand their current business model (if there is one), but it is a fun add-on in my life. With these new changes, I see a Business Model and also a service that could become the center of focus not only an addition. This new path clashes in direct competition with Google+ (primarily) and with Facebook.

Twitter now is a worthy competitor of my time against Google+ and Facebook, and this makes it all very exciting. I am eager to see the new Twitter.

Additionally, since all I can think of lately is iKnode, I began to focus on the validity  of our vision, specially looking at it as clear as the new Twitter (or at least it seems to be clear), or as fuzzy as the current one. iKnode’s whole vision is based on the three basic aspects that make a Back-end system:

  1. Application Execution
  2. Data Storage
  3. Task Scheduling
We have been testing Application Execution since November, and next week we release a Document based Data Storage and Task Scheduling. Having those 3 aspects, the vision of iKnode is functionally complete. But that is not all. Those 3 aspects are like the basic colors; you can mix them and get the rest. For example, disconnected services can be easily be implemented with the mixture of the three; another example is guaranteed messaging which can easily be implemented by using a data store and an scheduled task.
We have the minimum feature set that can cover the greatest surface of implementation for back-end systems. I believe we are in the right track for an stable business model, just like tweeter is doing now.

Evolution of an UI

// December 9th, 2011 // Comments Off on Evolution of an UI // .net, iknode

We have working hard on iKnode, and one of the things we wanted to improve was the UI. We just recently reduced the top bar to make it less complex, and also changed the icons to a more minimal set.

As we add functionality, iKnode has been growing complex and that has been reflected in the UI. That is exactly why we are taking the time to make it more friendly.

After we published the new UI, I compared it with past releases and I thought the evolution has been amazing, so I decided to put the UIs in a post. Without further ado, here there are starting from the first UI:

 

iKnode UI v0.8

Version 0.8

iKnode UI v1.0

Version 1.0

iKnode UI v1.1

Version 1.1

iKnode UI v1.5

Version 1.5

iKnode: What is in a name?

// November 18th, 2011 // Comments Off on iKnode: What is in a name? // .net, Algorithms, Apple, Architecture, asp.net, cloud computing, iknode

I was recently talking to a friend, and he asked me why I named our project iKnode. He said: “I know you are a fan of Steve Jobs but this is too much”. To be honest, it has nothing to do with Apple or Steve Jobs.

The story begins in 2003 when I was doing my dissertation for my master. I was working for a model to mine data from Data-warehouses to create a knowledge base using Frames and Protegé. I created an engine to do the transformation and mining, at the time I called it IKnow. It was a single engine that only analyzed, and extracted the data to create Ontology classes.

After a couple of years I got interested in distributed systems, and I made the engine run in a distributed fashion and interact with other engines. They could learn to do things, teach others and perform tasks. I figured that code is knowledge. If I wanted the engines to be able to learn and talk to each other they would have to have a common language. I decided to use C# for that. Now I had multiple nodes running on different machines, and I decided to call each node an IKnode. The product as a whole was still called IKnow.

After talking to a friend back in 2006, he mentioned that the name IKnode sounded more interesting than IKnow.  After some consideration I changed the name and the name space of the code. I even bought the  domain. In this same talk, it also came out that for IKnode to be useful you needed a whole team of nodes to perform tasks. And I mentioned to him, jokingly, “There is no I in IKnode”. And then I thought: “But there is an I in IKnode”. And that struck a chord. I thought: “the I is not important, so let’s make it a lower case I”. And that is how the name came to be iKnode. The only letter that is upper case in the name is the K. Which is the whole purpose of the project: Knowledge.

It is interesting to remember how far iKnode has traveled, and how it has grown. I feel like a proud father right now. :D