Re: Adding a new protocol

Eduardo <[email protected]> Thu, 16 May 2019 10:01:26 -0300
Newsgroups	gmane.comp.gnome.gaim.devel
Message-ID	<[email protected]>
This is a multi-part message in MIME format.
--===============3205815925822547348==
Content-Type: multipart/alternative;
 boundary="------------0B37DF02BEED02492FB91282"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------0B37DF02BEED02492FB91282
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

That's also a good idea. I'll check python-purple.

On 15/5/19 17:48, Eion Robb wrote:
> You could also load the yowsup library directly and write a protocol 
> plugin in Python using the https://github.com/anpetrov/python-purple 
> python plugin loader plugin, without needing to build a client/server 
> setup thing
>
> On Thu, 16 May 2019 at 00:14, Eduardo <[email protected] 
> <mailto:[email protected]>> wrote:
>
>     > What protocol were you thinking of writing for?
>
>     I'm using the yowsup library, with a python client whose only task
>     is to
>     forward the messages to Telegram. My idea is to connect pidgin
>     with that
>     script,  via a shallow plugin doing IPC, for example, or by
>     presenting
>     the yowsup client as a server to pidgin (using a basic protocol).
>
>     Hope that makes sense...
>
>     > There's a skeleton prpl in-tree called nullprpl.c (for 3.x.y
>     >
>     https://bitbucket.org/pidgin/main/src/default/libpurple/protocols/null/
>
>     > or for 2.x.y
>     > [...]
>
>     Thanks a lot Eion! It's exactly what I was looking for. You'll
>     probably
>     hear from me again if I can get something working ;).
>
>     Cheers, Eduardo.
>

--------------0B37DF02BEED02492FB91282
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>That's also a good idea. I'll check python-purple.<br>
    </p>
    <div class="moz-cite-prefix">On 15/5/19 17:48, Eion Robb wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAFt0mko6KadW=VVKDNivcoQcOKMYQoeA4uWUnem9Oh8z39ATjg@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr">You could also load the yowsup library directly
          and write a protocol plugin in Python using the <a
            href="https://github.com/anpetrov/python-purple"
            moz-do-not-send="true">https://github.com/anpetrov/python-purple</a>
          python plugin loader plugin, without needing to build a
          client/server setup thing</div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Thu, 16 May 2019 at 00:14,
          Eduardo &lt;<a href="mailto:[email protected]"
            moz-do-not-send="true">[email protected]</a>&gt;
          wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">&gt;
          What protocol were you thinking of writing for?<br>
          <br>
          I'm using the yowsup library, with a python client whose only
          task is to <br>
          forward the messages to Telegram. My idea is to connect pidgin
          with that <br>
          script,  via a shallow plugin doing IPC, for example, or by
          presenting <br>
          the yowsup client as a server to pidgin (using a basic
          protocol).<br>
          <br>
          Hope that makes sense...<br>
          <br>
          &gt; There's a skeleton prpl in-tree called nullprpl.c (for
          3.x.y <br>
          &gt; <a
href="https://bitbucket.org/pidgin/main/src/default/libpurple/protocols/null/"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://bitbucket.org/pidgin/main/src/default/libpurple/protocols/null/</a>
          <br>
          &gt; or for 2.x.y <br>
          &gt; [...]<br>
          <br>
          Thanks a lot Eion! It's exactly what I was looking for. You'll
          probably <br>
          hear from me again if I can get something working ;).<br>
          <br>
          Cheers, Eduardo.<br>
        </blockquote>
      </div>
    </blockquote>
  </body>
</html>

--------------0B37DF02BEED02492FB91282--


--===============3205815925822547348==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KRGV2ZWwgbWFp
bGluZyBsaXN0CkRldmVsQHBpZGdpbi5pbQpodHRwczovL3BpZGdpbi5pbS9jZ2ktYmluL21haWxt
YW4vbGlzdGluZm8vZGV2ZWw=

--===============3205815925822547348==--