Re: [Standards] Proposed XMPP Extension: File Transfer Thumbnails
On 3/31/09 4:30 PM, Jiří Zárevúcký wrote: > 2009/3/31 Jonathan Schleifer : >> Am 31.03.2009 um 15:45 schrieb Peter Saint-Andre: >> >>> Typically our protocol documents don't specify user interface details >>> like that. >> Hm, ok. But sometimes, it would make sense if a particular feature is >> presented the same way to the user in every client. This looks more >> consistent for the user if two users are using different clients. >> > > It makes sense for some features, but I don't think it's important for > file thumbnails. It can be displayed in a chat window, or it can be > part of a confirmation dialog. There is no difference in > functionality. One is just convenient for some people (but can be > annoying for others). IMHO the whole point of having different clients > is to have different ways of doing things such as this, that suit > different people. Agreed. Peter -- Peter Saint-Andre https://stpeter.im/ smime.p7s Description: S/MIME Cryptographic Signature
Re: [Standards] Proposed XMPP Extension: File Transfer Thumbnails
2009/3/31 Jonathan Schleifer : > Am 31.03.2009 um 15:45 schrieb Peter Saint-Andre: > >> Typically our protocol documents don't specify user interface details >> like that. > > Hm, ok. But sometimes, it would make sense if a particular feature is > presented the same way to the user in every client. This looks more > consistent for the user if two users are using different clients. > It makes sense for some features, but I don't think it's important for file thumbnails. It can be displayed in a chat window, or it can be part of a confirmation dialog. There is no difference in functionality. One is just convenient for some people (but can be annoying for others). IMHO the whole point of having different clients is to have different ways of doing things such as this, that suit different people.
Re: [Standards] Proposed XMPP Extension: File Transfer Thumbnails
> Typically our protocol documents don't specify user interface details > like that. Hm, ok. But sometimes, it would make sense if a particular feature is =20= presented the same way to the user in every client. This looks more =20 consistent for the user if two users are using different clients. I agree with that. Xavier -- http://www.gnu.org http://www.april.org http://www.lolica.org
Re: [Standards] Proposed XMPP Extension: File Transfer Thumbnails
Am 31.03.2009 um 16:10 schrieb Peter Saint-Andre: Making some suggestions seems OK, but I wouldn't want to say that a client MUST do it that way. Sure, I wasn't talking about MUST, but about recommendations ;). I think we already have text like this in XEP-0071 and we can borrow that. (Well, I see that XEP-0071 says only "these are hints only and cannot necessarily be relied upon in determining the size of the image" so that's not really states in security language.) We could also add a yellow warning sign: "/!\ Don't use this to allocate your buffer!" :þ. But this would be too specific I guess. -- Jonathan PGP.sig Description: Signierter Teil der Nachricht
Re: [Standards] Proposed XMPP Extension: File Transfer Thumbnails
On 3/31/09 8:05 AM, Jonathan Schleifer wrote: > Am 31.03.2009 um 15:45 schrieb Peter Saint-Andre: > >> Typically our protocol documents don't specify user interface details >> like that. > > Hm, ok. But sometimes, it would make sense if a particular feature is > presented the same way to the user in every client. This looks more > consistent for the user if two users are using different clients. Making some suggestions seems OK, but I wouldn't want to say that a client MUST do it that way. >>> • Security considerations: We specify width and height, but the client >>> MUST NOT rely on these, otherwise it can lead to security issues. >> >> Good point. > > Maybe a string like "The specified size should only be used as an > approximate to reserve display space where the thumbnail will be > displayed, like in the conversation, but it should NEVER be used as an > indicator how big the thumbnail really is." I think we already have text like this in XEP-0071 and we can borrow that. (Well, I see that XEP-0071 says only "these are hints only and cannot necessarily be relied upon in determining the size of the image" so that's not really states in security language.) Peter -- Peter Saint-Andre https://stpeter.im/ smime.p7s Description: S/MIME Cryptographic Signature
Re: [Standards] Proposed XMPP Extension: File Transfer Thumbnails
Am 31.03.2009 um 15:45 schrieb Peter Saint-Andre: Typically our protocol documents don't specify user interface details like that. Hm, ok. But sometimes, it would make sense if a particular feature is presented the same way to the user in every client. This looks more consistent for the user if two users are using different clients. • Security considerations: We specify width and height, but the client MUST NOT rely on these, otherwise it can lead to security issues. Good point. Maybe a string like "The specified size should only be used as an approximate to reserve display space where the thumbnail will be displayed, like in the conversation, but it should NEVER be used as an indicator how big the thumbnail really is." -- Jonathan PGP.sig Description: Signierter Teil der Nachricht
Re: [Standards] Proposed XMPP Extension: File Transfer Thumbnails
On 3/31/09 2:47 AM, Jonathan Schleifer wrote: > Am 30.03.2009 um 20:39 schrieb XMPP Extensions Editor: > >> The XMPP Extensions Editor has received a proposal for a new XEP. >> >> Title: File Transfer Thumbnails >> >> Abstract: This specification defines a way for a client supply a >> preview image for a file transfer. >> >> URL: http://www.xmpp.org/extensions/inbox/thumbs.html >> >> The XMPP Council will decide at its next meeting whether to accept >> this proposal as an official XEP. > > Nice, this is exactly what I suggested once (show a picture in the chat > window, transfer it when you click it). In fact this is pretty much a modernization of what Kopete does: http://xmpp.org/extensions/inbox/file-preview.html Somehow we never published that one, but the new approach with bits of binary seems like a good idea to me. > Two suggestions though: > > • Specify how the client should handle it. Like show a thumbnail in the > chat window and show start the transfer when you click it. Typically our protocol documents don't specify user interface details like that. > • Security considerations: We specify width and height, but the client > MUST NOT rely on these, otherwise it can lead to security issues. Good point. Peter -- Peter Saint-Andre https://stpeter.im/ smime.p7s Description: S/MIME Cryptographic Signature
Re: [Standards] Proposed XMPP Extension: File Transfer Thumbnails
Am 30.03.2009 um 20:39 schrieb XMPP Extensions Editor: The XMPP Extensions Editor has received a proposal for a new XEP. Title: File Transfer Thumbnails Abstract: This specification defines a way for a client supply a preview image for a file transfer. URL: http://www.xmpp.org/extensions/inbox/thumbs.html The XMPP Council will decide at its next meeting whether to accept this proposal as an official XEP. Nice, this is exactly what I suggested once (show a picture in the chat window, transfer it when you click it). Two suggestions though: • Specify how the client should handle it. Like show a thumbnail in the chat window and show start the transfer when you click it. • Security considerations: We specify width and height, but the client MUST NOT rely on these, otherwise it can lead to security issues. -- Jonathan PGP.sig Description: Signierter Teil der Nachricht
[Standards] Proposed XMPP Extension: File Transfer Thumbnails
The XMPP Extensions Editor has received a proposal for a new XEP. Title: File Transfer Thumbnails Abstract: This specification defines a way for a client supply a preview image for a file transfer. URL: http://www.xmpp.org/extensions/inbox/thumbs.html The XMPP Council will decide at its next meeting whether to accept this proposal as an official XEP.
