rituraj
HOW ONE ENTREPRENEUR’S HACKING THE SCIENCE OF HAPPINESS
Indian style Eating with your Hands
Forget Coding Creating an Identity Is a Pain
What does it feel like to be the CEO of a start-up?
Keith Rabois on Startup Hiring
Looking for a guru in CSS/HTML/Twitter Bootstrap
Need a resource for 25 hrs to translate illustrator files to css/html and twitter bootstrap. Pay well.
Indian Mafia
Looking for UI Elements for illustrator
Anyone know a free or premium UI Elements for Web App for illustrator (there are many available for PSD, want it for AI)
Re:Self-Destructing Email
on Monday January 28, 2013 @11:15PM (#5132290)
I actually agree with you, I wrote the post not to work on it, but give context and inspire the giants gmail, microsoft and others to do something about it.
Re:Self-Destructing Email
on Sunday January 27, 2013 @06:44PM (#5126240)
Speaking in terms of higher level of usage of language, meeting invites are only one kind of coordination in language. You make a request for a meeting, the other has a chance to Accept, Decline or Counter Offer the meeting.
Coordination is a major use case of email. Whenever you ask someone to do something, or in another words say send you something - language wise you are making a request - its the same construct as that of a meeting - the action is different.
Re:Self-Destructing Email
on Sunday January 27, 2013 @06:40PM (#5126219)
Nice find for sure. I think the issue with outside server technology is adoption by both sender / receiver - the main hypothesis is based on sync time management between both.
Like regular verbal communication (instead of messaging) happens over same time. For us thats like water to fish. Implementing a time server function to email systems would create a sync'ed communication system.
Re:Self-Destructing Email
on Sunday January 27, 2013 @06:36PM (#5126200)
The problem with Client side time management is you cannot sync time across the sender and receiver. Server side is where it would produce the max productivity.