sleep in the code there slowing down their bots. Unfortunately, this will do little to dissuade them (it's not like they're hunkered over their computer watching the return status of each of their controlled zombie computers' requests). But it makes me a little happy. Throttling will come next. Along with some other measures.Awesome! Blog@Case's first podcast! — The Freedman Center in Kelvin Smith Library: Podcast. And, it worked!
Check out the RSS feed for the Freedman Center blog. It includes the following little snippet where the magic happens:
<item>
<title>Podcast</title>
<link>http://blog.case.edu/FreedmanCenter/2005/10/07/podcast</link>
<description>Testing a podcast & learning how MoveableType enclosures work on our blog system......</description>
<guid>http://blog.case.edu/FreedmanCenter/2005/10/07/podcast</guid>
<pubDate>Fri, 07 Oct 2005 14:51:19 EST</pubDate>
<enclosure url="http://blog.case.edu/FreedmanCenter/podcasts/10-07-05.mp3" length="4412159" type="audio/mpeg" />
</item>
Go head. Check it out in iTunes. Just point your podcast subscriptions to http://http://blog.case.edu/FreedmanCenter/rss20.xml and watch the magic happen.
Sword is going to be a simple and friendly multi-user weblogging tool specifically designed for use in academic environments. It's currently in development as part of Mark van Eijk's internship at Fingertips... You can track Mark's progress on his development weblog. The source is available from our Subversion repository at http://fngtps.com/svn/sword/trunk
[
[
Jeremy Smith
]
]
will get
automagically converted to the link:
<a href="
http://wiki.case.edu/Jeremy_Smith">Jeremy Smith</a>. See it in action:
Jeremy Smith. Feel free to go to town. Create some content. Only authenticated Case users can edit the content, but it is all world-readable; so have at it.
[Update: The inter-blog-wiki-linking information has been added to the
FAQ.
]Are Blogging Engines Like Typepad and MovableType the Future for all Web Pages?
Somewhat, I would say.
In talking with persons around campus in finding possible candidates for group blogs, I discovered that there are three (yes, 3) things that people do with their web pages that comprise 80% of all of their interactions with it (in terms of being creators/contributors to the web site / web page(s)).
Yep, that's it. That is what people do with their web pages 80% of the time (I should actually be saying 80 +% of the time, because, really, it is probably more). So, what do you do with the use case(s) that land on the 80 side of the 80/20 rule; well, you make those as easy as possible. And, for numbers 1 and 2 of the above list, that's exactly what blogging was meant to make as easy as possible.
So, yes, I see, in some form or another, "blogging tools" being used for a majority of web sites. Site creation will (for now) still be handled in tools designed for that such as Frontpage, Dreamweaver, notepad and the like. But, once the layout is contructed, it will be moved into a blog-like system and turned over to the site(s)'s contributors/editors for content posting.
Of course, people, themselves, are masochistic and may end up just sticking with hand-editing HTML SSIs for content creation or (and in some cases, I would use the phrase "and even worse") end up being sat down at a CMS whose controls resemble the complexity of flying a 747 and become numb to the constant barrage of semi-used options such as "would you like to add 7 needlessly complex levels of workflow to this document," "would you like to configure this content to sunset on the third full moon of every 4th quarterly of the year," etc. I feel sorry for these people. There are better ways to do things.
IBM today is publishing an announcement on its Intranet site encouraging all 320,000+ employees world wide to consider engaging actively in the practice of "blogging"...
Whether or not an IBMer chooses to create or participate in a blog or a wiki or other form of online publishing or discussion is his or her own decision. However, it is very much in IBM's interest -- and, we believe, in each IBMer's own -- to be aware of this sphere of information, interaction and idea exchange...
Very nice. I think more companies should actively encourage and reward employees who participate in blogging and "wiki-ing". Communication (being able to communicate and write effectively) is one of the most important aspects of any job, especially a job in technology. Participating in these online discussions only makes one better at such.
For the people that don't "get it"; no harm, no foul. You're just not as cool as us... ;-)
Let's theoretically say, Case hosted a Wiki; in what ways should the wiki service integrate with the other services offered at Case?
I can think of one easy one. If you surround a word with double square brackets in a blog entry, it automatically becomes a Wiki word that points to the Case wiki. So, if you typed something like:
Today, I walked around the
Botanical Gardens
and checked out the
Art Museum.
The phrases
Botanical Gardens and
Art Museum would automatically become links to the appropriate Wiki node once published.
But, what other ways should integration occur with the Blog@Case system? And, in what ways should it integrate with other services like the Portal?
What about Blackboard? As a matter of fact, I have heard that the administrators of Blackboard may be adding in the Learning Objects' Campus Pack plugin, which, in some fashion (it's hard to deduce from reading the documentation), offers blog and wiki functionality. How should all of that integrate together? Should it integrate together?
Just thinking...