The Design and Implementation of laffer1

HP has a new backup product called upline. It's a web and application based backup solution for Windows based PCs.

I decided to give it a try. I love .Mac and saw this as a backup solution for my Windows box in which I lost homework and itunes content on last year.

The website is great. However, I'm not impressed with the windows client. It's a bit ugly, and suffers from one flaw. Users must pick what file types they want to backup. it shows folders it's scanning, but it doesn't backup the whole folder. I don't like this. My information is all stored in my profile in windows and I want a full backup of that folder. I don't know if this was a way to minimize disk space usage on their part or concerns of liability. Either way, I don't like it.

This product would have saved my music and word documents that were lost in my vista crash. I'm going to give it a little more time and see what they do with it.

There is a free trial for one year with 1GB of storage and the plans are reasonable with unlimited storage.

I'm working on adding a tag cloud to Just Journal. I haven't really thought about it much, but there is a bit to it. You need to have frequency counts for tags and their names.

That can be found with this query:

SELECT tags.name, count(entry_tags.tagid) as num from entry_tags, tags WHERE entry_tags.tagid = tags.id GROUP BY name;

That will sort by the name, and give counts.

midnightbsd 2
justjournal 2

etc...

Then you need to find the min and max values for the frequency. Also, you need to choose how many different levels you want for presentation. Do you want 3 font sizes? use max - min / 3 to find the points where you want to change the font size.

The database schema is broken up into two tables with 2 fields each (in use).

tag id and tag name in the tags table. entry_tags associates a tag with a blog entry. You have an entryid and a tagid.