Hello,
Dne Monday 18 of August 2008 18:48:10 Peter Saint-Andre napsal(a):
> http://dev.jabbim.cz/jdisk
>
> Pavel and I have an action item to write up how this works. I think you
> use standard XEP-0096 to upload files to the server and it stores them
> for you, but I'm not sure how they are retri
Dave Cridland wrote:
On Thu Aug 14 19:03:24 2008, Matthew Wild wrote:
IRC has the concept of invitation-only rooms. Although this isn't
implemented in any MUC server that I know of, today's protocol leaves
the option for implementation open, while this one doesn't.
Why not do what we discussed
Jonathan Schleifer wrote:
Peter Saint-Andre <[EMAIL PROTECTED]> wrote:
How do clients now handle receipt of two invitations (both mediated)?
They show two invitations and give a message that you are already
joined on the second one.
We could add a phrase to the directed MUC invitation like "
Gaston Dombiak wrote:
In XEP-129 I see that you can specify list of jids allowed to get the files.
That would be example 3. In our case for MUC rooms integration the HTTP PUT
was sent to an URL that correlates to a room so we are not using example 3
but letting the room use the list of room occup
In XEP-129 I see that you can specify list of jids allowed to get the files.
That would be example 3. In our case for MUC rooms integration the HTTP PUT
was sent to an URL that correlates to a room so we are not using example 3
but letting the room use the list of room occupants to answer if the fi
In line with the recent creation of several special-purpose,
lower-volume discussion lists (for Jingle, BOSH, social networking,
mobile applications, etc.), I have created two new lists:
[EMAIL PROTECTED] -- discussion about Multi-User Chat, sign up at
http://mail.jabber.org/mailman/listinfo/m
Zenon Kuder jr. wrote:
Dne Monday 18 of August 2008 02:32:48 Pavel Simerda napsal(a):
Looks fine to me, looking forward for Zenek's comments!
Pavel
I'm ok with the current version too. I'll try to poke Jabbim devs about their
potential comments. Also Marcus may add some valuable input from h
Dne Monday 18 of August 2008 02:32:48 Pavel Simerda napsal(a):
> Looks fine to me, looking forward for Zenek's comments!
>
> Pavel
I'm ok with the current version too. I'll try to poke Jabbim devs about their
potential comments. Also Marcus may add some valuable input from his Pidgin
implementat
Peter Saint-Andre <[EMAIL PROTECTED]> wrote:
> How do clients now handle receipt of two invitations (both mediated)?
They show two invitations and give a message that you are already
joined on the second one.
We could add a phrase to the directed MUC invitation like "The directed
invitation shou
On Thu Aug 14 19:03:24 2008, Matthew Wild wrote:
IRC has the concept of invitation-only rooms. Although this isn't
implemented in any MUC server that I know of, today's protocol
leaves
the option for implementation open, while this one doesn't.
Why not do what we discussed in ages past? Leav
Jonathan Schleifer wrote:
Another idea would be to send both, directed and via the server. We'd
just need to find a way to only display that once. Maybe give the
invitation an ID? That way, the invited user will be added to the
members list AND be able to join, even if there's a privacy list
bloc
Another idea would be to send both, directed and via the server. We'd
just need to find a way to only display that once. Maybe give the
invitation an ID? That way, the invited user will be added to the
members list AND be able to join, even if there's a privacy list
blockig the invitation from the
Dave Cridland wrote:
For "real" authentication, you'd want to use SASL between the client and
the MUC service, but if you did this, a rogue server could still
intercept the normal MUC messages. So what you need to do is have
integrity protected and encrypted messages, which effectively means
Jonathan Schleifer wrote:
Peter Saint-Andre <[EMAIL PROTECTED]> wrote:
In fact that's a members-only room, as currently defined in the XEP
(nothing special about ejabberd there). The joining user doesn't
present an invitation, instead the MUC service adds the joining user
to the member list wh
Peter Saint-Andre <[EMAIL PROTECTED]> wrote:
> In fact that's a members-only room, as currently defined in the XEP
> (nothing special about ejabberd there). The joining user doesn't
> present an invitation, instead the MUC service adds the joining user
> to the member list when the invitation is
Jonathan Schleifer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Am 18.08.2008 um 04:20 schrieb Peter Saint-Andre:
Agreed. Members-only rooms seem much more natural than invite-only
rooms, especially because we have authenticated identities.
I think an invite-only room would be i
http://dev.jabbim.cz/jdisk
Pavel and I have an action item to write up how this works. I think you
use standard XEP-0096 to upload files to the server and it stores them
for you, but I'm not sure how they are retrieved.
Gaston Dombiak wrote:
I didn’t assist to the Summit @ Brussels so I lack
I didn't assist to the Summit @ Brussels so I lack a lot of information. Having
said that, What is JabberDisk? Can't we use XEP-129 and may be also XEP-135 for
that goal? We are using XEP-129 for file sharing (in rooms) and since it's
server based it should be possible to hook up a virus scannin
On Mon Aug 18 07:14:00 2008, Johansson Olle E wrote:
18 aug 2008 kl. 04.20 skrev Peter Saint-Andre:
Agreed. Members-only rooms seem much more natural than invite-only
rooms, especially because we have authenticated identities. IRC
doesn't have authentication, so they might need some kind of
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Am 18.08.2008 um 04:20 schrieb Peter Saint-Andre:
Agreed. Members-only rooms seem much more natural than invite-only
rooms, especially because we have authenticated identities.
I think an invite-only room would be interesting for continued
Hi everyone,
I remember we spoke about "JabberDisk" at the last XMPP Summit in
Brussels but I can't found any documentation on it in the xeps or
Jabber wiki. We'd like to share images between multiple xmpp entities,
and we have to check for viruses in the transfered file. As such,
JabberD
21 matches
Mail list logo
