4 ms·
Ask HN: Can’t we define a new e-mail standard with Facebook’s features?
Features like groups, events, pinwalls, photo albums, likes, friends/contacts but also collaborative editing, versioning, chatting channels and voting come to mind.
I’m wondering what are the hurdles to define such an "e-mail 2.0" standard.
- frm1001xplrr 13y agoTried and failed, unfortunately: http://support.google.com/bin/answer.py?hl=en&answer=1083134 http://support.google.com/bin/answer.py?hl=en&answer=108...
- coned88 13y agoThere's no need to.
- bjackman 13y agohttps://tent.io/ https://tent.io/ ?
- smartwater 13y agoCan you explain in more detail?
- angersock 13y agoIt'll be like the email everyone knows and loves, but social!
- reubeningber 13y agoIsn't email inherently social?
- deleted 13y ago[deleted]
- kylesethgray 13y agoI think before we define a _new_ email standard, that there should be an email standard in the first place. So many clients treat email differently: * quote levels increasing or not * how to format the date of the previous message * whether or not you attach the original files when replying * how to format the headers signatures of the emails * where attachments are, i.e. inline or as an extra * read receipts on and on.
- greenyoda 13y agoGroups: You can create a "group" with regular e-mail using a mailing list. Events: Many corporate e-mail systems (e.g., Outlook) already have a meeting invitation function (accept, reject, reschedule, see people's free time slots, etc.). Pinwalls, photo albums, likes, friends: If I really wanted those integrated into my e-mail workflow, I'd be a Facebook user. Why should they be part of regular e-mail? Once you've added all those features, don't you really have a Facebook clone rather than an e-mail system?
- orangethirty 13y agoI'm working on that. The standard API is currently being designed.