Re: Matrix as a replacement for Telepathy

[Gary Kramlich <grim reaperworld com>]

On Fri, Aug 25, 2017 at 10:13 AM, David Woodhouse <dwmw2 infradead org> wrote:
> On Fri, 2017-08-25 at 09:51 -0500, Gary Kramlich wrote:
> > > On Fri, Aug 25, 2017 at 3:59 PM, David Woodhouse  wrote:
> > > > On Fri, 2017-08-25 at 15:34 +0200, Alexandre Franke wrote:
> > > > > If someone cares enough to implement support for a protocol in
> > > > > Telepathy, they could probably implement support for the protocol
> > > > > elsewhere too.
> > > > But where is "elsewhere"? If not libpurple, where *should* I be adding
> > > > support for my new toy protocol for example? If you've just taken your
> > > > ball and gone home...
> > >
> > > Well why not libpurple?
> >
> > As the current lead developer of Pidgin, and thus libpurple, I would
> > love to see more people using it.  if there's something we can do to
> > make Pidgin/libpurple a stronger contender in this race, please let me
> > know.
>
> Release 3.0? :)

I know, need more hours in the day :-/  I'll spend some time this
putting together a 3.0 checklist, but it's not going to be pretty..

> Seriously, all that nice GObjectification cleanup does make it a nicer
> proposal as a GNOME framework.

Yeah, unfortunately it's incomplete, and if we release now, we're just
going to have a super long 4.0 cycle too.  I'd rather get through 3.0
get the GObject based API stable and complete and then get into a
normal development cycle of feature releases again.

> It's also a little hard to add the new features that we need, as things
> stand. I actually ended up backporting a bunch of stuff from 3.x to the
> 2.x branch a while back, to support everything that Lync needed. I'm
> kind of resigned to the fact that I might need to do the same, for the
> protocol I'm working on now.

Dang, well let me know where I can help.

> But overall, I think libpurple does a fairly good job, even if it needs
> a little updating to handle the needs of some new protocols.

Thanks!

> > Your critiques about needing updates for newer protocols are certainly
> > valid, and we're slowly marching towards them as we're trying to
> > modernize our codebase.  That said if anyone would like to discuss
> > them in more detail, I'd love to hear it (off list naturally).
>
> For my part I haven't quite got there yet. I'm filling in the parts of
> the protocol support that libpurple *can* represent, before I turn to
> the bits I actually want to extend libpurple for.

Understood.

> Top of my list will be persistent messages, read receipts and multi-way
> V/V calls though. And I've already been asking on the devel list about
> why Pidgin has no way to display presence status or full names for an
> "unknown" person who sends me an IM, even though my prpl has it and
> could tell you.

Noted.

Thanks,

--
Gary Kramlich <grim reaperworld com>