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.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/palo_alto_ai/rabbitholes-how-i-built-a-chrome-extension-with-no-server-to-touch-your-data-1bph |
| Publication time | Sun, 24 May 2026 14:56:53 +0000 |
| Retrieval time | 2026-05-24T15:07:33.299Z |
| Last seen | 2026-05-24T15:07:33.299Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | Ttx7Vntl8qdw |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
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)
