Categories
Weblogging

TBD Tags et al

I’ve been wanting to write something on Technorati Tags, the conference on journalism, blogging, and credibility, as well as a follow-up on LID, and even a little on Wordform (Eh? What’s that?), but all of this deserves a thoughtful discussion, carefully written. Frankly, I’m not in the mood for either thoughtful or careful, so I think I’ll brave the cold and the snow and go for a walk. I’d take photos, but once you’ve seen one Missouri landscape covered in snow, you’ve seen them all.

Well, I’ll still take photos–would have to pry camera out of cold dead hands–but you’ll have to go to Tinfoil Project to see them. Bigger pics, better bandwidth suckage.

Categories
RDF Technology Weblogging

A credible coder

Recovered from the Wayback Machine.

I’ve been silent in this weblog, primarily because I’ve been working on a couple of other projects. I had talked with a good, and wise, friend of mine about this effort and he made a point that I felt was valid: that I should implement those applications or functionalities I’ve talked about previously first, before taking on a new project. It’s all about credibility you see.

Of course, I could point that I’ve delivered numerous tricks, tips, code fixes, not to mention how-tos and tutorials and what not, as well as helping to install 109 weblogs, and answering whatever questions others have asked. I had assumed that this gave me some credibility; Still, I understand what he was saying: complete applications shout where help and tips and fixes only whisper.

So I’ve been working on three major projects. The first is a ‘comment package’ that has much of the nifty comment functionality out at Burningbird, wrapped up into a package that could be used by people using other weblogging tools. This includes live preview, spell check, and post-edit functionalities. I have it finished for WordPress, but I’m also creating a Movable Type and Textpattern backend. These latter are for a couple of friends that have asked for the functionality. More to the point, though, I wanted to demonstrate that one can extend the tools outside of the traditional plug-in environment, and with that extension, make the functionality available to a variety of tools because the data and functionality between the tools is so similar.

This one is almost finished, but incorporating these changes into the templates for the other tools is a bit tricky because they are a changing, not the least because of that nofollow nonsense.

The second project is to provide updates to the material in my chapters for the Practical RDF book. This has been interesting and fun, and I am pleased to see a maturity in both specs and data. I’d like to see the technology a little more easily embeddable, which means lightweight language specific frameworks. But they’re coming.

I’m actually using the technology that I’m covering above in the final project, which is a variation of the Poetry Finder I talked about long ago. However, rather than just poetic annotation, this application will allow one to specify any field of data, such as legal, political, genetics, whatever, and annotate it using RDF statements, which are then added into the MySQL database for a specific weblog post.

It’s not going to require that users understand RDF, or even that developers understand RDF. The developers will be able to define a set of statements they want to capture as a model, and this will be used to generate form statements of the nature of _______________ issomething _____________________. An example would be “bird” IS METAPHOR FOR “freedom”, with the issomething provided by the model developer, and the values provided by the user.

Then, when a post is accessed (either WordPress, or Movable Type implemented as a dynamic PHP weblog) with an “/rdf” extension, .htaccess rules will trigger functionality that will deliver a complete RDF/XML output of all the data that is defined for a resource defined with the URL of the article. So, a specific article could have poetic and political annotation, and both would be combined into one model and returned when the URL is accessed with the “/rdf” extension.

Sure the statements defined using this extension are simple, but most models will consist of simple assertions. A case in point is the example data that I’m using at Practical RDF’s original Query-o-Matic: a listing of all terrorist acts since 1988. Simple, yet; but still managing to capture a lot more context that the other folksonomy/tags implementations I’ve seen.

The tricky part on this is getting the PHP together to maintain the backend services. There is RAP (RDF API in PHP), but it doesn’t implement SPARQL (the W3C RDF query language spec) yet, and I had hoped to use this query language.

My hope is by the time I’m finished with these projects, WordPress 1.5 will be out. I’ll then follow through on Wordform, but based on the final 1.5 product, not one in process. It will also be less ambitous than my original intent, primarily because its for my own use and as a curiousity to others — I don’t expect much interest in it.

What it will have is:

1. All data operations are pulled into a separate file rather than have bits and pieces of SQL scattered about. This makes it a whole lot easier to make changes, especially to the data model.

2. I’ll most likely be altering the comment and trackback spam prevention to incorporate my own ideas, which have shown themselves to be working relatively nicely in Burningbird. I’ve talked about these previously in this weblog.

3. I’m going to change the conditional checks in the code. All of them are as follows:

if ( ’spam’ != $approved ) {

In other words, the literal is first, the variable second. In all my years of programming, you put the variable first, because if it’s null (hasn’t been assigned a value) the conditional fails at that point without having to check the second value. I wasn’t aware that PHP differed in this regard, and I have no idea why the developers of WordPress do it this way. But it bugs me, so I’m changing them for no other reason than it bugs me, unless someone pops in with the reason for this, in which case I won’t. Who knows, maybe PHP does handle this all differently.

4. I’m making the admin more dynamic. Well, I’ve already made this change. With this, you can add a new comment or post status, high level menu item, and individual post menu item by updating tables, as these will not be table driven. In line with this, the semantic data extension talked about earlier will be incorporated into Wordform’s administration pages, as well as my existing fullpage preview functionality, per comment moderation, and post status of ‘insert’.

I won’t be adding multiple weblog support, primarily because it’s a lot of work, I won’t be using it, and Wordform is mainly for my use. The separation of SQL into a separate file should help with this if I ever get energetic about this application again.

When finished with all the various application, I will put them online as GPL open source for others to do with as they will. I’ll be posting on these changes, as well as links to the code, at Burningbird rather than this weblog; except for the Practical RDF book updates, of course, which will go to the book weblog.

Categories
Weblogging

If we could take back anger

If you’ve ever left a comment and then come back to the page, unless you’ve somehow changed your IP address, you’ll see an option to edit your comment. This post-published comment editing feature is one I’ve been testing for several months, without once running into a problem. Yesterday and today I added HTMLEditor for it, though I may end up removing this (I’m not sure we need much more than the ability to edit mistakes, and check spelling in comments).

Along with live preview, spell checking, Talk Back, and throttles that will prevent mass comment spam postings, I’m including this post-publishing editing feature as the core of a comment package I’m working on that will work for WordPress (1.22 and 1.5), Wordform…and maybe any weblogging tool where some developer wants to write the necessary interface code. Which of these options is turned on is configurable–especially post-comment editing.

When I added post-published editing long ago, I was worried that people would come into my comments and write nasty things, and then once people responded, edit what they said to make those that responded look like idiots. However, this never once happened. Most people use the feature to correct grammar, spelling, add new material, or clarify a sentence or phrase.

Now, the lack of hostile ‘hit-run-and-edit’ could be due to the fact that my writing lately hasn’t been of a nature to inspire the necessary anger for this behavior. It’s true that I have, for the most part, mellowed in the last few months (all that hiking and photography); not to mention having stopped writing about politics and RSS–both topics guaranteed to raise someone’s ire.

(This could change this week, as I take aim at both digital identity and podcasting — twin irritants of mine that are currently getting a lot of *BigBlo talk. And it’s been too wet to hike.)

I wonder, though, if the comment editing feature, rather than encourage rude behavior, actually discourages it, because you’re less likely to respond to a comment left by another person if you know that person can edit what they’ve said. And if you don’t respond, they can’t respond back, and others don’t get pulled in, and so on, and so forth.

More, this ability may give us a second chance: to re-think ill-thought words and to edit an angry comment before someone else responds to it. If you had this abililty, would you use it take back your anger? Unsay what you’ve said? Edit out the sharp, pointy bits?

The only way we’ll know for sure is to try out this post-published comment editing in a weblog that gets more heated discussions than I get. Unfortunately, most of the weblogs I know that regularly get animated or even angry threads, are Movable Type (I wonder why?), so I guess I’ll have to get this working for MT in addition to WordPress and Wordform.

In the meantime, I’d appreciate feedback as to whether to keep HTMLEditor in or remove it. Note that it only works for Mozilla compatible browsers and IE (and seems to be problematical in Mac OS X — HTMLArea is currently beta for Firefox).

And if someone has a Movable Type non-production site up that they wouldn’t mind me testing code against (and possibly breaking), with SSH and direct MySQL access at the command line, please send me an email. Update looks like I may have a test site…but the price I’m being asked *shudder * oh you poor, poor dears…

*Big Blogger

Categories
Burningbird Weblogging

This is a disclaimer

Recovered from the Wayback Machine.

This is the only disclaimer I will issue from this site. It reads:

I will never issue a disclaimer at this site. Again.

The discussion rages around us about how we’re in danger of losing our credibility, or our ethics are in question. However a more serious issue is at stake: we are in danger of becoming bores.

Somewhere, somehow, along the way we began to take ourselves seriously, and now it’s difficult to read original writing that doesn’t have a caveat or a disclaimer attached. Multiple weblogs have popped up with people appearing out of nowhere, demanding that we all conform to a certain set of beliefs and practices, and the rest of us, who at one point in time used to have fun nod our heads and say “Yesir” or “Yesmam”, because no matter what, we want to be seen as ‘credible’.

What is it that we’ve been doing the last several years but establishing the authenticity of our voices? What more credibility do we need than that?

I used to frown at sites where the webloggers would use pseudonyms, not the least because I have a god-awful time spelling that word. Actually, it was because I thought that if our words meant anything, we would attach our name to them.

What I’ve found as I’ve grown up from babe to toddler to fresh young thing, to old and tired woman in these very pages, is that names don’t matter, because it is the words themselves that have to stand out naked in the light. It is our writing by which you know us, or don’t. At this point in time, either you know me or your don’t; you trust me or you don’t, and no disclaimer is going to make my voice more authenticate, or real to you.

I also used to mouth about this standard and that: one shouldn’t delete or edit a writing once posted; or one should note when there is a possible conflict of interest; or, in the case of something like Marqui, one shouldn’t write about a product in our space unless one has an interest in same.

What a pompous prick I was.

Frankly, if another opportunity comes along like Marqui (but not Marqui, itself) I plan on taking it. Why? Because it allows me more dignity than to have to pass the hat, an act that nibbles away at my confidence. And I will most likely write once about how I’m being paid by the company, but I’m not going to circle the entries in red ink and paste on “I’m getting bloody paid for this”, with each entry. Neither will I write anything I wouldn’t normally write, but you’re going to have to take my word for it, because I’m not going to post a notarized notice on my site that I Am Not Lying for Bucks. In fact, you might as well assume that everything I will write is a lie, but it will be an authenticate lie, because I will never write anything that I don’t want to genuinely say.

So if a company wants to pay me for upping their Google rank,rather than sneak it in through my comments, I will. And I’ll do so in my own immutable way, which will probably frighten away all of the right-thinking companies anyway, leaving me the interesting ones, and we’ll proceed to possibly have some fun. Because if I don’t promise not to lie, I do promise to do my best not to bore you, but no guarantees: what I may find interesting may not interest you.

(You don’t like my gnomes?)

I was asked in my post, The Other Shoe on Nofollow, the following:

Really now. Do you have a citation for this conversation with Dave Winer or did you just make it up?

I answered:

I make everything up at this site.

I’m really a haberdasher in New Jersey. My name is Stan, and I’m bald, 85, thin as hunger, sad as regret, but with big black eyes that once twinkled wickedly at saucy ladies who would show too much ankle.

Oh, and I walk with a limp, every other Sunday.

That is my disclaimer: *I make everything up on this site. It will then be up to you to read me, or not; to believe me, or not. You will have to make your own judgment whether to regard what I say about the Google nofollow attribute, or Jeff Jarvis, or the Harvard Conference of the Week, or especially, the existence of Missouri mountain gnomes. Basically, you’ll have to read what I read, and then read what others read, and you’ll have to form your opinion and act accordingly, because I’m not going to do it for you through the use of a bloody disclaimer! Sorry, there is no ‘get out of thinking’ free card at my site.

(By the way, I lie, but I do not lie about gnomes.)

I read something in Rebecca Blood’s weblog that brought me up short this morning and made realize how far we have fallen in our effort to be polite and proper and credible and ethical.

I’ve noticed a slight problem with the Technorati tagging system. For every tag, Technorati is pulling an indentically tagged photograph from photo-sharing site Flickr. Unfortunately, for a few hours this morning the most recent tagged photo under MLK was a picture of a protester’s sign that read “Setting aside our differences to focus on our common goals: peace, love, harmony, killing Jews, and tolerance.” Nice. [more…]

Now, that photo is perfectly appropriate on Flickr as part of an individual’s collection, and as documentation of Sunday’s rally. It’s perfectly appropriate as an illustration for ‘protests’, or even ‘Israel’ and ‘Palestine’, even though it surely will offend some people wherever it appears. But it is not appropriate to illustrate a category tagged ‘MLK’. I personally was offended–these sentiments reflect the polar opposite to those espoused by Dr. King. More to the point, such an illustration is inappropriate–that poster has as much to do with Dr. King as would a picture of a banana peel.

I called Technorati to register a protest, but was informed that Technorati had no mechanism available for removing the photo other than turning off the entire Flickr feed. Worse, I was met with polite protestations that Technorati is not in the business of editing the Web, just delivering it. I was also given some vague heebee-jeebee about “community standards” and how “the community would decide”.

Well, I’m here to tell you that community standards vary wildly, and in the case of an aggregator mean nothing at all. An aggregator like Technorati only provides a succession of individual posts, it doesn’t summarize or codify the content it serves. Furthermore, “community standards” do not, indeed, can not defend against abuse of the system–only design can do that.

I will write more on Technorati Tags later, because they have very serious consequences to semantic web development, but for now, I read Rebecca’s reference to ‘appropriate’ images and enforcing ‘community standards’ and I wanted to put my head down and cry. What is sadder is that Rebecca has enough power within this community, and hence Technorati, to possibly force her opinion of what is ‘proper’ through, and that scares the bejeesus out of me.

If this is what you want from a ‘credible’ weblog, or an ‘ethical’ one, than I can guarantee you now: I will never be credible, I will never be ethical, and I sure as hell will never be appropriate. And you may stick your ‘community standards’ where the sun don’t shine in my mountain gnome’s gnarly little ass.

*I even stole that phrase from Dave Rogers, who I think is telling us that what’s real is shared spit and cat babysitting. But I have seen a gnome, Dave.

Categories
Specs Weblogging

The other shoe on nofollow

Recovered from the Wayback Machine.

I expected this reason to use nofollow would take a few weeks at least, but not the first day. Scoble is happy about the other reason for nofollow: being able to link to something in your writing and not give ‘google juice’ to the linked.

Now, he says, I can link to something I dislike and use the power of my link in order to punish the linked, but it won’t push them into a higher search result status.

Dave Winer started this, in a way. He would give sly hints about what people have said and done, leaving you knowing that an interesting conversation was going on elsewhere, but you’re only hearing one side of it. When you’d ask him for a link so you could see other viewpoints, he would reply that “…he didn’t want to give the other party Google juice.” Now I imagine that *he’ll link with impunity–other than the fact that Technorati and Blogdex still follow the links. For now, of course. I imagine within a week, Technorati will stop counting links with nofollow implemented. Blogdex will soon follow, I’m sure.

Is this so bad? In a way, yes it is. It’s an abuse of the purpose of the tag, which was agreed on to discourage comment spammers. More than that, though, it’s an abuse of the the core nature of this environment, where our criticism of another party, such as a weblogger, came with the price of a link. Now, even that price is gone.

*or not