raindrift

4 ms·

1. 1.▲
   by raindrift 12y ago

   I based my estimates on the best numbers I could find. That said, my spam numbers were in fact incorrect (spam is small and gets deleted). Accounting for that, people save an average of a year's worth of email. If you look at the growt
2. 2.▲
   by raindrift 12y ago

   These are both excellent points. I've done a bit more digging, and updated the article to reflect them. Thanks!
3. 3.▲
   How Big is Email?(medium.com)

   134 points by raindrift 12y ago|22 comments
4. 4.▲
   by raindrift 12y ago

   Hi. This is Ian, Threadable cofounder. Thanks for your questions! We're sustaining Threadable by charging business users for business-specific features. Those features will actually be rolling out soon, and have to do with internal acc
5. 5.▲
   by raindrift 12y ago

   I'm an early beta user, and have been really happy with it. It saves me a bunch of time, but I think the real value is in what it teaches me about where to focus our efforts. Way easier to predict which initiatives (features, hires, et
6. 6.▲
   by raindrift 13y ago

   Good question! At the moment, getting at your archives is about as easy as with Google Groups (which is to say, not very). Right now, you could use our webhooks to funnel all email into an archiver, so you have it. That's not a good so
7. 7.▲
   by raindrift 13y ago

   I agree completely! We're really excited about email transparency. Supporting it well has been one of our goals from the beginning. We have a few users who practice it (including us!) with whom we're working very closely to make s
8. 8.▲
   by raindrift 13y ago

   We exist, but we're still figuring out pricing. ;) As I said earlier, our plan is to charge for business features, and not by restricting the number of users in a given list. https://news.ycombinator.com/item?id=7429550
9. 9.▲
   by raindrift 13y ago

   Thanks glasser! One of the key changes between how Threadable works and previous mailing lists is that we can actually customize fairly deeply each message to each user, rather than simply reflecting the same thing out to the whole list. Th
10. 10.▲
    by raindrift 13y ago

    Hey mbesto, our API is really early right now, but we'd love to work with you to make this happen. You can find my email in my profile, I'd love to discuss how you'd like to make this work.
11. 11.▲
    by raindrift 13y ago

    There's a number of reasons, but our groups implementation is the most compelling one for me: A threadable list can be divided easily into subgroups with their own subset of the list membership. Any member can create a group, and you c
12. 12.▲
    by raindrift 13y ago

    I agree, email is sort of a morass of old, incompatible clients and aging protocols. They need work, but the installed base is huge, so it's a hard problem. The solution is probably to build a layer on top of all that to simplify it, m
13. 13.▲
    by raindrift 13y ago

    Heh. Threadable's actually Rails on the backend, but last time I had a problem with collectstatic being slow, I used this: https://github.com/antonagestam/collectfast
14. 14.▲
    by raindrift 13y ago

    Our current thought is to charge for business features. A Threadable list is a pretty open place by default. Lists are all members-only, but once you've been added you have a lot of control. Private (within the team) subgroups are a fe
15. 15.▲
    by raindrift 13y ago

    Thanks, neilk. People say they hate email, but we see that as an indicator of its utility: "I hate this but use it everyday" sounds like an opportunity for improvement. As Elie Wiesel said, "the opposite of love is not hate,
16. 16.▲
    by raindrift 13y ago

    Hi, everyone. I'm Ian, one of the Threadable founders. I'd be happy to answer any questions.
17. 17.▲
    by raindrift 13y ago

    Yep! The Chrome debugger for js, and pry-debugger for ruby.