Yahoo! Protocol and signals

GS gaf.stephanos at gmail.com
Fri May 8 12:16:24 EDT 2009


But this will make me modify the original yahoo plugin. That's the only way
I can have that plugin. As this is 'free' software, I can modify it and post
the two plugins (the modified yahoo and the invisibility one) right ? Even
without getting this stuff on the pidgin page.

On Fri, May 8, 2009 at 8:11 PM, Etan Reisner <pidgin at unreliablesource.net>wrote:

> On Fri, May 08, 2009 at 08:05:52PM +0400, GS wrote:
> <snip>
> > > The Yahoo prpl doesn't expose a send_raw function. Presumably because
> > > there isnt a simple raw format that can be used (though possibly just
> > > because no one saw a need to expose one).
> > >
> > > Similarly, if there is no exposed way to send raw data then there is
> > > little-to-no reason to expose raw received data by things like a
> > > yahoo-receiving signal.
> > >
> > > I don't know enough about Yahoo to say whether we should have either of
> > > those, but at the moment we don't.
> > >
> > >    -Etan
> > >
> >
> > Yes but could I submit a patch for all this later on ? This wouldn't hurt
> > you guys. It'll just do a lot of benefit to me.
>
> Like I said I don't know enough about Yahoo to know whether there is some
> meaningful format that can be passed around the way XMPP can pass around
> XML stanzas, and IRC can pass around lines of plain text. If there is, and
> it can be reaosonably handled by the prpl then I see no reason not to add
> support for it. But if the support is going to be "raw bytes" then that's
> not acceptable.
>
>    -Etan
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pidgin.im/pipermail/devel/attachments/20090508/5390eef7/attachment.html>


More information about the Devel mailing list