Hi edhelas, thanks for your feedback Le mercredi 2 novembre 2022, 13:21:01 CET Timothée Jaussoin a écrit :
> I think its still valuable in some cases, especially for compatibility > with external tools that wants to import/export Atom items also I'd > prefer to not break any compatibility with Atom. I agree about maintaining compatibility, as long as we are based on Atom, we have to keep this text version, even if it's using bandwidth for nothing. > > - what is this "Gallery profile" thing ? It looks like a terrible way to do > > photo galleries, ignoring all the work done by stuff like XEP-0447. Please, I > > see no good reason to have this. > > The goal is not to replace or have "two-standards". This Gallery profile > is a way to ensure that the node is having at least one attached picture > to all the items, allowing clients to display it using a specific layout > (a grid for example). This would allow to have Picture based social > feeds such as Instagram etc... I still don't think that it's a good way to do this: here images are just http links, while with XEP-0447 we can associate links and/or jingle and/or whatever with all metadata and thumbnails needed, and it's possible to add a way to link a blog post to images. > The goal of this XEP is to pose the bases of "what is a social feed" in > XMPP and the core of it relies on pubsub#type (I asked the support in > ejabberd there by the way > https://github.com/processone/ejabberd/issues/3914). > > The idea would be next to add a few more XEPs to define maybe other > pubsub#type from that one and to see how they can be handled > client/server side. For example we are thinking of adding pubsub#type > based filters in Pubsub services. That would allow clients to only get > the main article-nodes, comment-nodes, galleries-nodes etc... based on > their preferences and not retrieve everything and then filter client > side (it is one of the big performances issues that I have right now). 'pubsub#type' would be "http://www.w3.org/2005/Atom"; in any case here, I don't see how you would use it to get comment nodes or gallery node. You would have to add an other metadata for that (which can be done). Regarding comment nodes, I think that to do it properly we should fix pubsub collections and put blog + comments nodes in the same collection. Using filters and prefixes for nodes is really ugly workaround, and we can end-up with comments node persisting while a parent blog has been deleted. > > Regarding the link with XEP-0447: Stateless file sharing I don't see why > <file-sharing> can't be used with this XEP. I can try to adapt the > 'urn:xmpp:gallery:0' to gives the choice of the implementer on how he > would like to attach this mandatory picture per item (having two > examples, one with a '<link rel=enclosure/>' and another one with > '<file-sharing xmlns=urn:xmpp:sfs:0>' for example :) ). Then you would be mixing atom and XEPs material, it doesn't feel right. I believe that we need a proper protoXEP to handle photo galleries, probably something like XEP-0214 but with XEP-0447 payloads instead. I don't really like this gallery thing because it will set an ill-conceived precedent and when we come up with a proper photo gallery protoXEP, we'll end- up with 2 competing specifications (which is the plague of XMPP). > > Movim has been for more than 10 years in a weird state where I was > mostly based on 0277 with "hacks" to extend it outside this scope of > Microblog. Despite its name, XEP-0277 supports normal blogging and blogs outside of PEP out of the box, no need for a new XEP for that. > This XEP is a step ensuring that everything that is done is > fully standard and setting the bases of some future extensions in that area. what is done currently is standard XEP-0277. But whatever, I'm not against a new XEP with some extra stuff like node configuration etc. However, 'pubsub#type' is not specified in XEP-0060 (only seen in examples), and it should get the namespace of the item payload, i.e. "http://www.w3.org/ 2005/Atom" in our case, so you should use (create?) an other metadata field to handle "profiles". Also, your proposal is using verbatim stuff from XEP-0277, I believe that original XEP-0277 authors should be quoted somewhere inside your specification. King Regards Goffi _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
