LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  January 2005

CODE4LIB January 2005

Subject:

Re: Individually Customized RSS feeds

From:

Tito Sierra <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Mon, 31 Jan 2005 14:50:53 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (105 lines)

One approach that has been used to provide "private" RSS feeds without
username/password style authentication is to use a unique token string
for each personalized feed.  In this system each user/feed instance is
assigned a unique auto-generated token string that makes up the
important part of the feed's URL.  This is how the folks behind
Basecamp project management software (http://www.basecamphq.com/)
handle their custom RSS feeds for projects.

Unfortunately this style of authentication doesn't prevent someone else
from accessing your feed's contents if they get ahold of the URL
containing the token string.  The presumption is that the feed URL is
only displayed to the user after they have authenticated to their
account.  Additionally, a burden is placed on the user to not share
their feed URLs or expose them to web-based aggregators such as
Bloglines.  For users of desktop aggregators the token-approach
provides a little more privacy then feeds that use a more easily
obtainable user_id as part of the feed URL.

Of course for truly sensitive information you wouldn't even want to
even go there.

Tito Sierra
NCSU Libraries

On Jan 31, 2005, at 1:11 PM, Binkley, Peter wrote:

> My impression is that the better class of desktop RSS readers can
> handle
> a feed that comes in with http authentication over an https connection,
> but that the web-based readers (such as Bloglines) can't at the moment.
>
> The problem would be that you'd have to trust a remote web service with
> your id and password (or else reenter them every time you accessed
> Bloglines). We've built an RSS feed that presents everything on your
> Sirsi MyAccount page (charged items, fines, holds) in the form of an
> RSS
> feed, using Cocoon's screen-scraping functions. This makes it easy to
> embed your barcode and pin in the url - not exactly secure, but not
> much
> less secure than sending the barcode and pin in clear text over http,
> which is what happens when you access the native Sirsi MyAccount page.
>
> But what if you put this in your Bloglines account? It becomes part of
> their social-bookmarking world, so the books I've signed out become
> searchable ... So we haven't rolled this out, we're still thinking
> about
> it. We also have an http-authenticated https proxy page in front of
> Cocoon that we can use, but we haven't decided what to do with all
> this.
>
> Peter
>
>
>> -----Original Message-----
>> From: Code for Libraries [mailto:[log in to unmask]] On
>> Behalf Of Walter Lewis
>> Sent: Friday, January 28, 2005 08:15 PM
>> To: [log in to unmask]
>> Subject: Re: [CODE4LIB] Individually Customized RSS feeds
>>
>> Edward Iglesias wrote:
>>> Well there have been some postings recently on SIRSI adopting RSS
>>> technology.  See
>>>
>> http://www.theshiftedlibrarian.com/archives/2005/01/19/sirsi_breaks_op
>>> en_the_rss_flood_gates.html
>>>
>>> Eric Lease Morgan wrote:>
>>>> If I understand the concept, I have tried to do this as a
>> part of the
>>>> (incomplete) Ockham Alerting Service. The Service allows
>> you to query
>>>> an index, and the search results are then available as
>> HTML, email,
>>>> or an RSS feed. When the content in the index gets
>> refreshed, the RSS
>>>> feed will return different results every time. The operative word
>>>> here is "when". See:>>
>>>>   http://alert.ockham.org/
>>
>> I think I *get* the notion of search results as RSS feed.
>> And I respect Eric's "when" qualifier.  I even like some of
>> the things being suggested in the SIRSI announcement and
>> discussion posted on Shifted Librarian.
>>
>> What I was particularly thinking of was stuff that we would,
>> in the pre-Spam/phish era of email, have only considered
>> emailing (and, in many cases, still do of course):
>>         hold notifications
>>         overdue notifications
>>         profile based SDI reports (e.g. new books or articles in *)
>>         targeted announcements (by location, status, etc.)
>> When dealing with individual patrons, I'm assuming that we
>> need to authenticate in order to respect (or at least
>> acknowledge) their right to privacy. (how much privacy with
>> email is a different thread)
>>
>> Could any/many of the different classes of RSS readers deal
>> with a standard web authentication scheme? standalone?
>> embedded in email clients? embedded in browsers?
>>
>> Walter Lewis
>> Halton Hills
>>
>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager