Email: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
m (re-categorization & links)
Line 1: Line 1:
'''Offering Email through the Laptops'''
'''Offering Email through the Laptops'''


OLPC intern [[http://www.akbars.net/blog Imran Akbar]] is working on a prototype email client written in Python. It will initially utilize existing POP/IMAP servers to store messages, and use a keyserver for [[http://www.gnupg.org/ GPG]] encryption and [[http://www.zlib.net zlib]] compression built-in. The GUI interface will be simpler, with three tabs on the left: Mail, Contacts, and maybe History. Voicemail capabilities will be added later utilizing the [[http://www.speex.org Speex]] codec (recording and playing back of voice messages).
OLPC intern [http://www.akbars.net/blog Imran Akbar] is working on a prototype email client written in [[Python]]. It will initially utilize existing POP/IMAP servers to store messages, and use a keyserver for [http://www.gnupg.org/ GPG] encryption and [http://www.zlib.net zlib] compression built-in. The GUI interface will be simpler, with three tabs on the left: Mail, Contacts, and maybe History. Voicemail capabilities will be added later utilizing the [http://www.speex.org Speex] codec (recording and playing back of voice messages).


Other ideas:
Other ideas:
* captchas and [[http://www.hashcash.org hashcash]] to eliminate spam
* captchas and [http://www.hashcash.org hashcash] to eliminate spam
* casy mailing-list creation
* casy mailing-list creation
* tags
* tags
* presence - location & local time, through a P2P layer such as [[http://thecircle.org.au/involved.html the Circle]]
* presence - location & local time, through a P2P layer such as [http://thecircle.org.au/involved.html the Circle]
* global address book
* global address book
* ditching the Re: and Fw: conventions, and moving them to the headers instead, along with hashes for each conversation so they can be properly threaded
* ditching the Re: and Fw: conventions, and moving them to the headers instead, along with hashes for each conversation so they can be properly threaded
Line 20: Line 20:


Bits and Pieces:
Bits and Pieces:
* [[http://proquest.safaribooksonline.com/0596000855/python2-CHP-11-SECT-4 pymailgui]]
* [http://proquest.safaribooksonline.com/0596000855/python2-CHP-11-SECT-4 pymailgui]
* [[http://www.soul-less.pwp.blueyonder.co.uk/pyne/ pyne]]
* [http://www.soul-less.pwp.blueyonder.co.uk/pyne/ pyne]
* [[http://people.csail.mit.edu/hubert/pyaudio/ pyaudio]]
* [http://people.csail.mit.edu/hubert/pyaudio/ pyaudio]
* Either pyQt or PyGTK as the GUI toolkit - perhaps pyQt due to cross-platform compatibility, with a frozen binary for systems without [[http://www.trolltech.com/qt/ Qt]].
* Either pyQt or PyGTK as the GUI toolkit - perhaps pyQt due to cross-platform compatibility, with a frozen binary for systems without [http://www.trolltech.com/qt/ Qt].


Tentative timeline:
Tentative timeline:
Line 33: Line 33:
http://www.gaborcselle.com/blog/2006/07/how-researchers-are-reinventing-mail.html
http://www.gaborcselle.com/blog/2006/07/how-researchers-are-reinventing-mail.html


Generous thanks to [[http://www.wingware.com Wingware]] for their great IDE for Python.
Generous thanks to [http://www.wingware.com Wingware] for their great IDE for Python.


Imran is looking for a nice name for the project, preferably a recursive name a-la GNU.
Imran is looking for a nice name for the project, preferably a recursive name a-la GNU.
Line 40: Line 40:


[[Category:Software ideas]]
[[Category:Software ideas]]
[[Category:Python]]

Revision as of 00:03, 12 January 2007

Offering Email through the Laptops

OLPC intern Imran Akbar is working on a prototype email client written in Python. It will initially utilize existing POP/IMAP servers to store messages, and use a keyserver for GPG encryption and zlib compression built-in. The GUI interface will be simpler, with three tabs on the left: Mail, Contacts, and maybe History. Voicemail capabilities will be added later utilizing the Speex codec (recording and playing back of voice messages).

Other ideas:

  • captchas and hashcash to eliminate spam
  • casy mailing-list creation
  • tags
  • presence - location & local time, through a P2P layer such as the Circle
  • global address book
  • ditching the Re: and Fw: conventions, and moving them to the headers instead, along with hashes for each conversation so they can be properly threaded

Considering a four-step spam solution: for in-network email:

  • captchas required to send any msg
  • hashcashs added to email headers
  • a user-based dynamic ranking system

for regular email:

  • integrating pyzor (collaborative spam filtering) and spambayes (bayesian spam filtering)

Bits and Pieces:

  • pymailgui
  • pyne
  • pyaudio
  • Either pyQt or PyGTK as the GUI toolkit - perhaps pyQt due to cross-platform compatibility, with a frozen binary for systems without Qt.

Tentative timeline:

  • End of July: a running python email client with a GUI
  • End of August: above, with encryption/compression/backend database support
  • End of September: above, with P2P support and voicemail capabilities

More thoughts on why email still sucks: http://www.gaborcselle.com/blog/2006/07/how-researchers-are-reinventing-mail.html

Generous thanks to Wingware for their great IDE for Python.

Imran is looking for a nice name for the project, preferably a recursive name a-la GNU.

--Imr 14:54, 14 July 2006 (EDT)

Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=Email&oldid=20773"