Hi again, Holger Weiß just told me that there is already a pubsub#item_expire feature in 0060 and that it is implemented in ejabberd already (https://github.com/processone/ejabberd/commit/29dcc9b94ccfd514cf388979e7210d...). I completely overlooked that. So I propose that I update my proposal with another PR that will mention this as a SHOULD in the Stories node configuration and update my implementation to rely on that. Regards, edhelas Le 17/12/2024 à 18:37, Timothée Jaussoin a écrit :
Hi !
I'm ok to move the retractation thing in a specific XEP, indeed it would take a bit more effort to have it as a server feature and I didn't wanted to block the whole process.
Once something like a pubsub#expire node configuration exist we could upgrade again the Stories XEP to rely on it.
For now the current Stories XEP will define a new kind of node where "Stories like" content will be there, allowing the clients to configure their UX/UI properly.
Regards,
edhelas
Le 17/12/2024 à 18:21, Goffi a écrit :
Le mardi 17 décembre 2024, 15:56:42 heure normale d’Europe centrale Daniel Gultsch a écrit :
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: Pubsub Stories Abstract: This specification defines a way of publishing Stories over XMPP.
URL: https://xmpp.org/extensions/inbox/stories.html
The Council will decide in the next two weeks whether to accept this proposal as an official XEP. _______________________________________________ Standards mailing list -- standards@xmpp.org To unsubscribe send an email to standards-leave@xmpp.org
Hi Edhelas,
Thank you for your contribution.
I've voted +0 on this one, so I'm not blocking it but I'm not pushing either. I want to explain why here.
I think this feature is popular and thus likely useful and desirable. However, I have some issues with the design of this specification:
- It's not generic; it's only for blogging. Retracting items after a delay should be a generic feature. - The delay is vague and should be specified. Ideally, it should be possible to customize the delay, with a reasonable value set by default. - The retraction is done by the client, which is my major concern: if the client doesn't connect (or connects much later), items won't be retracted. The retraction should be handled by the Pubsub service.
While I appreciate the stories profile, I believe the retraction design isn't quite right.
I suggest that we completely remove this retraction feature from this specification and move it to a new one. This new spec should use a well-known node configuration to remove items after a customizable amount of time (or at a specific date and time). We can add a fallback asking the publishing client to retract items if the service doesn't support this config option. This way, we have a clean and generic method for item retraction.
What are your thoughts?
Best, Goffi
_______________________________________________ Standards mailing list -- standards@xmpp.org To unsubscribe send an email to standards-leave@xmpp.org
Standards mailing list -- standards@xmpp.org To unsubscribe send an email to standards-leave@xmpp.org