Laura Lemay has posted a nice review of tactics you can use to combat referrer spam. This is the type of spam where the evil spammers try to get their clients’ URLs into your web traffic reports. They particularly target sites which use scripts that display referrers to individual pages right on the page. Unfortunately, I’ve used such things in the past so I’m on the target list quite often. Really vile domain names get posted to my logs and make it more difficult to get useful info from my site statistics. I’m going to look at how I can implement some of the stuff in Laura’s post this weekend.
Getting back to real basics, what appears to be key in KM is certainly not the individual as an individual, but tying the individual into groups and groups into organisational objectives, because, let’s face it, KM is about making businesses work better.
It all has to come back to whether KM, knowledge sharing, communities of practice, what have you, actually contribute to achieving the organization’s goals. Excellent point.
So, we’re creating this context-free realm of free-floating metadata, like word magnets on a refrigerator door, that we will paw through and assemble, and, most important, do things we haven’t yet thought of.
The web still delights me even after working with it full-time for the past 6 or 7 years.
I’ve written several articles on weblogs for various publications over the past few years. Each and every one of them has changed ‘weblog’ into ‘Web log’ per some style guide rule during the editing process, over my objections. This always gets my goat for some reason. It’s weblog, people!
On a related note, I came across this page on how you can cite a weblog entry in MLA style.
Keith Robinson makes the case for outlining your publishing process before determining what system you need (if any) to support it.
Just learned a new acronym/concept today: COINs. Denham Grey posted a comparison of
Collaborative Innovation Networks (COINs) to Communities of Practice (CoPs): On COINs and CoPs.
As I now understand things, a COIN is a specialized form of CoP, an informal network that spans business boundaries and has a prime focus on innovation rather than individual participant identity, awareness and learning.
COINs follow examples of the open source ethos, participants are early adopters and they adhere to principles of collaborative knowledge networking. This seems to a fusion of social networks, enabled by web technology and knowledge sharing.
Denham provides several links to source material in his post. Check it out.
I spotted this definition on Doc Searls’ IT Garage (paraphrase):
DIY-IT is happening wherever you see shelves full of O’Reilly books.
So true! I’ve learned a lot and advanced my career by reading as many O’Reilly books as I can get my hands on and find the time to read.
Which reminds me of one-half of a cell phone conversation I overheard in the M Street Borders in DC one day. This young guy in dockers was kneeling in front of a shelf of operating system books and his phone rang. Here is the half of the conversation I heard:
Young Dockers Guy: Hello?
YDG: Yes, I know the server is down.
YDG: I’m looking for a book on it right now!
Peter van Dijck provides us with a view into the Belgian IA/UX community. He scores intercultural bonus points for a Fons Trompenaars reference!
Jeffrey Zeldman revisits web standards evangelism after some time off the rubber chicken circuit. I guess I’m not reading in the right places but I’ve never had a sense that there were huge rifts in the standards social club (other than RSS of course). I never felt turned off towards adopting standards once I learned about the benefits from reading folks such as Zeldman and Meyer. Maybe the controversy rings loudest to those in the middle of it?
Lisa Dusseault has posted about how the CalDAV standard that she proposed is picking up a bit of steam:
This is all great news. Calendaring interoperability has languished except for that burst of productivity back in 1998. People are locked into one calendar application depending on what server technology they have available, since there’s no common calendar access standard. Invitations work, kinda, but in practice the problems with recurrances mean that people must follow up the machine-readable text with human-readable text in case a mistake was made between two different vendors’ software.
Good news, but nowhere near done yet — this is just the beginning. Now we need volunteers. We need people to write specification text, review text, and manage the issues. We need people simply to pay attention to the work being done and provide their experience, or simply opinions, to bring issues to resolution.
I’m excited to hear about this effort. Effective calendar sharing is probably one of the major failings of most personal information management systems, open or commercial. Of course, the OSAF group that Lisa works with is trying to change all that.