rabbitholes: how I built a Chrome extension with no server to touch your data
The article discusses the development of a Chrome extension called 'rabbitholes' that prioritizes user privacy by eliminating the need for a server. Unlike traditional extensions that route data through developer-controlled servers, this extension connects directly to APIs without logging user data. The architecture allows for compliance with Manifest V3 while providing a seamless user experience for text highlighting and inline explanations.
- ▪Most browser extensions route user data through a developer-controlled server, which can compromise privacy.
- ▪The 'rabbitholes' extension connects directly to APIs, ensuring that no intermediary server logs user data.
- ▪The extension allows users to highlight text and receive inline explanations without polluting the host page's styles.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3875408) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } J Now Posted on May 24 rabbitholes: how I built a Chrome extension with no server to touch your data #ai #javascript #privacy #showdev Most browser extensions that call external APIs route your data through a developer-controlled server first. That's not a conspiracy — it's the path of least resistance. You stand up a backend, proxy requests through it, log errors, maybe cache responses.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
