[Standards] microblogging maintainer :)
stpeter at stpeter.im
Mon Feb 14 15:06:09 UTC 2011
Resurrecting an old thread...
On 12/20/10 1:39 PM, Simon Tennant (buddycloud) wrote:
> On 20/12/2010 19:01, Thomas Baquet wrote:
>> Okay, so let's take the Atom way then: when a node allows a write
>> access to user, it means he can post reply to items on it. But there
>> stills a problem: imagine than - in a more general way - I post an
>> blog article on my "blog" node; how will I manage wether people will
>> effectively post a reply to this article or when they will post an
>> article which is not a reply? For certain kind of content allowing
>> people post in my node item which are not necesseraly item can be
>> useful (like facebook wall), but others no.
> It would really help if we had some concrete examples of what features
> and use-cases this spec is trying to support?
> We all have different ideas of what micro-blogging means means and
> arbitrarily hammering out a spec without some predefined use cases and
> users stories is spec-masturbation: fun, but rather pointless.
> It may well be worth leaving this spec as nothing more than "publish to
> a node" (pep or pubsub) and "use atom payloads".
But how useful is that?
> Trying to define anything more than that, like the business logic of who
> can reply to what is really the role of an implementer and depends on
> the type of community they are building their application for.
That seems to be true.
> If people want to define more then implement an application and see how
> users use it and adjust accordingly.
> I would really like this stuff all standardised based on how buddycloud
> users have used channels, but even then I think that going more detailed
> is really constraining (and with little benefit).
My sense from discussions in Brussels (although we never had a good,
dedicated chat about microblogging -- at least not one that I was
involved with) is that it's still time for experimentation, not
standardization. That is, as Simon pointed out above, "we all have
different ideas of what microblogging means". So perhaps XEP-0277 is
either too early or too late, depending on your perspective...
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 6105 bytes
Desc: S/MIME Cryptographic Signature
More information about the Standards