Difference between revisions of "Project Newsletter"
Jump to navigation
Jump to search
Megalanya0 (talk | contribs) m (MOTHERFUCKER ! ! !) |
CoolCanuck (talk | contribs) (spamdex info) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 12: | Line 12: | ||
| − | == '' | + | == Ideas == |
| + | * Have a separate email address for each newsletter. | ||
| + | ** Public access to the email addresses will need to be limited to prevent random spam from entering the archives. | ||
| + | *** Spam could also be prevented by maintaining a blacklist. (this also keeps out script kiddies) | ||
| + | ** Have a way for people to forward past 'issues' of newsletters. Submitted newsletter issues can be verified using copies from multiple submitters. | ||
| + | * Problem: a lot of newsletters require you to click a confirmation link in an email. Some solutions: | ||
| + | ** Make the archiving tools search the email content for confirmation links and follow them. | ||
| + | ** Have a password protected page where people can click confirm links. | ||
| + | *** First solution is better, but the second one could be used if the bot fails to properly follow the confirmation link. | ||
| + | * Problem: some newsletters require the initial email to be replied to for confirmation. | ||
| + | ** Solution: Make the archiving tools auto-reply to the first email received from a newsletter. | ||
| + | * Download image URLs in each email with wget. | ||
| + | * Upload received emails to IA in [[ArchiveBot]]-like GO packs, and separate files by the receiving address. | ||
| + | * Provide an interface for reading archived emails. | ||
| + | * Have a bot crawl the web looking for more newsletters. | ||
| + | ** Should it automatically create a new email address and try signing up for newsletters, or should there be some sort of human intervention? | ||
| + | * Problem: if unsubscribe links are made public and followed, the archiving address will be unsubscribed. | ||
| + | ** Maybe unsubscribe links could be removed from each email and the unsubscribe link changed to http://example.com or http://archiveteam.org? | ||
| + | *** Upload darkened copies of the original emails to IA along with the modified ones. | ||
| + | * Have a list of newsletters currently being saved to prevent saving multiple copies of the same newsletter. | ||
| − | == | + | ==Notes== |
| + | * http://www.spamdex.org/ has a bunch of spam archives. Maybe we could collaborate OR at least see how they have it implemented in the backend.. | ||
| − | + | {{Navigation box}} | |
Latest revision as of 04:48, 30 November 2017
| Project Newsletter | |
| |
 | |
| URL | http://mail1.newsletter.nerds.io/, http://mail2.newsletter.nerds.io/, http://mail3.newsletter.nerds.io/ (dev branch for mail1) |
| Project status | Online! |
| Archiving status | In progress... |
| Project source | newsletter-python |
| Project tracker | Unknown |
| IRC channel | #projectnewsletter (on EFnet) |
| Project lead | Unknown |
Archiving all the email newsletters. Join the discussion in #projectnewsletter.
Ideas
- Have a separate email address for each newsletter.
- Public access to the email addresses will need to be limited to prevent random spam from entering the archives.
- Spam could also be prevented by maintaining a blacklist. (this also keeps out script kiddies)
- Have a way for people to forward past 'issues' of newsletters. Submitted newsletter issues can be verified using copies from multiple submitters.
- Public access to the email addresses will need to be limited to prevent random spam from entering the archives.
- Problem: a lot of newsletters require you to click a confirmation link in an email. Some solutions:
- Make the archiving tools search the email content for confirmation links and follow them.
- Have a password protected page where people can click confirm links.
- First solution is better, but the second one could be used if the bot fails to properly follow the confirmation link.
- Problem: some newsletters require the initial email to be replied to for confirmation.
- Solution: Make the archiving tools auto-reply to the first email received from a newsletter.
- Download image URLs in each email with wget.
- Upload received emails to IA in ArchiveBot-like GO packs, and separate files by the receiving address.
- Provide an interface for reading archived emails.
- Have a bot crawl the web looking for more newsletters.
- Should it automatically create a new email address and try signing up for newsletters, or should there be some sort of human intervention?
- Problem: if unsubscribe links are made public and followed, the archiving address will be unsubscribed.
- Maybe unsubscribe links could be removed from each email and the unsubscribe link changed to http://example.com or http://archiveteam.org?
- Upload darkened copies of the original emails to IA along with the modified ones.
- Maybe unsubscribe links could be removed from each email and the unsubscribe link changed to http://example.com or http://archiveteam.org?
- Have a list of newsletters currently being saved to prevent saving multiple copies of the same newsletter.
Notes
- http://www.spamdex.org/ has a bunch of spam archives. Maybe we could collaborate OR at least see how they have it implemented in the backend..
