- It's not generic; it's only for blogging. Retracting items after a delay
should be a generic feature.

I think it's only for media, blogging isn't allowed.

Though I agree with what was said in council that multiple media should be allowed to do "slideshow" style stories.

Yes the Stories XEP enforce one media per item, but automatic retractation as a generic Pubsub node configuration could be useful on a more global level.

Once we have pubsub#expire I think the Stories XEP will mention it as a SHOULD, leaving the freedom of the developer, and user, to define it or note.

It could also be used for other PEP nodes, for example User Location or User Tune.

However I'm opposed by the idea of multiple medias, how the Stories are handled in all the implementations I know (Instagram, Snapchat, Telegram, Signal) is that each Story has one media attached and the client is actually taking care of "grouping" all the recent Stories of one user as a slideshow. All the implementations above have the following behavior: tap right to go to the next story of the user or the next user story if there's none left, swipe right to directly jump to the next user.

In the Telegram API for example: https://core.telegram.org/api/stories :

media: The story media (a vertical photo or a vertical video, max 30 MB).

Handling multiple medias per Story AND multiple Stories at the same time will be very confusing in the UI.

If you want to have several images in your Story a few of those implementations allow you to craft a unique image with a "collage" of several images (they are called Layout on Instagram). This is something that I might consider to do on my side.

Combine multiple photos into one on your Instagram story

https://help.instagram.com/385953178139846/?helpref=platform_switcher&cms_platform=android-app&cms_id=385953178139846

I hope that you'll understand my feedback, I'd like to keep things very simple but this limitation is really the bare minimum to have a coherent flow and implementation in the clients.

Regards,

edhelas

- 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.

I think all mention of retraction could be removed. It's not the point of the XEP and I think it distracts from the purpose. If clients want to hide after eg 24 hours that's up to them and their UX desires.

_______________________________________________
Standards mailing list -- standards@xmpp.org
To unsubscribe send an email to standards-leave@xmpp.org