4 ms·

> * Less work than blogging, way more benefits > > * Build a community around your inbox > > * Only share the emails you intend to It's just a fancy mailing li

by 2ion 8y ago

> * Less work than blogging, way more benefits > > * Build a community around your inbox > > * Only share the emails you intend to It's just a fancy mailing list then? Minus the SMTP leg, plus privacy/consent issues and moving to a non-free storage format as well as concentrating the presence of the "thread" at one site. The best email lore out there is saved to mailing list archives and can be linked to and shared just as easily. And mailing lists take "forwards" too.

deleted 8y ago
[deleted]
cryptonector 8y ago
Might as well build a tool to blogify mailing list archives. If the list is private you can always publish the blog-form summary if you have the authority to do it. But there's no way to monetize that -- you have to provide much more than that, and centralize things in the process, in order to monetize. For corporate customers who want to publish into an org, rather than the world, this service might actually be very valuable. For non-corporate uses this might make some sense, but for me... I'd not let a third party read my email.
Alex3917 8y ago
> It's just a fancy mailing list then? It's more of a social network built around email conversations. E.g. we make it easy to not only to leave comments and share on social, but also to embed threads within any other site. Unlike email lists, we're also designed to make it easy to share great conversations after the fact, rather than having everyone copied on every message as it happens. I think one good use case for the site is sharing the best conversations from otherwise private mailing lists. (With everyone's permission, or if the list specifically allows it.) > moving to a non-free storage format If you look at the API response for our threads, it's actually much easier to parse than any archival format. That said we're not (currently) an archival product; we don't store the original raw messages, and we don't output them into archival formats designed for longterm storage. I would like to integrate with some archival products in the future though. Right now when you donate your email archives to a university, they are only readable in the reading room of the university after signing an NDA with the librarian. I think we offer a good solution for making it easy to redact some of the more interesting threads and get them on the web, and I think a lot of that stuff would be super interesting.
epicide 8y ago
I'm really struggling to find a good use for this. Putting content in a blog post means the author thought the information was worth at least copying and pasting (and possibly even editing). A lot of blog posts aren't even worth the time reading the title. This is somehow less than that.

by 2ion 8y ago

deleted 8y ago

[deleted]

cryptonector 8y ago

Might as well build a tool to blogify mailing list archives. If the list is private you can always publish the blog-form summary if you have the authority to do it. But there's no way to monetize that -- you have to provide much more than that, and centralize things in the process, in order to monetize. For corporate customers who want to publish into an org, rather than the world, this service might actually be very valuable. For non-corporate uses this might make some sense, but for me... I'd not let a third party read my email.

Alex3917 8y ago

> It's just a fancy mailing list then? It's more of a social network built around email conversations. E.g. we make it easy to not only to leave comments and share on social, but also to embed threads within any other site. Unlike email lists, we're also designed to make it easy to share great conversations after the fact, rather than having everyone copied on every message as it happens. I think one good use case for the site is sharing the best conversations from otherwise private mailing lists. (With everyone's permission, or if the list specifically allows it.) > moving to a non-free storage format If you look at the API response for our threads, it's actually much easier to parse than any archival format. That said we're not (currently) an archival product; we don't store the original raw messages, and we don't output them into archival formats designed for longterm storage. I would like to integrate with some archival products in the future though. Right now when you donate your email archives to a university, they are only readable in the reading room of the university after signing an NDA with the librarian. I think we offer a good solution for making it easy to redact some of the more interesting threads and get them on the web, and I think a lot of that stuff would be super interesting.

epicide 8y ago

I'm really struggling to find a good use for this. Putting content in a blog post means the author thought the information was worth at least copying and pasting (and possibly even editing). A lot of blog posts aren't even worth the time reading the title. This is somehow less than that.