- Reasoning for project closure:
- The method as designed is likely to be "filtered as spam by the companies email filters."
- Implementing a Playwright script would be tedious as every website would need a different script.
- This effort could therefore instead be better spent manually deleting each account.
- Reflections:
- Using Mermaid.js for the first time, I found it to be a hassle. Excalidraw serves much better for diagramming.
GOAL contact customer service (known forward as "support") of given companies/websites with request to delete account.
- information:
- possible contacts:
- Thorin Klosowski - Wirecutter @ New York Times
- DeleteMe
- unroll.me
- notes:
- college emails, from Handshake: "If you no longer have access to the Student email address associated with your account, please get in touch with your university's career center to have it deleted."
-
GOAL: quickly delete many (even hundreds) of online accounts.
-
FUNCTION: automate "Request for Account Deletion" emails
-
CONSIDERATIONS: legality, follow-ups, inability to delete account via email, non-cooperation, multiple support addresses for single company
-
SCOPE CREEP:
- one user email vs many
- pre-sorted vs sorting
- pre-compacted vs compacting
- pre-reqs
- accounts.csv
- format: email,username,company
- email_template
- variables: support_emails, user_email, company_name, username, signature_name
- accounts.csv
- program steps
- data handling
- variables:
- uhh
- optional: log into user_email & store senders? - inspo: gh.com/Gobutsu/Conan
- ingest email_template
- store email_template
- ingest accounts.csv
- store account_list
- variables:
- support email gathering
- collect support emails of companies listed
- check sources:
- dns registry?
- open dataset?
- data.gov, kaggle datasets
- business directories!
- yelp fusion API, yellow pages?, chamber of commerce?
- web scrape?
- gh repos?
- online search
- i.e. site:blizzard.com "support email"
- or "contact"...?
- i.e. site:blizzard.com "support email"
- confirm email validity?
- check sources:
- store in company_list
- collect support emails of companies listed
- make emails
- construct sample using template
- choose first company
- replace variables
- output email for user preview
- user confirmation
- construct all emails
- iterate company_list
- new email
- replace variables
- store to email_list
- iterate
- new email
- iterate company_list
- construct sample using template
- send emails
- user confirmation
- iterate email_list
- send
- print success/fail
- iterate
- data handling