<p dir="ltr">While at it, I'd love to see a mobile port of the I2P plugin Bote mail (there's already a mobile port of I2P). </p>
<p dir="ltr">- Sent from my phone</p>
<div class="gmail_quote">Den 5 dec 2013 16:38 skrev "Nathan of Guardian" <<a href="mailto:nathan@guardianproject.info">nathan@guardianproject.info</a>>:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
One of the cool features of ChatSecure/Gibberbot that we have barely<br>
supported is the ability to add new protocol plugins. This is how we<br>
support Bonjour/ZeroConf messaging, but other than that, we haven't<br>
implemented any new protocol plugins.<br>
<br>
I am planning our activities for 2014, and am trying to decide where we<br>
should best spend our time. We already have a bunch of great things in<br>
the works on app sharing (Bazaar) and general encrypted data/file<br>
sharing (OTRDATA, Dataplug). However, I want to also explore making<br>
ChatSecure work with other services and protocols.<br>
<br>
In the very near term, I am working on a Bluetooth messaging plugin, so<br>
that the app can be used for secure messaging when there is no internet<br>
available, or its better to use in a physically near location. This<br>
would be useful for protests, "squares", classrooms, public cafes, etc,<br>
and be a carrier for some of our OTRDATA app messages like the Bazaar<br>
app syncing project.<br>
<br>
There are some existing open APIs for WhatsApp and WeChat, and Line's<br>
protocol can likely be sniffed and reversed. Should we get into a battle<br>
with these companies by trying to be the first "safe and secure" client<br>
app for their services? Should we call them out publicly to be granted<br>
favored app status, perhaps appealing to their interest in supporting<br>
business or enterprise users? My end goal here is that we can convert<br>
some small percentage of the 100millions users these systems have. In<br>
addition, Line, Viber, etc are being increasingly targeted and blocked<br>
by countries who don't care for them.<br>
<br>
Or is that all a waste of time? Is going back to the days of hacking AIM<br>
not a good approach?<br>
<br>
Should we instead focus on enhancing XMPP in open an extensible ways, or<br>
supporting some of these new protocols like Telegram<br>
(<a href="http://core.telegram.org/api" target="_blank">http://core.telegram.org/api</a>) and BitMessage? Or perhaps this new<br>
Layer.com thing I sent the link out about?<br>
<br>
The Briar Project is one that is near to our hearts, as well, so maybe<br>
we should focus on being a really great Briar client? Along those lines,<br>
we could also support TextSecure's SMS protocol and/or spend more time<br>
ensuring interoperability with Cryptocat's mpOTR/XMPP-MUC system.<br>
<br>
There are many possibilities out there, and we can't do them all. My<br>
goal is to ensure ChatSecure stays current and relevant, while staying<br>
open and interoperable. In the end, ChatSecure != XMPP client only, and<br>
we need to make sure people can tangible feel that.<br>
<br>
Thanks for your thoughts and feedback.<br>
<br>
+n<br>
<br>
<br>
<br>
_______________________________________________<br>
Guardian-dev mailing list<br>
<br>
Post: <a href="mailto:Guardian-dev@lists.mayfirst.org">Guardian-dev@lists.mayfirst.org</a><br>
List info: <a href="https://lists.mayfirst.org/mailman/listinfo/guardian-dev" target="_blank">https://lists.mayfirst.org/mailman/listinfo/guardian-dev</a><br>
<br>
To Unsubscribe<br>
    Send email to:  <a href="mailto:Guardian-dev-unsubscribe@lists.mayfirst.org">Guardian-dev-unsubscribe@lists.mayfirst.org</a><br>
    Or visit: <a href="https://lists.mayfirst.org/mailman/options/guardian-dev/natanael.l%40gmail.com" target="_blank">https://lists.mayfirst.org/mailman/options/guardian-dev/natanael.l%40gmail.com</a><br>
<br>
You are subscribed as: <a href="mailto:natanael.l@gmail.com">natanael.l@gmail.com</a><br>
</blockquote></div>