4:48 pm
One of the things I am considering doing differently on my social network is allowing screen names instead of real names. I am even considering allowing entirely anonymous users. The focus is more on publishing that interaction, although interaction is a big part of it. There are lines to consider, of course, but who am I to say you shouldn't be able to complain about your job and not get fired? It's a consideration at least and as I get closer to user profiles I'll have to make a choice for relative anonymity or public identity.
7:16 pm
I've been testing an example plugin that seems to be working OK. I don't like how the memory usage shot up, but then again Clay is just now getting over 1mb in memory usage. Compared to anything else, that's pretty damn good. My goal is to keep it below 3mb on a full scale site. My old Worpress site was using closer to 20mb with few addons. So plugins are finally becoming functional. The issue I'm running into is automation. I don't want app developers to have to support a plugin, I just want it to work. On the other hand I want apps to have control over how a particular plugin behaves or is displayed. It's a lot trickier than I expected and I've taken too long to implement to have a solid grasp of the original plan. I hope to finish it up so I can get back to adding apps.
8:20 pm
I've been finishing up the plugins app/module in Clay. Once they are working I'll be revamping the blog app to work better for multiple users and adding a comments app. The social network isn't online yet...awaiting these changes and a new feature I'm not going to discuss just yet. I'm trying to keep my perfectionism at bay so I can actually launch in January haha. Honestly though, I do think what I am doing right now could be important one day so I want to do right. I am ready to finish the latest changes though...this old version of Clay is definitely dated.
4:24 pm
The Clay repo has been upgraded with the latest Bootstrap and JQuery versions and the changes merged. Over the next week or so I plan to get an alpha version of my social network up. I'll post a link here sometime afterward and allow a few people to register and try it out. In the beginning I'll only be allowing small blocks of users to register at a time and you'll have to use a link from here with a reference code. Hopefully by the end of January I can allow larger groups to register at a time. I dont want it to grow too fast at first. Once I am confident my servers can take more then I'll open it up. In the meantime, the code will be available for other sites to go up. I will likely release the code in beta in march and open up the distributed network. Distribution will be optional to 3rd parties, but will enable a lot of features that wont otherwise be available. More to battery is dying :P
5:16 pm
I've added a branch to the Clay repo and began upgrading to Bootstrap 3. It's more of an undertaking than I expected, but will hopefully save some time opposed to doing it down the road. I also added Font Awesome support. I hope to finish up the changes and merge this week.
6:09 pm
A new kind of social experiment is coming and I can't wait. It laughs in the face of corporate media and limitless IT giants. It's free, open source, open in every way, and distributed. It has been brewing in my head for years and no one has done it correctly, so I'm going to do it. By myself at first, but hopefully others will pick it up. It's almost time to remember again what WWW stands for. It's almost time to take back the web and make companies realize the the users are about to become their competition. It's almost time...and I can't wait.
In January 2015, I will be launching a social network built on Clay. It will start out as a single site. From there it will grow into a distributed social networking platform. More details and specs to come. The site will open in limited alpha and move to beta once other sites can join.
5:39 pm
I finally got back to working on Clay some more.  The Plugins app/module are almost finished, but I haven't pushed them to the repo yet.  There is still some work to do and a lot of testing left.  I've been adding a Core API to applications that will provide outline information without having to call individual application APIs, such as: item types, items, fields, etc.  This API will also soon handle routing for short urls and an extension of it may be used by the menu/navigation system.  It is also required by Plugins to utilize Hooks in applications.

Unfortunately, I didn't get to work on anything tonight because my daughter's laptop (my old laptop) crashed and I'm trying to do a backup and restore.  

There are several updates I want to do to Clay before the 1.0 release coming up.  One of the things I really want to do is upgrade Bootstrap to the latest build, but that will involve changes all over the place.  That may end up coming a little later, as I don't see any critical changes, but I would like to migrate to it sooner than later.  The longer I go without migrating the more that will require updates.  I also want to do some restructuring in the Clay libraries, but again I may push those to a supplemental upgrade.  

My plan right now is to push forward with Plugins, get the menu system in place, and implement short urls.  I plan to have a few publishing applications available for 1.0 and some supporting plugins to go with them. I will probably take a little time to evaluate how long a Bootstrap migration will take and then decide when to put that through.

Right now I'm hoping to release Clay Framework 1.0 just before 25th December and Clay 1.0  just after 1 January.  I'm thinking it's doubtful I'll have a lot of documentation for either one.  I'm actually hoping to have a lot of the documentation built into Clay and the framework will mostly start out with source generated documentation anyway.

My real job is keeping me really busy this week, but I'm hoping if I can manage to focus a little on Clay each day I will be able to finally finish my push toward 1.0.  I really want to move on to building with it and not just in it.
5:35 pm
Alright so I haven't done a lot of work on Clay lately, but I have been really busy. Here are some updates. In August I started a new hobby: homebrewing beer! So far I've bottled a wheat beer and a German-style lager and I have a Scottish red and a Belgian white almost ready to bottle. The next batch will be a try at a Belgian dubbel and then probably another lager. By far my favorite hobby of all time. Also in August I went on a road trip to Slovenia, Croatia, Austria, and Germany. We stopped in Munich for a few days, but Pula, Croatia was by far my favorite stop. If you ever get a chance, go to Croatia. I live in Italy so it wasn't far of a drive for me. I also found out I made Tech Sgt (Air Force) so I get a raise in either December or January. On top of that I have been promoted early so I have my own shop now. A little nervous about that part, but I have a lot of background knowledge so hopefully it works out. I was supposed to get a promotion in November to a shop chief position, unfortunately in some ways at least things change so I'm taking on a new role where I work now. This past weekend I went to Destination Star Trek 3 in London! Was awesome! I took my wife, she's the Trekkie, but I really ended up having a good time. So, back to Clay. I have come to the conclusion if I keep building it for someone else, no one may actually use it. From now on I'm going back to the original intent and building it for me. I plan to still release it to the public, but if someone wants something different out of it they will have to help. It's time for me to start building with it and not just on it. With that being said, most of the features I've wanted are what I've discussed before. I'm just not trying to tailor it as much to what I think people want to use. It's been a fun couple of months!
In effort to begin building up documentation of Clay, I've added an RFC repo under Clay. This repo will hold Requests for Comments files that outline the project. They are intended to open the project up more and provide developers a means to contribute intellectually to the project. They are also intended to be used as a roadmap tool to guide Clay through stable versions.
An addition to application requirements is being implemented. Apps will be required to have a Core class in their library folders. This will be used by Clay core libraries and modules for supporting system functions. Eventually it will be used for routing short urls, menus, and breadcrumbs. Initially it will be used for hooks. A generic class will be extendable from the core to simplify the process.
8:39 pm
I've been working on the Dashboard side of Plugins. I should be pushing that out to the repo Sunday. After that I have to add some utility libraries for apps to declare itemtypes and itemids. Those libraries will also be used by the menu and other things. The menu is the next major task, but we're not quite there yet.