Writing Comments, Get Profile "About", avatar Data, RSS feed

[Jode...@gmail.com]

We would like to use the Digg API to:
1. collect user Digg comments on a story on our site and send the
comment back to include in the users Digg profile.
2. Get a Digg user's "about", avatar and contact info data
3. Build an RSS feed for a user
Cant see that any of this is currently supported?

[Steve Williams]

At 06:29 AM 6/25/2008, Jode...@gmail.com wrote:
>We would like to use the Digg API to:
>1. collect user Digg comments on a story on our site and send the
>comment back to include in the users Digg profile.

We're working on OAuth authentication and read/write access via the API.

>2. Get a Digg user's "about", avatar and contact info data

Is the "avatar" the image referred to in the API as the user's
"icon"? If so, that's available as a property in each user element.

When you say "about," I believe you are referring to the "About Me"
text in each user's profile. That's a great suggestion. I think we
might add that as a sub-element of the user element. HOWEVER, please
note that the user element appears in many API responses, so we try
to keep it small. The "About Me" text would probably be included
only in response to requests for an individual user, i.e.
/user/{username}. Would that be sufficient?

As for "contact info," please be more specific? As you can imagine,
we're pretty careful about disclosing the user's email address. We
MIGHT make the user's profile read/write via the API with OAuth, but
I can't say for sure yet. It would help in our planning if we can
understand exactly what you need.

(Digg plans to be an OpenID consumer before we are an OpenID
provider, but does your request overlap with OpenID profile exchange?)

>3. Build an RSS feed for a user

Any particular RSS feed? Submissions? Diggs? Comments? A combined
view? You can generate each of those RSS URLs from the profile URL
in the List Users response--again only for /user/{username}. Just
observe the URL pattern and apply it. Or is that not sufficient?

[Jode...@gmail.com]

Steve,
Steve,

Thanks for being so responsive.

1. Look fwd to write API when available

2. Avatar - thanks now see the png. "About" - Yes individual user
request is perfect. Contact info - agree email is private, other
data like location, gender, birthdate (or age) is usually public and
would be good to get. Yes OpenID profile exch works for us too.

3. Build an RSS feed - thanks, realised after sending the message,
syntax is easy to build.

Cheers

On Jun 26, 1:04 am, Steve Williams <s...@digg.com> wrote:

[Steve Williams]

At 01:27 AM 6/26/2008, Jode...@gmail.com wrote:
>Contact info - agree email is private, other data like location,

>gender, birthdate (or age) is usually public ...

Actually, we've had a ticket open for that since last September. I
bumped up its priority.

It'll be based on permissions set by each user, same as the
visibility of these data on the web site.