W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2013

Re: [whatwg] IRC and WWW integration proposal

From: Jonathan Garbee <jonathan@garbee.me>
Date: Sun, 17 Feb 2013 17:56:29 -0500
Message-ID: <CANQy2y0cK4DWv43qhk_=Br6=HuBHy8MpUJQzN1XU=sNLeueJsw@mail.gmail.com>
To: WhatWG Maling List <whatwg@lists.whatwg.org>
I'll actually follow up my last post with this.

Is there any scenario where something can be done with these changes, or
any one of them, that today isn't possible with the current specifications?
I simply don't see one myself. If you could give a scenario, then could you
possibly make an example page and write a polyfill that would show the
use-case? It may help us better understand any other use-case that is
currently not possible and show us what functionality to look at in order
to create something for the (a?) spec that would work.


On Sun, Feb 17, 2013 at 4:10 PM, Jonathan Garbee <jonathan@garbee.me> wrote:

> Usecase 1: This can already be covered by having the bot/engine look for
> an irc protocol link on the page.
>
> Usecase 2 part one: Operating systems already do this. They see an irc://
> protocol and ask what to open it with or use their already assigned option.
> No need for a browser to take this over.
>
> Usecase 2 part two: Most browsers offer extension platforms, someone can
> easily create one to look for irc:// links and display something based on
> that.
>
> I personally am not seeing any major benefit by having the proposed
> additions added into spec(s). Just more work for developers both on
> browsers and websites if they chose to support this.
>
> -Garbee
>
>
>
>>   Usecase 1: I search for python and see a link to their website in
>> search results, and the search engine looks up both title and IRC info - so
>> I see webpage title, and a link to its irc network or channel.
>>   Usecase 2: Browsers implement some interface to display IRC channel
>> link or window when user visits a page. Advantages:
>>   - The websites will benefit from this and will not have to manually
>> embed qwebirc or Mibbit instances into their webpages anymore[1], leaving
>> the IRC client preference to the user (choose from locally installed
>> clients, or a client provided by the website).
>>   - User would not have to skim a page of text to locate and click an
>> irc:// link manually, as such links would be a part of browser interface
>> (an IRC icon like RSS feed icon?).
>>
>>
>
Received on Sunday, 17 February 2013 22:57:00 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:19 UTC