[prev in list] [next in list] [prev in thread] [next in thread] 

List:       tor-dev
Subject:    [tor-dev] [GSoC] BridgeDB Twitter Distributor report
From:       Kostas Jakeliunas <kostas () jakeliunas ! com>
Date:       2014-07-26 5:27:16
Message-ID: CAN0KoygJy9GTOPg2yzwkD0JKxzy4JLMbh3vMRJ7QxOQ9k_juQQ () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Progress/activities since last time:

  * incorporating BridgeRequest's together with an initial bridge request
API over JSON (it's easier to do both as they are tightly related.) The
bridge request api is based on isis' initial fix/12029-dist-api_r1;

  * bogus server-side bridge provider that implements the json api: just
something that gives fake bridges based on the request (which is
handled/contained in BridgeRequest.) (will have server side code real soon
now (hoped to have it by now.))

  * my churn_rewrite could probably make use of bridgedb's current approach
to pickled storage. (It's also worth switching to twisted.spread.jelly for
(mostly) security)

  * experimenting with sending images over twitter DMs. Twitter API does
not support images in DMs, but the web as well as various mobile apps
support attaching images to DMs (images end up in twitter CDN. (served over
ton.twitter.com), which is good.) Some progress here: the web client DM
send requests (where image files can be attached) are contained; the bot
should be able to send images in DMs soon, emulating a normal web user
agent (but using the two twitter APIs for all other activities and DMs.)

  * once bridgerequest's + request api (client-side + my mock server-side
thing) are done, the bot will have approached a not-far-from-functional
state

Apologies for the late report.

--

Kostas.

0x0e5dce45 @ pgp.mit.edu

[Attachment #5 (text/html)]

<p>Progress/activities since last time:</p>
<p>   * incorporating BridgeRequest&#39;s together with an initial bridge request API \
over JSON (it&#39;s easier to do both as they are tightly related.) The bridge \
request api is based on isis&#39; initial fix/12029-dist-api_r1;</p>

<p>   * bogus server-side bridge provider that implements the json api: just \
something that gives fake bridges based on the request (which is handled/contained in \
BridgeRequest.) (will have server side code real soon now (hoped to have it by \
now.))</p>

<p>   * my churn_rewrite could probably make use of bridgedb&#39;s current approach \
to pickled storage. (It&#39;s also worth switching to twisted.spread.jelly for \
(mostly) security)</p> <p>   * experimenting with sending images over twitter DMs. \
Twitter API does not support images in DMs, but the web as well as various mobile \
apps support attaching images to DMs (images end up in twitter CDN. (served over <a \
href="http://ton.twitter.com">ton.twitter.com</a>), which is good.) Some progress \
here: the web client DM send requests (where image files can be attached) are \
contained; the bot should be able to send images in DMs soon, emulating a normal web \
user agent (but using the two twitter APIs for all other activities and DMs.)</p>

<p>   * once bridgerequest&#39;s + request api (client-side + my mock server-side \
thing) are done, the bot will have approached a not-far-from-functional state</p> \
<p>Apologies for the late report.</p> <p>--</p>
<p>Kostas.</p>
<p>0x0e5dce45 @ <a href="http://pgp.mit.edu">pgp.mit.edu</a></p>



_______________________________________________
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev


[prev in list] [next in list] [prev in thread] [next in thread]