This document discusses using email interfaces for Ruby applications. Some key points covered include: - Email is ubiquitous and can provide inherent attention and gradual engagement. It also allows embedding identity and resurrecting dead data. - Elements of an email interface include the TO address, subject line, message body, and attachments. - Receiving email involves tools like Postfix and POP/IMAP for fetching messages, then processing them using libraries like TMail and mms2r. - Testing email interfaces requires fixtures to ensure proper functionality.

1. Email Interfaces
for your
Ruby Applications

2. About Me

3. Why an Email
Interface?

4. Everyone has it.

5. Everyone gets it.

6. Inherent attention.

7. Gradual
engagement.

8. Embedded identity.

9. Resurrect dead data.

10. Other people’s
programming.

11. The actual mobile web.

12. Asynchronicity.

13. The need for speed.

14. It’s brutally productive.

15. Make the internet
work for us.

16. The Downside

17. Poor fit

18. Power-users only

19. Support
headaches

20. Spam

21. No feedback

22. (Potentially)
Slow

23. Styles of Interaction

24. Links

25. NetFlix

26. CraigsList

27. gCal

28. Reply

29. Google
Groups

30. Basecamp

31. Lighthouse

32. Command Line

33. Remember
the Milk

34. I Want
Sandy

35. 3mindMe

36. Forwarding

37. TripIt

38. TrackMyShipments

39. Highrise

40. User-Generated
Content

41. Posterous

42. Flickr

43. Rate It All

44. Elements of the
Interface

45. The TO: address

46. TripIt

47. Tumblr

48. Posterous

49. 3mindMe

50. The Subject

51. Hiveminder

52. Flickr

53. Posterous

54. The Body

55. Remember
the Milk

56. TripIt

57. I Want Sandy

58. The Attachments

59. Backpack

60. Flickr

61. Posterous

62. This is how
we do it

63. Receiving

64. Postfix

65. POP/IMAP

66. Lamson

67. Fetching

68. Postfix Filter

69. TMail::MailDir

70. Fetcher

71. Long-Running Process

72. Monit

73. Cron

74. Lockfile

75. Processing

76. TMail

77. mms2r

78. RESTfully

79. Astrotrain

80. Testing

81. Fixtures

82. Thanks!
• http://speakerrate.com/talks/1539
• http://delicious.com/deisinger/emailtalk
• Twitter: @deisinger