• Learned how to use react router
• Added styles, fonts and content to header and footer
• Added prettier tailwind plugin
• Structure right now is the following (where the header and footer are on all pages) / /listings /unsubscribe 404 page

Next up is the signup form (easy and might have done by tonight) and the listings pages (styling is going to be hardest part).

Lambda should no longer error out and cause retry. It should also now update the database before sending emails and finish sending all emails even when some are invalid.

Mailgun gives this error when sending to some domains: "Sender address rejected: Domain not found"

Seems like it could have something to do with DMARC or something. This impacts less than 20% of users.

It is possible that a user selects to be updated for both internships and new grad roles (intended behavior).

However, it is not clear what each post listed in our emails pertains to. We should just separate them in the email with some sort of heading or indicator next to the location.

Not urgent.

Rate Limiter will help short term. Need a way to ban IPs that are consistently spamming.

Ideas:

• Upon X number of 429 responses (essentially response saying "you're spamming"), we add to a Redis Banlist, and block any IP in Redist banlist upon future requests
  • Redis is in memory, so this isn't quite persistent, though it will "persist" long enough to satisfy our use case

Workflow

• User Signs up
• Backend stores user data in Redis Cache (or some other temp storage solution), along with an arbitrary UUID
• Fire off an email to the user with a link for confirmation (UUID appended in link)
• When verification is successful, fire request to backend with UUID
• We verify that UUID matches, and pull data out of Redis cache and enter into database

This is largely doable. Areas of concern

• Figuring out Redis with Go
• New email service to send out validation emails. I currently really like our separation of powers with respect to architecture and would like to stay away from adding email services into the Go API and going all monolith on things.
• UUID cycle needs to thought about more

AWS Simple Email Service gives 62,000 free emails per month forever if the requests are coming from a Lambda or EC2 application. After that, it's only $0.10 per 1,000 emails. Mailgun, although it's on the student pack, still only gives 20,000 free emails per month which we will theoretically surpass once we start having over 600 sign-ups. We therefore want to make this migration before trying to get the link put on the pittcsc/coderquad repos.

Should pretty much be a nicer version of the GitHub README's.

The 2 that we are using for Intern and New Grad respectively are:

• https://github.com/pittcsc/Summer2023-Internships
• https://github.com/coderQuad/New-Grad-Positions-2023

API Endpoint to get all job postings is a GET to: localhost:8080/postings/

• Returns the job postings in the following shape:

{
    "NewGradPosts": [{...}, {...}],
    "InternPosts": [{...}, {...}],
}

Just one page with 2 tabs to display the jobs in table form. 1 tab for intern posts, and the other for newgrad Route preferably: https://domain/joblistings, or something like that