Save, Share, Revist

In early January 2015, Mozilla UX conducted user research to refresh their understanding of how people save, share, and revisit content. People are happy with simple techniques they understand, using multiple tools, and aren't especially interested in revamping their process. link

The Firefox Email Tabs experiment drew on that research. link

It was important to actually have them documented and backed up by research: * People use simple techniques * Everyone claims to be happy with their current processes * Everyone used multiple tools that typically fed into each other * Those processes might seem complicated and inefficient to me, but didn’t to them * People said they might be open to improvements in specific steps * People were not interested in revamping their overall processes * Some techniques were particularly popular: Screenshots URLs Email Texting Bookmarks

.

I wonder about allowing an inbound email to arrive in a queue which could be browsed by the site author as ghost pages and then forked into the site. This to empower creation via mobile devices using familiar tools.

I don't especially like the invitation for actual SPAM into yet another inbox. But mozilla's research results seem compelling and maybe worth exploring.

Some resources I remember from bivio. We had `sendmail` configured to transfer any inbound SMTP message into a specific HTTP endpoint so we could process inbound email with all the same framework features as inbound web requests. mock_sendmail() Bivio::Util::SendmailHTTP.pm

Related concept, but javascript. smtp2http