cyberSaps business: blogging news, internet biz, communities, UK angle
Blog is such a pejorative, amateur and mostly, young word. These days new words appear quickly in dictionaries and blog is no exception. With an estimated 4 million blogs most are indeed teenage girls talking with other, mainly local, teenage girls, and this is what the dictionary definition stems from. However, the internet is a big place, used by individuals to talk to their friends, and businesses to expand their client base.
Businesses do indeed blog. Serious businesses. They understand what it means to communicate directly with clients. How valuable that two way direct communication is. How they can influence the thinking of people outside their company. How they can demonstrate their expertise. How they can even work with, collaborate, with 'outsiders' to harness the might of the network.
OK. Then don't use the word blog. Take all it's power, all it's RSS feeds and aggregation features, trackback, easy editing, updating from mobiles, take it and call it, taa-daa... A news page. A news page with community features.
Nobody need know, that secretly, sometimes very late at night, you are a blogger.
So some people are still on dial up. OK most people are still on dial up. About half of the US is on broadband, about 30% of the UK is on broadband. So, someone on a 56k modem, hitting that page is gonna wait forever, or 28 minutes. While, little old me, on my 3Mb pipe I wait about 13 seconds. Which is OK in my book, I've always thought 13 secs to be a reasonable time, especially when I was on 64k myself.
One day, we're all going to be on much faster connections. These personal pages, are for then, when my kids look back at how they grew up. I'm not bothered at all if someone on dial up complains that this section of my site takes too long to load — they shouldn't be looking. Only me and people who know me can feel free to look, if they have broadband, or the time, as my parents do, to wait on 56k.
Be warned, it's going to get worse. More pictures. More video. Even I will be wanting more than 3Mb downstream.
|Total HTTP Requests:||179|
|Total Size:||8579254 bytes|
Object Size Totals
|Object type||Size (bytes)|
|Total CSS imports:||5|
|Connection Rate||Download Time|
|ISDN 128K||524.64 seconds|
|T1 1.44Mbps||46.45 seconds|
Oh my! OS X 1.3.5 Jaguar Panther is very nice. I had an old beta
before OS X was released, it was slow and awkward. This is fast and,
once I had fiddled with the prefs-as you do, looks nice, feels nice.
Hello, once again Apple. Even the clock speaks the time. Hee hee.
I have it running on a Firewire Powerbook G3 500Mhz 384Mb ram. Feels fairly responsive. Think I may like it enough to buy a faster machine.
Currently, connecting to my PC version of Radio through the excellent Firefox. Also have my beloved Thunderbird email app running alongside the necessary Timbuktu.
Where are the window opening and closing sounds, and what about changing the font in menus--to Sand ;-))))
This morning in my pubSub subscription for 'Userland' I saw another "I'm moving from Radio cuz it sucks" post.
Fed up with Userland the company I may be, and though nobody at Userland seems to care that ignorant bullshit like this is put out there, I felt it's time to refute some of the arguments put forward as "reasons for leaving."
- "Funky" HTML (good luck trying cleaning it up, Radio seems to do whatever it wants to with HTML). True, some of Radio's HTML is funky. But funky works, and works across all browsers. I've cleaned up some myself, Userland seems to be working to clean more. If I really needed to I could dive in and fix it all. All of Radio is available to edit, there's not a lot that's been kernelised, especially when it comes to the HTML. This really ain't a biggie in the real world.
- Userland's "Web Bug" gif embedded in RU generated pages (used to create the last 24 hour referrer logs) is extremely slow to load, making your whole site seem slow even when you "self host". I self host and now have zero to do with Userland's servers. I've removed the web bug, put comments on my own Manila server (since removed for other reasons than performance). I create my own logs using industry standard techniques, by analysing my own raw logs with Analogue.
- Lack of control over code. Sure you can make your own changes to Radio's Engine, but there's a chance they'll get written over in the next root update. This is the biggest, biggest misinformed error in these 10 problems. There's educated ways and fool hardy ways to edit code. Many things can be written by being inspired by Radio's code base, and those can be placed anywhere, never to be touched by a root update. The only place that could change in a root update is in the Radio.root, in the system table. Even then, most long term Frontier developers will have their own coping strategies for this. Mine is to use system.verbs.builtins.rootUpdates.update. I would then check what I've protected against new code, merge, then update the other servers I manage from the newly updated server. I don't do this everyday, it can be a big job. Mostly though it used to take an hour or so.
- Poor/Scattered Documentation - Userland should give users a free electronic copy of Roger's book with the first year's subscription to RU. There's a ton of dox. Find a Frontier verb, either look it up in Docserver, or look through Matt Neuburg's Frontier: The Definitive Guide available online. Or, use Google. I'm amazed that so many people forget to try Google first. As an FAQ Google will get your answer much faster than asking in the discussion groups. Remember the 15 years age of Frontier/Manila/Radio. Everything has been asked and answered before.
- Not a lot product development going on. Dave has moved on to other things leaving Userland and its applications in stagnation. Dave, gawd bless him, was both the worst and best thing about Userland. Now he's gone, I still hope that Userland will get on the right track. Dave Winer would never stop to fix bugs. He'd always find some other road to travel up in his discoveries of what Frontier could do. And some amazing discoveries were indeed found. But as I travelled those paths with him, I felt that I was always leaving the base camps ill prepared to survive on their own.
- Difficult to move you data to a different system ("lock-in"). It took me quite a while a a lot of tinkering to move my RU content to a less proprietary, more open format. Less proprietary? The only thing that's closed off from tinkering or rewriting is the kernel. And that's going to be open sourced pretty soon. More open? UserTalk was written to make code writing easier. If you've ever tried it you'll know what everybody says when they reminisce about writing code in an outliner, forget awkward curly brace notation for indentation and structure, the outliner takes care of all that, invisibly. Then it's the language itself: easy to learn, to look up verbs in either the ODB itself, or in Docserver, just control double click or option double click. Radio is open and accessible.
- Year old bugs have yet to be addressed. Four year old bugs have yet to be addressed, though this memory leak doesn't really affect the low use home user of Radio. But sure Userland really have missed the boat with bugs. For too long the response was, "thanks for the bug report, we've added it to the bug tracking." Even for minor typos. Many of us would correct the bug when we saw other's reporting, bypassing the company.
- Client Application is a CPU hog (at least on Mac OS X and Mac OS 9). This is an easy bug to fix. Well, I actually bypassed the problem, not fixed it. I switched off the check to see if anything is deleted in the local /www/ folder. Now, Radio only hogs when it does something, like aggregate the news, or check a folder for images or videos, or mp3s, or checks the mail, or checks other comment threads I'm monitoring, or... Otherwise, she just sits there. When you've a powerful content management system on your desk top, it's best if she's doing something.
- It's 2004 and no still SFTP available (unless you feel like creating your own tunnel). If you were using Userland's servers why would this matter to you? I use plain FTP just like 99% of the world.
- Almost impossible to do anything with comments & trackback entries if they're hosted by Userland's servers (which by default they are and there are no easy plug-ins to other services). Moving the comments to another service is a lot more difficult than moving your posts. No, moving to a different comments server, or service is piss easy. Getting your posts, from Userland, or any other service isn't easy for sure, but can be done especially if you'd use my Wipe Manila tool (BTW: no dox with it yet, nor free support.)
- (Bonus) You're pretty much forced to have a static pages (unless you really want to jump through some hoops) for your site (no php/python/perl/ruby interaction sorry). If you independently host, you can add any code to your pages, and interact with whatever you have on your server. However you want. Add the code directly to your template(s), include it as a renderObject on your desk top, or as an SSI. This is a daft point.
If you use Userland's servers, things are going to be slow. Uploading to a really busy server can cause time out problems. Comment servers were spread out more several months back, but have filled up again. Likewise with the web bug. Userland will always have problems scaling. Much better to use your own (rented) FTP server, a different comments service, or even another Manila site on perhaps your own server. And forget the web bug.
Mind, it's been over a year since I needed to update a Manila installation. And, since my licence for Radio expired this Spring, I've not needed to update that either. Next time I update Manila, say, I expect a long update process. Or, is that, that I hope there's lots of new stuff and lots of bug fixes and lots more from Userland?
There is still quite a bit of development still going on in the Radio world. I've brought out several tools myself, and other too have written some nice macros and tools. Several projects I've worked on are for my own personal use, I could release them as tools but the numbers just ain't there to make it work while. I particularly like my link in to Photoshop. Now, that's something that you cannot do with a server based blog.
Lock-in? How about exporting all your posts into one RSS feed? I built a tool to do just that. Others have merely exported their posts to text files and popped them into MT. I've even built a Wipe Manila tool that looks in Google for your Manila posts or Radio comments and either sucks them down and/or over writes them. There is no lock in.
In truth, I hadn't prepared for such a painful question. Painful, in that the damn leak has been there so many years, and still not fixed. It's so old that I'd forgotten about it. Likewise, root bloat, has also been lived with and forgotten.
In essence, I deal with the memory leak by putting machines off line several times a day for a minute or so after 10,000 page builds. For root bloat, I compact roots once a day for about 7-8 minutes for a large and busy installation, about 3 minutes for my Government sites (luckily out of office hours) and about a minute for some smaller installations that I manage. A minute and a half for my own Radio installation, too.
Why do I still use it? I don't know better. I can throw UserTalk around, within minutes knocking up sophisticated tools, so fast it makes me chuckle. Writing code in an outliner is tidy and the debugger a joy, and there's so much code to look through for examples.
8 months later, in London, in a room full of key developers, Manila, Radio, Frontier was shown to be a toy.
In a few days time, I'll have completed a review of Manila. I wanted this to be honest, but in my rough notes, I'd only included the lack of exciting development/developers, performance/scaling issues as points against. Now, I realise that I'll need to include, ye olde memory leak and root bloat directly as these are the root cause of the above symptoms. Not good. To tell potential customers of a four year old memory leak, they're going to ask, "if that's not been fixed, where's the product going?"
Frontier's being open sourced at the end of this month. But this won't mean the memory leak will be fixed, possibly ever.
Userland's two products Manila and Radio need good publicity, like any blog product, service. At the moment, they get near zero publicity. I've often wondered why? Now I think I see, perhaps the new management actually need to keep quiet. Certainly, they don't label their products: "WARNING: memory leakage and root bloat will cause your server to be offline for several minutes everyday. As a direct result, we'll not sell many products, and will not afford to keep the product regularly updated, nor will many developers stay around, those that do will be bitter, and the support lists will thusly be dictatorially moderated and eerily quiet."
Still, Manila is still the most comprehensive and easy to use CMSs on the market. You've only to ask my football meatheads or The Government Office for the West Midlands. Neither of them notice the memory leak.
And there's a decent book, which should be arriving here soon.
I wonder if I could mix in these business cards and school year book ideas with muy Manila address book? This sounds cools. They could create a search, with the returned results being used to populate a set of business cards, say for a team. Or, a poster for a floor.
"It'll be great to see peeps and schmooze about micro-content."
Marc Canter's European Tour: I've signed up for the London gig. Though I won't be able to stay very late, I'll have a last train to catch back up to Telford, I think it'll be worth while, just to get to meet some real faces. Matt Mower I've been meaning to meet for some time, and of course Julian Bond. Luke Razzell, I've met in the Summer.
Search across searches
This is version two. This time, everything is linked. So, not only can you browse the whole A to Z listing of names, but you can look up other people who are of the same department, team, location or grade. Also you can see who's an individual's line manager (and their line manager), and who else they line manage.
Using Manila's "shortcut" feature, people can add global shortcuts for:
- individual record pages
- email addresses
- phone numbers
Currently, I've had to swap the actual mugshots for silhouettes. Though, I loaded their ID badge images, the 'management' aren't keen, or is that the unions? Still, the idea is that each person, 'owns' their individual record. That is, in Manila parlance, they're the member who posted their message. So, they can log in, normally, and edit their message (record) even uploading a nicer picture, than their standard ID mugshot.
I expect over time, that this will be fun. What? A work's address book fun? Why not? If they can upload their own image, they could upload several. Pictures of their cat, of their holidays. Links to other sites. It could become much more than a regular phone book, somewhere where they browse for laughs. Linking to other work colleagues looking at friends of a friend. Hmmm. This is all sounding rather familiar, like a social network?
Well, considering that there are many bloggers within the Government Office as it is, we're not to far away from every person having a Manila blog. Technically, we're there (have been for 4+ years), it's a political problem, like the mugshots.