Category: Technology

Categories
Web

Cite not link

I do have considerable sympathy for 1Thomas Crampton, when he discovered that all of his stories at the International Herald Tribune have been pulled from the web because of a merger with the New York Times.

So, what did the NY Times do to merge these sites?

They killed the IHT and erased the archives.

1- Every one of the links ever made to IHT stories now points back to the generic NY Times global front page.

2- Even when I go to the NY Times global page, I cannot find my articles. In other words, my entire journalistic career at the IHT – from war zones to SARS wards – has been erased.

At the same, though, I don’t have as much sympathy for Wikipedia losing its links to the same stories, as detailed by 2Crampton in a second posting.

The issue: Wikipedia – one of the highest traffic websites on the Internet – makes reference to a large number of IHT stories, but those links are now all dead. They need to delete them all and find new references or use another solution.

As I wrote in comments at Teleread:

I do have sympathy, I know I would be frustrated if my stories disappeared from the web, but at the same time, there is a certain level of karma about all of this.

How many times have webloggers chortled at the closure of another newspaper? How many times have webloggers gloated about how we will win over Big Media?

The thing is, when Big Media is gone, who will we quote? Who will we link? Where will the underlying credibility for our stories be found?

Isn’t this exactly what webloggers have wanted all along?

Isn’t this what webloggers have wanted, all along?

I have sympathy for a writer losing his work, though I assume he kept copies of his writings. If they can’t be found in hard copies of the newspaper, then I’m assuming the paper is releasing its copyright on the items, and that Mr. Crampton will be able to re-publish these on his own. That’s the agreement I have with O’Reilly: when it no longer actively publishes one of my works, the copyright is returned to me. In addition, with some of the books, we have a mutual agreement that when the book is no longer published, the work will be released to the public domain.

I don’t have sympathy for Wikipedia, though, because the way many citations are made at the site don’t follow Wikipedia’s citation policy. Links are a lazy form of citation. The relevant passage in the publication should be quoted in the Wikipedia article, matched with a citation listing the publication, author, title of the work, and publication—not a quick link to an external site over which Wikipedia has no control.

I’m currently fixing one of my stories, Tyson Valley, a Lone Elk, and the Bomb because the original material was moved, without redirection. But as I fix the article, what I’m doing is making copies of all of the material, for my own reference. Saving the web page is no different than making a photocopy of an article in the days before the web.

In addition, I will be adding a formal citation for the source, as well as the link, so if the article moves again, whoever reads my story will know how to search for the article’s new location. At a minimum, they’ll know where the article was originally found.

I’m also repackaging the public domain writing and images for serving at my site, again with a text citation expressing appreciations to the site that originally published the images.

By using this approach, the stories I consider “timeless”, in whatever context that word means in this ephemeral environment, would not require my constant intervention.

Authors posting to Wikipedia should be doing the same, and this policy should be enforced: provide a direct quote of relevant material (allowed under Fair Use), and provide a formal citation, in addition to the link. Or perhaps, instead of the link. Because when the newspapers disappear, they’ll have no reason to keep the old archives. No reason at all. And then, where will Wikipedia be?

1Crampton, Thomas, “Reporter to NY Times Publisher: You Erased My Career”, thomascrampton.com. May 8, 2009.
2Crampton, Thomas, “Wikipedia Grappling with Deletion of IHT.com”, thomascrampton. May 8, 2009.

Categories
SVG XHTML/HTML

Whipping boy

I noticed a passing twitter message from Laura Scott. It said One word: standards. Firefox follows w3c standards. Internet Explorer does not. She wrote it in response to another Twitter message from tutu4lu, who was having problems with a web page appearing differently with IE than Firefox.

It is true that Firefox implements more standards than IE, especially in when it comes to some of my favorites, such as SVG. And I appreciate the fact.

Firefox does not necessarily get an A+ for all of its effort, though. In particular, if Microsoft’s lack of implementation of XHTML has been one force against broader implementation of XHTML at web sites, Firefox’s own handling of XML errors in XHTML is another, more subtle force against XHTML.

Here’s an example. I added an ampersand (&) to a URL in one of my posts, which generates an XHTML error. The following are three screen shots from Chrome, Opera, and Safari, respectively, that demonstrate how they handle the error:

XHTML error in Chrome
Opera XHTML error
Safari error

Safari and Chrome are both built on WebKit, which handles XHTML errors by parsing, and rendering, the document up to the error. This has the advantage of providing some content, as well as being able to more quickly find the error when you’re debugging.

Opera doesn’t render the document, but it does provide a display of the source with highlighting where the error occurs. This is extremely helpful when you’re debugging a larger document. In addition, Opera also provides an option to render the document in HTML, rather than XHTML, which is helpful for everyone else.

Contrast and compare these screenshots with the following, from Firefox.

Firefox error handling

The Firefox XHTML error handling is also known as YSOD, or Yellow Screen of Death. It’s harsh, abrupt, and somewhat punishing in nature, with its sickly yellow background, and bright red text. The message is typically cut off by the edge of the browser window, so one can’t easily see where the error has occurred. It’s most definitely intimidating for readers who accidentally stumble on to an XHTML page currently in a broken state.

All four of the browsers do support the XHTML standard, and all stop processing the XHTML when an error occurs, as is proper. But where Safari/Webkit, Chrome/Webkit, and Opera try to provide a useful web page, Firefox picks up a ruler and gives the owner of the web site a good whacking.

It’s easy to fall into the trap of blaming all web development and design problems on Microsoft and IE, and to use IE as a whipping boy—to the exclusion of looking, critically, at the other browsers in the web space. If the lack of support for XHTML in IE is a primary inhibitor of the spread of XHTML, Firefox’s YSOD has to take the second place prize. Support for XHTML doesn’t end at the parser.

Categories
Diversity Technology

Open Arms

Regarding the recent Golden Gate Ruby Conference…

Sara Allan

The second low point was Matt Aimonetti’s talk “CouchDB + Ruby: Perform Like a Pr0n Star.” It is unfortunate that he took this joke too far. What might have been a short, juvenille, eye-rolling bit of humor continued throughout the talk to become increasingly disturbing. Amidst this normally warm, welcoming community, I spent an uncomfortable half hour wondering if I had somehow found myself in 1975.

…

If he had left it at a few introductory jokes, I would be writing a very different post. Instead the porn references continued with images of scantily-clad women gratuitously splashed across technical diagrams and intro slides. As he got into code snippets, he inserted interstitial images every few slides (removed from the slides below). The first time it happened, he mentioned that he wanted to keep everyone’s attention. It had the reverse effect. This technique was distracting and disrespectful to an audience who, frankly, is turned on by code.

Audrey Eschright

Here’s another problem in this tangle: Ruby (and Rails in particular) loves the rock star image. You see it in job posts, how people talk about their work, and the way Rubyists rant on their blogs. It’s macho, it can be offputting to both genders, and it makes it easy in this kind of situation to say, “what’s your problem? I’m just busy being awesome”. It’s also a significant barrier to adoption for people who aren’t already a part of this culture, and don’t find it appealing.

Mike Gunderloy

For what it’s worth, I think the original presentation was an inappropriate and regrettable mistake. However, far more disturbing to me are the reactions to the discussion on the part of some of the Rails community.

Folks, the idea that women are disproportionately underrepresented in engineering and software in general, and open source development in particular, should not be new and controversial in 2009 – anyone who cares to look can find such things as the FLOSSpols findings, or any amount of academic literature on the subject. Anyone who cares to take the time to actually talk to the women who are a part of the open source community will have no trouble getting an earful about how challenging it can be to participate.

…

But unfortunately for me, in parallel to the public discussion there have been private ones. I can’t reveal details without breaking confidences, but suffice it to say that a significant number of Rails core contributors – with leadership (if that’s the right word) from DHH – apparently feel that being unwelcoming and “edgy” is not just acceptable, but laudable. The difference between their opinions and mine is so severe that I cannot in good conscience remain a public spokesman for Rails.

Victoria Wang, in comments

DHH’s attitude seems to say that the more we lower ourselves to the most base level of marketing scum in the name of entertainment, the better, even if at the end of the day there are no more women, or anyone worth knowing, in the room. It kind of makes me want to never touch Rails code again.

Rev Dan, in comments

What chaps my ass about the whole thing is that it’s doing little more but reinforce the bullshit “developers are immature, overgrown 14-year-olds” stereotype. I’m sick to death of that one, especially because I run into that type of jackass more often than I care to.

We kinda have a “chicken and egg” scenario going on here… unless there are more women who attend these things then the few women who do will always feel like outsiders… but if the few women who attend now are offended, then why will more attend?

Matt Aimonetti’s response

In the case of my talk, people knew what to expect, they *picked* the talk, and were warned by the organizers before I started that I would be using imagery potentially offensive to some. The topic of my talk was obvious, and I would have hoped that people who were likely to be offended would have simply chosen not to attend my talk or read my slides on the internet. It’s like complaining that television has too much material unsuitable for children, yet not taking steps to limit their viewing of it. You can’t have it both ways.

We can argue forever about morals, professionalism, ethics, respect, etc., though this is all a distraction from the real problem that was raised by Sarah, namely that we have very few minorities in the Ruby community, especially women. Minorities do need to be more represented!

Ryan Bigg

I fear that it will rip a community apart. A community that should be working together on getting past this issue and bettering themselves, not regressing to childish bickering. That’s what gives this community an “immature” stamp by the [insert other programming language here] groups.

…

All I ask for you guys is to…

Chill.

Sho Fukamachi

Other reactions include pathetic “I am being victimised” attention-seeking, lame attempts at demonstrating how much “I truly care about women” etc, hilarious “I am leaving the Ruby community and re-installing Visual Studio” threats (please do!), and every combination thereof. I cannot help but think that if Matt’s presentation has the effect of getting rid of these disingenuous wowsers then he should henceforth be invited, nay required, to present at every Rails conference.

DHH, the father of Rails



But wait…there’s more…

Alpha Male Programmers aren’t keeping Women Out

You certainly have to be mindful when you’re working near the edge of social conventions, but that doesn’t for a second lead me to the conclusion that we should step away from all the edges. Finding exactly where the line goes — and then enjoying the performance from being right on it — requires a few steps over it here and there.

update

Excellent aggregation of opinions from women in the Ruby/Rails community. Particularly liked Amy Hoy’s take in comments

If you are going to try to be edgy and push boundaries and shit, you should at least be sure you’re good at it and know how to handle that kind of content, first. Otherwise, it’s just destructive.

Categories
JavaScript Technology

Sun sells out and there goes Java and MySQL

I guess I will now be looking at how to port my Drupal installations to PostGreSQL, since Sun sold out to Oracle. The Java issue doesn’t impact me, as I saw the writing on the wall as regards to Java a long time ago.

However, support for MySQL will most likely be completely undercut, if not eliminated. Or it will go through that fine Oracle touch, which means you can’t depend on support for the database in the future—not without it being either bloated, or “monetized” in some way. This is how Oracle works.

I can hear it now: But MySQL is open source. Oracle can’t hurt it, because it’s open source!

Being “open source” will protect MySQL. Yeah, right. And I believe I’m Superwoman and can’t be hurt by bullets, so just shoot me now.

I completely forgot about Sun and OpenOffice. I use OpenOffice for all of my writing. Guess I can kiss that good-bye, too.

I’d like to just kick IBM right now, for transmorphing back into the stupid, clumsy Big Blue dinosaur of days of yore. It let itself down, by not buying Sun. And it let the rest of us down, too.

Interesting reading the old post on Sun buying MySQL AB, from last year.

I think Sun is the best possible buyer, because of the following reasons: (Note that this is of course my interpretation)

  • Sun is committed to open source.
  • Sun doesn’t have an database of their own; In other words, no risk of internal conflicts between similar products.
  • Sun understands what it means to be a virtual company where people work from home.
  • Sun has a good understanding of developers needs and there is a good chance that the integration of the two companies will be relative smooth.
  • Sun has said they will let the MySQL developers continue work as before in their own unit and without big changes (except of course changes for the better!).

Of course, the early founder of MySQL left Sun, and started another open source MySQL company. We’ll see where this goes.

Last update, but the original founder of MySQL, Michael Widenius, has posted a note on the Oracle/Sun merger and MySQL.

The biggest threat to MySQL future is not Oracle per se, but that the MySQL talent at Sun will spread like the wind and go to a lot of different companies which will set the MySQL development and support back years.

I would not like to see this happen and I am doing everything I can do to keep this talent pool together (after all, most of them are long time personal friends of mine). I am prepared to hire or find a good home (either at Monty Program Ab or close to it) for all core MySQL personnel.

The man is probably inundated with resumes right now.

Categories
Social Media Web

My abbreviated self

I discovered that a URL has to be less than 30 characters, or Twitter automatically creates a Tinyurl version of the URL. This, even if the entire message is less than 140 characters.

There’s no way I can create URLs that are less than 30 character and still maintain my subdomain designations. Therefore I’m not going to try, and will most likely be removing any short URL stuff here. With all the recent “one million followers” foo flah, including the breathless designation that one person achieving one million Twitter followers is equivalent to landing a man on the moon and space flight, in scientific importance, I would just as soon stick with stodgy old weblogging.

Weblogging, where no one really knows how many people are following you, most people don’t care, we can actually communicate complete thoughts, and do what we want with our URLs.

From today’s WhatWG IRC:

hsivonen: I can imagine all sorts of blog posts about evil HTML5 raining on the rev=canonical backpattery parade

svl: Mostly (from what I’ve seen) it’s been “let’s all use this en-masse, so html5 will be forced to include this”.

Of all the items in contention with the HTML5 working group, the use of rev=canonical is not high on my list. Why? Because there’s no real argument for it’s use, and a lot of good arguments against its use, and it’s just as easy to use something else.

This all came about because Twitter was built first, designed later. One of the difficulties to keeping a message to 140 characters is that URLs can take 140 characters, and more. Yet there is no URL shortening mechanism built into Twitter. Not only is there no URL shortening mechanism built into Twitter, Twitter, itself, uses another, 3rd party, service: tinyurl.com.

Now, all of a sudden, people are in a dead cold panic about using a service that may go away, leaving link rot in Twitter archives. I hate to break it to the folks so worried, but it will probably be a cold day in hell before anyone digs into Twitter archives. Most of us can’t keep up with the stream of tweets we get today, much less worry about yesterday’s or last week’s.

But there are a lot of other problems associated with using a 3rd party service. Problems such as the recent Twitter follies, otherwise known as Twitter Been Hacked, that ended up being a not particularly fun Easter Egg this weekend. When you click on a Tinyurl URL, you don’t know what you’re going to get, where you’re going, or worse, what will happen to you when you get there. Even Kierkegaard would have a problem with this leap of faith.

There’s also an issue with search engine link credit, not to mention everyone using different URL shortening services so you can’t tell if someone has referenced one of your posts in Twitter, or not. This didn’t use to be a problem, but since everyone does most of their linking in Twitter now, it gets mighty quiet in these here parts. You might think, sigh, no one likes what you’re doing, only to find out that a bunch of people have come to your party, but the party’s been moved to a different address.

So I think we can agree that third party URL services may not be the best of ideas. I, personally, like that we provide our own URL shorteners. Not only would we get the search engine credit, it should encourage the use of the same URL in Twitter, which might help us find the party we lost. Plus, wouldn’t you rather click a link that has burningbird.net in it, then one that has dfse.com? Implementation of our own short URLs should be simple in this day and age of content management systems. All we need to do is agree on a form.

Agree? Did someone say, agree?

As I wrote earlier, I’ve heard too many good arguments against rev=canonical, including the fact it’s too easy to make a typo and write rev=canonical, when we mean rel=canonical, and vice versa. In addition, rel is in HTML5, rev is not, and I’m not going to hammer a stake in the ground over rel/rev. I’m keeping my stakes for things that are important to me.

Note to HTML5 WG: she has a hammer. And stakes.

As for what attribute value to use with rel, whether it’s shortlink or shorturl or just plain short, I don’t care. I took about five minutes to implement shortlink in this space. I implemented shortlink, because this is the option currently listed in the rel attribute wiki page. However, it would only take about a minute to change to shorturl. I even added the short link to the bottom of my posts, which can be copied manually and used to paste into a Twitter post, if you’re so inclined. See, I don’t have to wait for anyone’s approval; I am empowered by Happy Typing Fingers.

Regardless of what we do, I agree with Aristotle: way too much effort on something that should be easy to decide, quick to implement, giving us time to worry about things that are important in HTML5. Things such as SVG, RDFa, and accessibility.

Other discussions related to rel/rev/tiny:

And that’s my 4424 character take on tiny URLs.

Another reason tiny URLs are getting attention is because of the evil new DiggBar. Goodness gracious, people, why on earth do you use crap like this?