From 238231051c5ab976758b0e709e0f2eeb7b456bc6 Mon Sep 17 00:00:00 2001 From: Nicholas Orlowsky Date: Sat, 27 Sep 2025 11:47:50 -0400 Subject: [PATCH] finish the unfinished sentence in 7-12 --- src/blogs/side-project-7-12-23.filler.html | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/src/blogs/side-project-7-12-23.filler.html b/src/blogs/side-project-7-12-23.filler.html index e025f64..bc2bb9d 100644 --- a/src/blogs/side-project-7-12-23.filler.html +++ b/src/blogs/side-project-7-12-23.filler.html @@ -55,7 +55,9 @@ however I'd still have to jump through hoops to get an Autonomous System num in the coming weeks.

  • Reduced External Dependence: The main goal of NWS is to have no external dependence. In theory, everything but core internet infrastructure -should

    +should be done in-house. From what I can gather, migrating off of using Cloudflare for DNS + load balancing/failover would require that I am able to setup anycast so that + if one PoP goes down, traffic will still be routed to the others.

    • Olney

    @@ -63,7 +65,7 @@ should

    Olney is a new project I am starting with my friend Sridhar Nandigam. It aims to make tracking your job applications easier. Most of my friends either use spreadsheets or Trello to track their job applications, I think that we can make something that's a bit better for the job. Some features I'd like to have are: resume version attached to -your application, job posting notifications from job boards such as pittcsc, and watching +your application, job posting notifications from job boards such as pittcsc, and watching your email for emails from recruiters. Currently, I have part of the backend setup with basic CRUD operations. Now that I'm done with the latest batch of NWS work, this is next on my list to work on.