Update news-2025.md

Author: thdoan

news-2025.md

@@ -1,9 +1,9 @@
 ## The future is in the cloud (June 26, 2025)
 
-Google finally got back to us regarding why v14 was rejected, and it has something to do with how we're coding the subscription verification logic. We'll try to refactor the code to comply, but this puts us at another fork in the road: we'll probably have to eventually migrate the Options page to be completely server-side. Frankly, this is what we should have done from the very beginning if we'd had enough resources and time then. This is how the big freemium extensions do it ([example](https://www.loom.com/)), and IMHO it's the correct way. Moving Options to the server has many upsides with only one minor downside:
+Google finally got back to us regarding why v14 was rejected, and it has something to do with how we're coding the subscription verification logic. We'll try to refactor the code to comply, but this puts us at another fork in the road: we'll probably have to eventually migrate the Options page to be completely server-side. Frankly, this is what we should have done from the very beginning if we'd had enough resources and time then. This is how the big freemium extensions do it (e.g., Loom), and "this is the way" 🤓. Moving Options to the server has many upsides with only one minor downside:
 
 * ➕ We can **continuously improve it** without having to go through the lengthy extension review process.
-* ➕ We have **complete control over our code** without having to meet stringent MV3 requirements ([example](https://chromewebstore.google.com/detail/ublock-origin/cjpalhdlnbpafiamejdnhcphjbkeiagm)).
+* ➕ We have **complete control over our code** without having to meet stringent MV3 requirements ([example](https://www.quippd.com/writing/2024/10/16/google-is-killing-uBlock-origin-no-chromium-browser-is-safe.html)).
 * ➕ **Better protection** from bad actors cracking the extension, etc.
 * ➖ The Options page will be a little slower to load.