Archive for the 'www' Category

Reciproc8: A Framework For Reciprocal Linking

Here’s an idea I’d like to implement. I’m not sure yet if anyone will want to use it, but I think they might; the idea is a widget for reciprocal linking.

Picture it like a snippet of javascript that serves up a couple links, much like Adsense serves up ads. However, instead of serving a paid-for advertisement, it just shows a pair (or some other small tuple) of link to other sites. You don’t earn any money for showing these links, instead you simply have your site in the queue as well, and it will be listed on the other sites in the network. Essentially, you’re exchanging links, but with out the cumbersome need to make individual arrangements — and you could potentially link to thousands (or hundreds of thousands) of other sites, without actually having a static list of a 100,000 links somewhere on your site.

Reciprocal links really means you’re providing a potential stream of traffic to others in exchange for receiving potential traffic yourself. The reason you want this traffic is immaterial; whether you want more people to view your ads, or whether you want to change the world and need more people to hear your ideas — all that is irrelevant to the system. All it does is serve links.

The system of serving links would be evenly distributed. Say, for example, the service was live and 100,000 sites had joined. Each puts a javascript snippet somewhere on their page which displays two links to member sites. Let’s say, for the sake of simplicity, that the average number of page impressions per site is 1000/day. Some may be far higher, many will be far lower. Regardless, that would mean that the network of sites displays 200 million links per day, or that each member site would have 2,000 links a day showing, somewhere on the network. This is assuming that links change with each page impression, and that after each link has appeared once it returns to the end of the queue, waiting to appear again.

Basically, something like this would be free reciprocal advertising. If you run ads, the benefit could be more traffic ergo more revenue; if you don’t, more traffic ergo more people are seeing what you’re doing. Assuming that you’re writing or creating something cool that you want to share, that might be all you want.

I sort of like the idea. Low overhead, simple, no complicated ranking algorithms, win-win scenario for anyone who joins the network. It would be a moderately simple application to build, which means that anyone could replicate it without much trouble. But, so what? I’m going to try to have something like this built this winter, just to see how it will work, and to gauge interest.

If this sort of simple non-advertising advertising sounds intriguing to you, please leave a comment; thanks!

Can We Unify Our Feed Formats?

Thinking about Feeds.

So we have XML, generally. We have RSS 0.91, 1.0, 2.0, we have Atom. Of the aforementioned, I’m currently partial to Atom. This is just after a cursory comparison of the different formats, I could certainly bear to look deeper into them…

However… they are all feeds designed to do pretty much the same thing. That is, they’re similar enough, it ought to be fairly easy to choose one format, and then parse other formats and then re-publish them into the One True Feed Format.

There are challenges with the above approach. Some formats include elements or attributes which don’t have a corresponding equivalent in another format. These could be filled in with default values so as not to lose data.

Still, the problem is: what One True Format do we transform it into? Feed formats don’t seem to inspire quite as heated debates as, say, text editors (vi! emacs!) or operating systems (Linux, various flavours of BSD… let’s not even mention Microsoft), or even Linux package management systems (RPM, deb, portage, etc.). That said, choosing One True Format is certain to tick somebody off, no matter which is chosen.

So, why not sidestep that altogether, and turn all our feeds into YAML? Specifically, into YAML that is also valid JSON?

It could be that this is an idea that was contemplated by souls wiser than I, and already abandoned. Perhaps it’s not easily implemented. Maybe nobody’s interested.

So forget YAML for a moment (though the idea still appeals to me). Standardizing on a single feed type still makes sense. At the same time… I don’t think it’s likely in the near future.

Why?

  • Too many Very Large services have already chosen different formats and don’t seem likely to change. Blogger, IIRC, uses Atom. I believe Six Apart uses RDF, which would be RSS 1.0. Other services support multiple formats, or 2.0, or 0.91.
  • Supporting different formats is fairly low overhead. It takes a little time, but it’s not an extremely difficult prospect for a feed aggregator to add a parser for a different format. They’re all XML. Many features are in common. One person working alone could create parsers for all the various formats in comparatively short order.

In short… it’s just too easy to allow people to keep using their favorite format, and to just parse all of them if we’re building a feed reader. Nobody gets worked up about it, there is no Grand Debate or Holy Feed Crusade.

My own answer to the question asked in the headline? No, probably not. Not any time soon.

On “Metawebs” Past

Of course, “Metaweb” is not a new term, and I’m hoping there’s something better to call this overlay of the web…

Interestingly just noted this use of “Metaweb” in 2003 by Nova Spivak: The Birth of “The Metaweb” — The Next Big Thing — What We are All Really Building.

What was he talking about? RSS, mainly. I think the impact of RSS is still slowly climbing, and isn’t finished yet. Even though RSS is yesterday’s news to many, it’s value has yet to be understood or felt by many, and there’s certainly a case to be made for a term like “Metaweb” to apply to RSS as well.

Anyways; a great article from a time when RSS was still pushing its way in to greater use.

I’d welcome other ideas on what to call the new hyper-overlay of the web instead of “the Metaweb” — as long as it isn’t “Web 3.0″. ;-)

The Metaweb

I’m not sure I’m very good at predicting the Next Big Thing. I mean, when I first heard about Microsoft Windows in 1990, I figured that would be a complete flop*. Yeah. So, there you go.

(* But really, who could blame me?)

Still, I think we can be assured that there will be, at some point, another Next Big Thing. It’s just the actual shape and smell of it that eludes us.

I don’t know if the Metaweb will be the Next Big Thing. But if it isn’t, I think it may be the Next Next Big Thing, or possibly the 3.times(”Next”) Big Thing, or maybe somewhere beyond that. I don’t even know if we’ll call it “the Metaweb”, but at the moment, I don’t know what else to call it.

When I say “Metaweb”, then, what am I talking about? Mainly, I mean a layer of activity and content over the web, interdependent with existing web content. Some possible examples:
Continue reading ‘The Metaweb’

On Flock: Observations After Using Flock As Primary Browser for 2 Weeks

I said awhile ago that I would try Flock out for 2 weeks. That just came to a close, and I have to say, I’m very happy to be using Firefox again.

Now, I did get used to Flock. But it had no features that compelled me to continue using it, and quite a few that dissuaded me from wanting to continue. I took notes as I saw things; as you can see below, I didn’t really find much more to comment on past the 12th. I think by that time I had seen & tried all of Flock’s features that were applicable to me. My observations below:

11-8-07

  • Twitter in the People sidebar doesn’t stay updated; it’s always about 5-10 minutes old. This makes it, effectively, useless; it could use a refresh button, and an option to view replies only.
  • Blog posting tool; works great, but… I like to edit in source code, but with the shortcut buttons provided by the Wordpress editor.
  • CTRL-tab, or opening a window in a new tab, opens right next to your current tab, rather than at the end of the row. There are actually times I wanted this to be an option in FF, but having it do this every time can be annoying. I’d rather have it go to the end of the row by default, and next to my current tab iff I add another key (alt-ctrl-click? Is that taken?).
  • The search bar; in FF you can change the engine on the fly, just go to the drop down and click a different one. In Flock, if you choose another engine, it searches for the input box’s current string, automatically opening the new search page, even if there is an empty string there. To make a different search engine stay up there, you need to actually make that engine the default. :-(

11-9-07

  • Crashed without warning, only 8 tabs open, and none of them should have been very taxing client apps…

11-10-07

  • Already quit using the integrated blog posting tool, I’d rather use the Write page in WP.

11-12-07

  • Hate the way Flock adds Feeds by default, to itself. I use Google Reader; I want RSS items I click to be added to Google Reader. I’m sure flock has an option for this (UPDATE: It does): it should ask you the first time you add a feed what you want to do with them.
  • Have noted that where Flock opens a new tab actually seems to have a bit of randomness to it. I’ve had it open new tabs right beside the current tab; if you continue opening new ones, it sometimes continues opening them to the right of your current tab. Other times, it opens them at the far right, like Firefox. Once, I had it open them to the left of my current tab. There seems to be no rhyme or reason to it; sometimes it does it one way, sometimes another.

I really tried to be objective. I think 2 weeks was sufficient time for Flock to win me over, if the features it had were those I’d really use. Although I’ve expressed how I don’t really care for Flock’s default theme, I came to ignore that pretty quickly once I got used to it — it really doesn’t affect how you use the browser.

But having used it for a couple weeks; I’m done. Back to Firefox. Flock is a fine product, and there may be people for whom it’s combination of features and social networking/web 2.0 integrations are perfect. I’m just not one of those people.

ShiftSpace - An Open Source layer above any webpage

ShiftSpace bills itself as “An Open Source layer above any webpage”. It deserves to be talked about. I’m going to sleep, so I’ll have to talk about it later.

Destroy The Web 2.0 Look

Dovetailing nicely with my appeal for some new cliches, Elliot Jay Stocks of Carsonified recently did a talk called “Destroy The Web 2.0 Look.

Thank you, Mr. Stocks! Excellent presentation. That presentation is suitable for a ChangeThis manifesto, if you ask me.

Personally, I think some of the elements of typical “web 2.0″ design wouldn’t be that bad… if they were not slavishly applied to Every Single New Web Site/Application/doohickey that we see fly off the shelf. But since they are, I think a backlash is long overdue. Vive la revolution! Let’s not reflect a logo, for a change.

Of course, this means that people will need designers to actually design again, rather than just going through all the “2.0″-ish Photoshop tutorials they found on Smashing Magazine or Mashable. Good!

The slide show:

Triggit

I’m trying to be objective. I love startups, and I like seeing all the new ideas, and sometimes the ideas that seems silly to me at first (Twitter was one) really take off. So, I’m trying out something called Triggit.

The elevator pitch is, Triggit is a new way to add images, embed videos, and place Amazon affiliate links on your blog. Technically, I suppose it could be used with any website, but the target is definitely bloggers.

I pretty much dismissed it at first. I mean… putting an image or a YouTube video in a blog post? I need a tool for this?
Continue reading ‘Triggit’

Rethinking The Twitter Shoe

Some changes to my approach:

  • I think I’m going to use the twitter gem, rather than twitter4r. The only reason; it just seems a bit simpler. I may change my mind again. Or you may change your mind.
  • Alternatively, I may just use Net::HTTP — the twitter api seems straight forward, and this would eliminate a dependency.
  • I don’t think this will be a mass consumption tool at any time in the near future. It simply won’t be a 1 or 2 click install, like an AIR application. And really, that’s ok; maybe a Shoes application is supposed to require you to roll up your sleeves and muck about a little bit. Get your hands dirty. Open a command line. Edit a file or two.

So, basically, then, all the shoe has to do is get or post messages to twitter. It will also need to parse XML or JSON, so I suppose I’ll be looking for a gem to make that easier, as well. I’m a big fan of Not Reinventing The Wheel. Stay tuned, padwan.

The Paradox Of LinkedIn At Work

There’s an odd thing I’ve noticed about LinkedIn. As it gets more and more ubiquitous, I have more and more connections to people who I work with. Well, this makes sense — that’s part of the purpose, connecting (and therefore, staying connected in the future) with the people you know, and who know you. Being connected to those who’ve worked with you just makes sense.

What’s odd is, as this occurs, people are invariably connected to their supervisors, and to their supervisor’s supervisor, and so on. I know, that’s still not odd, except:

I think I have yet to see a LinkedIn profile that doesn’t have one or more of:

  • career opportunities
  • consulting offers
  • new ventures
  • job inquiries

listed in the “interested In” category.

Just find this strange because usually, at least in North America, one does not advertise to one’s managers that one is interested in leaving the company.

Granted, it’s also assumed in North America that people will take the best opportunity available, so there is the unspoken assumption that everyone is open to a better offer, if it comes along. Also, since basically everyone includes those points, they eventually become unremarkable.

Has anyone else ever found this strange?