3 ms·
That's a nice application idea. I have some feedback: * The email subject is labeled "name of your reminder" on the input form and "title" on the confirmatio
by BarkMore 16y ago
That's a nice application idea. I have some feedback:
* The email subject is labeled "name of your reminder" on the input form and "title" on the confirmation page. I recommend using the term "subject" in both places because that's what people are used to seeing in their email clients.
* I recommend changing "Execution date" on the confirmation page to something less geeky like "Send time".
* The confirmation page should have an edit link.
How will you prevent people from using the application to send spam?
- jmonegro 16y agoHey, 1 & 2 You're right. It was 3am and I wasn't paying much attention to that kind of details :p 3. Yes. Regarding spam: it's not really useful for spammers because they'd have to send one message at a time. Although they could build bots, Rails 3's security methods offer primary defense against this. Not that it couldn't be circumvented. I thought about sending a confirmation e-mail, but I deemed that to be an unnecessary layer of complexity - I wanted to build the simplest e-mail reminder service around. I guess I would edge towards daily IP based limits?
- BarkMore 16y agoThe problem is not so much bulk sending of mail, but sending of unwanted mail from one user to another. Amazon might shut you down if you have a large number of recipients marking these unwanted messages as spam. Perhaps you should record enough information about sender (ip address, unique cookie) so that you can bulk delete and blacklist a problem sender. You can identify problem senders from the unsubscribe link that should be included in the messages.