I'm currently working on a personal project: a local web app that aims to consolidate all my browser bookmarks, GitHub stars, YouTube playlist metadata, RSS feeds, notes, and more into one centralized hub.
For the bookmarks, I'm planning to create a browser extension that lets users select a page to store, which will send the URL to my backend. I also want to include an import function.
Regarding GitHub and YouTube, I'm thinking of using OAuth so that I can stay logged in and automatically fetch URLs from my accounts at regular intervals instead of adding them manually. Right now, I'm learning how to implement OAuth in FastAPI.
I would appreciate any advice on how to structure this project and whether I'm on the right track! Also, if there's a better way to implement this, I'd love to hear about it.
2 Answers
While I haven't dived into OAuth myself, have you considered scraping the data instead? Since it's a local web app, that could be a simpler approach.
Hey! I think your project is a great idea—it sounds like you're building a comprehensive dashboard for all your content. I recommend breaking it down into modules since you’re still in a learning phase. Using OAuth is definitely a smart choice, and don’t overlook the importance of a clean UI.
Also, make sure your backend is robust. Implement things like caching and retry logic to keep it running smoothly. Starting with a low-level design (LLD) could really help you map everything out. Good luck!
I appreciate the suggestion! However, I want this project to be future-proof. Scraping can be unreliable if the layout changes, and I’ll need to access metadata regularly, which wouldn’t work well with scraping. Plus, I’m eager to learn new techniques like OAuth while building this.