On Nov 6, 6:55 pm, Jeff Scudder <j... google.com> wrote:
> In your last post you asked about a time line, but I'm
> afraid I can't commit to one just yet. At this point
I'm not 100%
> certain that this is something that we will change.
There are reasons
> for allowing arbitrary names for the author and reasons
for basing the
> author name on your credentials, so it is something we
will have to
> discuss. I think I know which way you would vote
Ah, thanks for categorizing my issue then
Is it possible to give me a possible 'functional' reason,
seen from
the user's point of view, against allowing to set the author
field in
a comment entry? Or is it strictly a security/prvacy issue?
I'm just
interested what possible motivations could be.
Because the way I see it, why would anyone want to use the
Blogger API
to add comment entries to his posts, if it's not possible to
set the
author field? I thought goal of the API is to offer an
interface to
have access to methods so that you can use the data *and*
functionality of Blogger?
Thanks again for your time, Jeff.
Maarten
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Blogger Data API" group.
To post to this group, send email to bloggerDev googlegroups.com
To unsubscribe from this group, send email to
bloggerDev-unsubscribe googlegroups.com
For more options, visit this group at http:
//groups.google.com/group/bloggerDev?hl=en
-~----------~----~----~----~------~----~------~--~---
|