On 01/05/2015 21:28, Goffi wrote:
G'day,
Hello goffi,
Sorry I was not replying, I'm quite busy now, but am going to join you
guys ASAP, unfortunately, got a flu now.
In XEP-0277 I have two issues:
1) comments link
In section 3 comments are defined by addind a <link/> to a pubsub item
atom payload (#3.1).
This node can be anywhere, and in the comment node/items, there is not
link to the original item (#3.2).
The issue here is if we discover the comment node without knowing the
original item, there is no way to associate both.
A consequence I can imagine is if the original item is deleted, and the
comments is on an other service, there is no way for the comments pubsub
service admin to know if the original item still exits, so he can't
clean its database properly.
Yes, I am aware of the issue but it can't be fixed before we have a good
way to store XML in the metadata.
2) published/updated
the <published/> and <updated/> elements are given by the publisher, he
can write anything he wants inside. I think that the server should
enforce these data, or we will have the same issues as in email like
mesages in the future (e.g. to appear first).
Yes, I know about this. This was made purposely to make it possible, for
instance, to import old blog posts from different source.
We use this on LiJ to import old posts from juick.com and it works perfect.
Cheers
Goffi
Thanks.
