From: http://pylistc.jabberstudio.org/, Warning:
> I am not really a developper so PyListC is really amateur work. It should > only be seen as a proof of concept. If enough people are interested in a > mailing-list like feature as provided by PyListC, it should be better to > write a JEP to use Pubsub to manage lists. However, as few jabber servers > currently offer pubsub services and the JEP should be implemented in every > clients, PyListC may fill the void for some time... So PyListC is here till everyone implements pubsub... I think perhaps it would be a cool idea to spilt PyListC into two parts: - a pure pubsub server - a magic interface layer that lets clients that don't understand pubsub use the pubsub service. That way you could use PyListC to sign up on other pubsub services when they become available, and _that_ would be a killer usage of PyListC! (kinda like rss.jabber.ru does rss feeds) On 11/18/05, Pedro Melo <[EMAIL PROTECTED]> wrote: > Hi, > > On Nov 17, 2005, at 8:35 PM, Lavanant Etienne wrote: > > > It provides Jabber with a mailing-list like feature. I hope some > > people will be interested in this feature. Anyway, the jabberstudio > > page for the project is : > > http://jabberstudio.org/projects/pylistc/project/view.php > > This seems to be very similiar to a chatroom... Check JEP-0045... > Also, you could probably implement this on top of JEP-0060, pubsub. > > I'm not saying that I don't like it, I'm just saying I don't get it :). > > Best regards, > -- > HIId: Pedro Melo > SMTP: [EMAIL PROTECTED] > XMPP: [EMAIL PROTECTED] > > _______________________________________________ > py-transports mailing list > py-transports@blathersource.org > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports > -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ From [EMAIL PROTECTED] Fri Nov 18 12:10:21 2005 From: [EMAIL PROTECTED] (Andreas van Cranenburgh) Date: Fri Nov 18 12:10:25 2005 Subject: [py-transports] New Python component available : PyListC In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> On Fri, Nov 18, 2005 at 01:50:55PM +0200, Norman Rasmussen wrote: > From: http://pylistc.jabberstudio.org/, Warning: > > > I am not really a developper so PyListC is really amateur work. It > > should only be seen as a proof of concept. If enough people are > > interested in a mailing-list like feature as provided by PyListC, it > > should be better to write a JEP to use Pubsub to manage lists. > > However, as few jabber servers currently offer pubsub services and > > the JEP should be implemented in every clients, PyListC may fill the > > void for some time... > So PyListC is here till everyone implements pubsub... I think perhaps > it would be a cool idea to spilt PyListC into two parts: > - a pure pubsub server > - a magic interface layer that lets clients that don't understand > pubsub use the pubsub service. > > That way you could use PyListC to sign up on other pubsub services > when they become available, and _that_ would be a killer usage of > PyListC! (kinda like rss.jabber.ru does rss feeds) +1 In more general terms you might say: let's do MVC. Right? (Model View Controller, see wikipedia etc.) -- Andreas [ http://unstable.nl | xmpp:[EMAIL PROTECTED] ] [ callto:ils.seconix.com/[EMAIL PROTECTED] ] -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://modevia.com/pipermail/py-transports/attachments/20051118/912f50cb/attachment.pgp From [EMAIL PROTECTED] Fri Nov 18 12:23:02 2005 From: [EMAIL PROTECTED] (Andreas van Cranenburgh) Date: Fri Nov 18 12:23:06 2005 Subject: [py-transports] New Python component available : PyListC In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> On Thu, Nov 17, 2005 at 09:35:15PM +0100, Lavanant Etienne wrote: > Hi everybody, > just a few words to tell you that I released today a new Python > component called PyListC for Python List Component. It is not a > gateway to an other protocol but it is made out of the code of > PyMSNt-0.9.3. > > It provides Jabber with a mailing-list like feature. I hope some > people will be interested in this feature. Anyway, the jabberstudio > page for the project is : > http://jabberstudio.org/projects/pylistc/project/view.php <copy-paste> Requires cookies This site requires cookies to be enabled in your browser. Please check your preferences/settings and try again. </copy-paste> suddenly I remember why I wasn't planning on hosting anything on jabberstudio. either way, do you also have a homepage? I prefer those to project pages, anyway. [background: I use privoxy to block certain cookies, and this was with elinks which doesn't do much javascript, cause I'm not graphical atm]. > It is a very basic list component for now but I released it early on > purpose so that I could receive feedbacks on the code, how the > component works, etc. So if you have anything to tell me about the > component, feel free to post on this list or to contact me on Jabber. I'd love to see the code and comment. I proposed a list-in-jabber feature numerous times. Though I had, initially, a read-only style in mind, which maps better to RSS and PubSub, maybe? The many-to-many nature of transports maps great to mailing lists (or vice versa). But I'm sure PubSub proponents will now flame me for all these statements I make, I can't make hard arguments for them, and I haven't studied PubSub properly yet!. (Waiting to be convinced by implementations, waiting to see them in my favourite apps etc.) > Thanks to James Burton for his great work on PyMSNt. Yeah, and thank you for the initiative! It's cool to see his codebase can be so generally useful :) But I guess that's also very much thanks to Twisted itself, that it's a whole framework etc. -- Andreas [ http://unstable.nl | xmpp:[EMAIL PROTECTED] ] [ callto:ils.seconix.com/[EMAIL PROTECTED] ] -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://modevia.com/pipermail/py-transports/attachments/20051118/1fd6d026/attachment.pgp From [EMAIL PROTECTED] Fri Nov 18 12:35:07 2005 From: [EMAIL PROTECTED] (Etienne LAVANANT) Date: Fri Nov 18 12:35:15 2005 Subject: [py-transports] New Python component available : PyListC In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> > Hi, > > On Nov 17, 2005, at 8:35 PM, Lavanant Etienne wrote: > > > It provides Jabber with a mailing-list like feature. I hope some > > people will be interested in this feature. Anyway, the jabberstudio > > page for the project is : > > http://jabberstudio.org/projects/pylistc/project/view.php > > This seems to be very similiar to a chatroom... Check JEP-0045... > Also, you could probably implement this on top of JEP-0060, pubsub. > > I'm not saying that I don't like it, I'm just saying I don't get it :). It is true that functionnality is close to a MUC room but user interface is very different so usages will be very different. It is exactly the same as IRC vs mailing-lists : they both allow to communicate with several people all interested in the same topic and those people do not have to know everybody to communicate. However, if you want to be informed of the last great product of company X, you would prefer subscribing to a mailing list rather than joining an IRC room waiting for an annoucement. If you want to have a very interactive chat with a group of friends you would prefer joining them on an IRC room rather than communicate with them thanks to a mailing list. I think those tools (MUC+PyListC or IRC+mailing-list) complement each other and one tool was missing in the Jabber world. -- Tiennou ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From [EMAIL PROTECTED] Fri Nov 18 12:48:33 2005 From: [EMAIL PROTECTED] (Etienne LAVANANT) Date: Fri Nov 18 12:48:37 2005 Subject: [py-transports] New Python component available : PyListC In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> > From: http://pylistc.jabberstudio.org/, Warning: > > > I am not really a developper so PyListC is really amateur work. It should > only be seen as a proof of concept. If enough people are interested in a > mailing-list like feature as provided by PyListC, it should be better to > write a JEP to use Pubsub to manage lists. However, as few jabber servers > currently offer pubsub services and the JEP should be implemented in every > clients, PyListC may fill the void for some time... > > So PyListC is here till everyone implements pubsub... I think perhaps > it would be a cool idea to spilt PyListC into two parts: > - a pure pubsub server > - a magic interface layer that lets clients that don't understand > pubsub use the pubsub service. > The interface layer was my original idea but I started the project over to the beginning to implement it the way it is now (component manage lists and users by itself). I did it the way it is now because I could not get every pubsub functionnalities I wanted in current pubsub implementations, because I eventually made out that it was easier to make it as a standalone component and because it gave me more freedom to implement additionnal functionnalities without having to wait for pubsub to support them (or support them the way I want). However, I agree it would be an interesting step between the standalone component stage and the direct communication between clients and pubsub stage. It is just too early to do that right now but it is definitely a MUST HAVE if a list diffusion JEP appears. -- Tiennou ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From [EMAIL PROTECTED] Fri Nov 18 12:50:42 2005 From: [EMAIL PROTECTED] (Daniel Henninger) Date: Fri Nov 18 12:50:48 2005 Subject: [py-transports] JID of MUC room way too long :P In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Quite frankly, the length doesn't bother me in the slightest. If we change it, that means I get to spend my time running around catching and fixing all of the places in which it's published. Everything in the jabber world is longish. =) Hell, my AIM chatrooms, on my server, will end up being: chatrooms.aim.jabber.vorpalcloud.org ;D I'm just happy that we have a real place to host it, not my personal server. =) It's already moved once, I don't want to start a trend of a moving target. Daniel On Nov 18, 2005, at 5:47 AM, Andreas van Cranenburgh wrote: > On Thu, Nov 17, 2005 at 12:34:28PM -0600, Aaron Axelsen wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Sorry guys, we had to take the server down for an emergency reboot. >> It is back up and running now. The chatroom is once again available >> at: [EMAIL PROTECTED] > > I can't stand it, how can you make this so unnecessarily long? It's > not > at all human-remember-able: > > - pytransports: it's py-transports here, Py*t there, py*-t there, etc! > - conference: it's long. eg "conf" or "muc" would do. > - jabber: unnecessary, but ok. some people want a seperate > namespace for > jabber, because it looks like e-mail. > etc. > > I propose a stable, short and final MUC room. Where people will > actually > chat. Heh. :) > > Maybe someone (eg. me) can run a virtualhost for blathersource.org? > This would look very official: [EMAIL PROTECTED] :) > > Does anyone agree? Ok heh, this is a really trivial matter :) > > -- > Andreas [ http://unstable.nl | > xmpp:[EMAIL PROTECTED] ] > [ callto:ils.seconix.com/ > [EMAIL PROTECTED] ] > _______________________________________________ > py-transports mailing list > py-transports@blathersource.org > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
