[Psi-devel] Feature request: Group chat history

There's currently no logging of group chat conversations, is this
being planned for 0.12?

--

-- 
- Norman Rasmussen
 - Email: norman@...
 - Home page: http://norman.rasmussen.co.za/

Re: [Psi-devel] Feature request: Group chat history

On 1 Nov 2007, at 13:29, Norman Rasmussen wrote:
> There's currently no logging of group chat conversations, is this
> being planned for 0.12?

The only two things planned for certain for 0.12 are tabbed muc and  
roster search. Other things will happen, or not, depending on if  
anyone codes them in time.

/K

Feature request: Handling of im: URIs

Hi there!

Since there seems to be a rather short development phase planned for
0.12 I'd like to express my hopes that maybe the handling of im: URIs
might make it into that release.

I believe that permanent, irc-like group chats are one of the killer
features of Jabber that set it a side from other instant messaging
networks. IRC is a nice thing, but we all now, that it's mostly for
geeks. I think, that Jabber has the potential to bring IRC goodness to
the mere mortal.  That's why I would regard the handling of im: URIs
as an important feature to have.

I remember discussing this briefly on the Psi Groupchat a while ago and
one of the devs mentioning, that he has already some code for that
sitting in his development branch. So here is hoping, that this code
might make it into 0.12! 

Regards!

Jan

Re: Feature request: Handling of im: URIs

Jan Vornberger wrote:
> Hi there!
> 
> Since there seems to be a rather short development phase planned for
> 0.12 I'd like to express my hopes that maybe the handling of im: URIs
> might make it into that release.

It's required by RFC 3921, too. :)

> I believe that permanent, irc-like group chats are one of the killer
> features of Jabber that set it a side from other instant messaging
> networks. IRC is a nice thing, but we all now, that it's mostly for
> geeks. I think, that Jabber has the potential to bring IRC goodness to
> the mere mortal.  That's why I would regard the handling of im: URIs
> as an important feature to have.

Just curious: What does the im: URI scheme have to do with persistent
groupchats?

Peter

--

-- 
Peter Saint-Andre
https://stpeter.im/

Jan Vornberger wrote:
> Hi there!

Re: Feature request: Handling of im: URIs

Hi there!

On Thu, Nov 01, 2007 at 07:05:38PM -0600, Peter Saint-Andre wrote:
> Jan Vornberger wrote:
> > I believe that permanent, irc-like group chats are one of the killer
> > features of Jabber that set it a side from other instant messaging
> > networks. IRC is a nice thing, but we all now, that it's mostly for
> > geeks. I think, that Jabber has the potential to bring IRC goodness to
> > the mere mortal.  That's why I would regard the handling of im: URIs
> > as an important feature to have.
> 
> Just curious: What does the im: URI scheme have to do with persistent
> groupchats?

Oh, I should have made myself more clear here: In my experience the act
of joining a groupchat is actually not that straightforward for the
average newcomer to Jabber. In most clients you are asked for a host
name and a channel name which means you need to understand that
groupchats live on certain conference servers and how that shows up in
its address. It is somewhat of a barrier.

If - instead - the user would be able to simply click on a website on
a link saying 'join our groupchat' and be dropped into that groupchat
without having to worry about where exactly this thing lives, it would
be much more useable. Combined with a more streamlined procedure of
'getting jabber' (and from what I can tell the redesign of jabber.org
seems to take a big step into this direction) I can actually see this
being a viable way for people to set up their own chat room.
I would imagine some community website which tells its members: Get
Jabber (some link) and join our new exciting groupchat (some im: link)!

Re: Feature request: Handling of im: URIs

Jan Vornberger wrote:
> On Thu, Nov 01, 2007 at 07:05:38PM -0600, Peter Saint-Andre wrote:
>> Just curious: What does the im: URI scheme have to do with persistent
>> groupchats?
> 
> Oh, I should have made myself more clear here: In my experience the act
> of joining a groupchat is actually not that straightforward for the
> average newcomer to Jabber. In most clients you are asked for a host
> name and a channel name which means you need to understand that
> groupchats live on certain conference servers and how that shows up in
> its address. It is somewhat of a barrier.
> 
> If - instead - the user would be able to simply click on a website on
> a link saying 'join our groupchat' and be dropped into that groupchat
> without having to worry about where exactly this thing lives, it would
> be much more useable. Combined with a more streamlined procedure of
> 'getting jabber' (and from what I can tell the redesign of jabber.org
> seems to take a big step into this direction) I can actually see this
> being a viable way for people to set up their own chat room.
> I would imagine some community website which tells its members: Get
> Jabber (some link) and join our new exciting groupchat (some im: link)!

I agree. I think you want support for xmpp: URIs. For instance to join
the jdev room on conference.jabber.org you would click this link:

xmpp:jdev@...?join

Peter

--

-- 

Re: Feature request: Handling of xmpp: URIs

On Thu, Nov 01, 2007 at 09:00:29PM -0600, Peter Saint-Andre wrote:
> I agree. I think you want support for xmpp: URIs. For instance to join
> the jdev room on conference.jabber.org you would click this link:
> 
> xmpp:jdev@...?join

Oh, I might have mixed things up. Yes, it seems I would like
support for xmpp: URIs then. 

Jan

Re: Feature request: Handling of im: URIs

On 1 Nov 2007, at 23:24, Jan Vornberger wrote:
> Since there seems to be a rather short development phase planned for
> 0.12 I'd like to express my hopes that maybe the handling of im: URIs
> might make it into that release.

It's not one of the things I'm going to desperately try to do for  
0.12, but it's about top of the things I'll try and do if I have  
time. In fact, links were broken temporarily in SVN when my  
unfinished code accidentally got committed.

/K

SuSE packages download link outdated

The link to the SuSE downloads is outdated at
	http://psi-im.org/download/

As the owner of this repository writes in his blog 
http://dev-loki.blogspot.com/:
--------------------------------------------------------------------
FRIDAY, SEPTEMBER 14, 2007

» Moving to Packman 
It's been a while I talked about doing this, but finally, the day has come: 
I'm moving my packages to the Packman repository \o/.

This is a good thing for everyone, as at some point, it will mean that users 
need to add one repository less.

I'm not exactly "moving" and my "guru" repository isn't quite dead yet, as the 
process is being implemented gradually. With the exception of smart, every 
new build/release will be published to Packman, and I migrate my existing 
packages slowly to either Packman or the openSUSE Build Service.
--------------------------------------------------------------------

Psi 0.11 cannot be found in some repository at this time pre-packaged for 
OpenSuSE at this time.

So be aware and it could be advantageous to remark this beside the download 
link.

René
_______________________________________________
Psi-Devel mailing list

Re: SuSE packages download link outdated

Oh, I found a new one after using the Software Search at OpenSUSE:

http://download.opensuse.org/repositories/server:/messaging/

Just need to add the appropriate path to YaST and You are up to date with 
SUSE, OpenSuSE, SLES and Psi 

I don't know whether this repository is already an official one.
Otherwise there could be changed the link at Your website.

René

On Friday 02 November 2007 11:50, René Krell wrote:
> The link to the SuSE downloads is outdated at
> 	http://psi-im.org/download/
>
> As the owner of this repository writes in his blog
> http://dev-loki.blogspot.com/:
> --------------------------------------------------------------------
> FRIDAY, SEPTEMBER 14, 2007
>
> » Moving to Packman
> It's been a while I talked about doing this, but finally, the day has come:
> I'm moving my packages to the Packman repository \o/.
>
> This is a good thing for everyone, as at some point, it will mean that
> users need to add one repository less.
>
> I'm not exactly "moving" and my "guru" repository isn't quite dead yet, as
> the process is being implemented gradually. With the exception of smart,