Am Donnerstag, den 19.11.2020, 18:10 +0500 schrieb Andrew Nenakhov: > So of course, we use HTTP > for hosting sticker packs and stickers themselves, and any client on > any OS can *easily* import any image by their URIs. This way clients > do not need to use pubsub or anything, just use the links, super > easy. > Also, this model makes updating the pack more easy. > > Beyond that, we've actually come to understanding that single-connect > model is fundamentally broken and stands in the way of good, and have > rather successfully implemented multiple streams into clients. So > loading dreaded presences and new messages come in the main stream, > where you post presence, and loading an archive for specific > conversations happens in another. Fetching list of group chat members > happens in another, etc. On iOS (and on Android too, actually) it is > almost always faster to open a new stream and fetch only the required > data, than to load everything on the only stream. This makes > interfaces far more responsive, and, among other things, makes stream > management unnecessary. > I think you are just reinventing matrix protocol. If xmpp is so non- usable on apple devices why bother making non-interoperable protocol (or client) when there's is already what you'll likely end up with. Just make a protocol gate to xmpp if you still want to support that.
--rr _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
