See here for a description of what I'm doing: https://poal.co/s/technology/569412 Did a lot of reading today. Looked into react, and pug and how extensions work in general. Read about manifest v2 vs v3. v3 is being pushed by google and cripples the functionality of extensions, in a way that makes ad-block harder. Doesn't seem like it will hurt what I'm doing, but it is another complication, since most guides and tutorials are written for v2. https://www.adtoniq.io/blog/the-real-story-behind-chrome-manifest-v3-google-is-protecting-their-revenue-at-the-expense-of-users Also read about mozilla's promises architecture, which is a pretty cool way to handle asynchronized functionality and web-ext which should work well against firefox, chrome, and safari. Trying to decide on an architecture. I'm thinking that most of the code is going to be hosted on captaindirgo.com and loaded dynamically by the extension. This way I can push updates without everyone having to manually update their extension to the next version all the time. Normally you wouldn't need to worry about this because extensions loaded from the store automatically update, but since this project is probably going to be banned from the extension stores just like dissenter was, if I need to change the extension code, the user would have to redownload it from captaindirgo.com to see the changes. Also, I'm a little worried about mobile browsers and how to make them work. If I have most of the code on the web, I can more easily get them running. In any case, all the code, the extension code and the web server is going to be open sourced. Also trying to decide whether to keep using gulp or switch to webpack to handle building. Not really that concerned about it, but since chrome is phasing out manifest v2, and firefox doesn't even support manifest v3 yet (fucking corporate politics), the builder has to be flexible enough to handle vastly varying environments.