Difference between revisions of "Project Newsletter"

From Archiveteam
Jump to: navigation, search
m
(Ideas)
Line 12: Line 12:
 
** Have a password protected page where people can click confirm links.
 
** 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.
 
*** First solution is better, but the second one could be used if the bot fails to properly follow the confirmation link.
 +
* Download image URLs in each email with wget.
 
* Upload received emails to IA in [[ArchiveBot]]-like GO packs, and separate files by the receiving account.
 
* Upload received emails to IA in [[ArchiveBot]]-like GO packs, and separate files by the receiving account.
 
* Provide an interface for reading archived emails.
 
* Provide an interface for reading archived emails.
Line 17: Line 18:
 
** Should it automatically create a new email address and try signing up for newsletters, or should there be some sort of human intervention?
 
** 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.
 
* 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?

Revision as of 00:37, 27 March 2015

Archiving all the email newsletters. Join the discussion in #projectnewsletter.

TODO TODO TODO

Ideas

  • Have a separate email address for each newsletter.
    • Have a page where people can create new email accounts and sign them up for newsletters.
    • Public access to the email addresses will need to be limited to prevent random spam from entering the archives.
    • 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.
  • Download image URLs in each email with wget.
  • Upload received emails to IA in ArchiveBot-like GO packs, and separate files by the receiving account.
  • 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.