Show HN: Extract email attachments into shareable links
Link = https://moogle.cc/nirvaancms.html
After having to upload images/json files one too many times to S3, I decided to build a process which allowed me to email files to a set email address and have the files appear in s3 with a shareable link.
I can see a product like this being useful as a headless CMS, sharing a files outside Dropbox/GDrive, config files for web and IoT projects, and general backup.
Let me know what you think, HN.
Link = https://moogle.cc/nirvaancms.html
8 comments
[ 2.9 ms ] story [ 30.1 ms ] threadHow long are the files retained? [Yes, it's in the FAQ, but it should be in the main page.]
How can I delete a file? Why do you not send two links: One with the public url of the file and one with a delete page. What happens if Google indexes one file and keeps checking it weekly?
Beware Gmail sometimes send big attachments as links to Google Drive. It's very confusing for end users.
About who can read my emails: I don't understand why you explain they are encrypted. I'd prefer a policy like mailinator, but perhaps you should ask a lawyer.
If there’s sufficient interest in this, I could enforce login on emails sent to a different email inbox such as private@moogle.cc. That way, only the sender would be able to see the attachments. I’ll have to think this thru though.
Would be nice if I could just right click attachments in Outlook and copy a sharable link to them.
Maybe the moogle inbox can be a standalone read-only inbox (i.e., no reply, no forwarding) for things like linking to attachments and making private notes about emails?
I believe Zoho Mail does something similar for private notes but I don’t think they give you links to attachments.
I wouldn't get too hung up on the messaging.
(Safety: mail providers like SES will verify incoming mails for viruses and spam Size limits: SES limits email sizes to 10MB.)
Using email as a delivery mechanism let me focus on building the backend plumbing and not on virus checks/File Upload UI.