Jefferson Ogata wrote:
On 2006-07-19 15:49, Peter Saint-Andre wrote:
The question is not whether certain organizations need this, the
question is how to best do this in XMPP. IMHO we have two alternatives:
1. A new, optional attribute in the stream header. This informs the
receiving party of
[EMAIL PROTECTED] wrote:
I see the need for your feature requests.
I presume if users go through any provisioning steps to register an
account with your service than that would be one place for such a
disclaimer.
If you permit in-band account registration, the welcome message could be
On Wednesday 19 July 2006 18:46, Benjamin Podszun wrote:
Please - don't mix banners with braindead and completely useless eMail
signatures.. These disclaimers you are probably talking about are
largely deemed irrelevant and I've yet to find one that really contains
anything worth the
On 2006-07-19 12:32, Tobias Markmann wrote:
You can put that kind of information, disclaimer, TOS, etc., in the
registration form which your server returns to the client which is going
to create a account. If that isn't supported the server can just provide
Off-Band Registration where the user
Jefferson Ogata wrote:
Again, the requirement is that this occur before authentication.
Look at how FTP, ssh2, or rsync do it. Really, it is an oversight that
this is not currently built in to XMPP; it's trivial to define an
attribute or element at the beginning of the stream element to
On 7/19/06, Jefferson Ogata [EMAIL PROTECTED] wrote:
Look at how FTP, ssh2, or rsync do it. Really, it is an oversight that
this is not currently built in to XMPP; it's trivial to define an
attribute or element at the beginning of the stream element to handle
this. It's a matter of specifying
On Wed Jul 19 19:55:06 2006, Hal Rottenberg wrote:
Is what you are asking a valid concern and a good idea? Yes, I
agree
there. What I don't want to see is putting any new requirements on
the clients if that can be avoided. Putting it on servers is a
better
idea. I'll leave the question of
On 2006-07-19 18:55, Hal Rottenberg wrote:
Let me expand on the reasons for my first reply (which re-reading I
see it looks a bit antagonistic which I didn't intend).
I dig.
I don't see this as an oversight necessarily. You are comparing
apples and oranges when you bring SSH and such back
Is there any provision in XMPP or JEPs for service banners? By this I
mean proper banners such as are supported by ssh2, as well as
traditional protocols such as FTP and telnet. A requirement is that the
banner be presented to the user before authentication. An MOTD doesn't
qualify here.
--
On 7/18/06, Jefferson Ogata [EMAIL PROTECTED] wrote:
Is there any provision in XMPP or JEPs for service banners? By this I
mean proper banners such as are supported by ssh2, as well as
traditional protocols such as FTP and telnet. A requirement is that the
banner be presented to the user before
Hal Rottenberg wrote:
On 7/18/06, Jefferson Ogata [EMAIL PROTECTED] wrote:
Is there any provision in XMPP or JEPs for service banners? By this I
mean proper banners such as are supported by ssh2, as well as
traditional protocols such as FTP and telnet. A requirement is that the
banner be
On 2006-07-19 02:00, Hal Rottenberg wrote:
On 7/18/06, Jefferson Ogata [EMAIL PROTECTED] wrote:
Is there any provision in XMPP or JEPs for service banners? By this I
mean proper banners such as are supported by ssh2, as well as
traditional protocols such as FTP and telnet. A requirement is
I see the need for your feature requests.I presume if users go through any provisioning steps to register an account with your service than that would be one place for such a disclaimer. If you permit in-band account registration, the welcome message could be another place.If you need to remind
13 matches
Mail list logo
