
gittech. site
for different kinds of informations and explorations.
Unbaited β Control your X feed with LLMs. Browser extension that filters bait
Published at
2 days ago
Main Article
unbaited
Control your X feed with an LLM of your choice from Groq. A browser extension that helps you filter out engagement bait and inflammatory content from your X (formerly Twitter) feed.
How it works
The extension uses Groq's ultra-fast API to analyze tweets using a model of your choice. When you scroll through X, it:
- Detects new tweets as they appear in your viewport
- Sends the tweet content (only text as of now) to Groq's API for analysis
- Blurs tweets that are identified as engagement bait, political tweets, etc.
- Gives you the option to reveal hidden tweets with a single click
Installation
Chrome/Safari
- Install the extension from the Chrome Web Store
- Get your API key from Groq
- Open the extension settings and enter your API key
- Optionally customize the system prompt to adjust how tweets are analyzed
Firefox
- Install the extension from Mozilla Add-ons
- Get your API key from Groq
- Open the extension settings and enter your API key
- Optionally customize the system prompt to adjust how tweets are analyzed
Browser Support
- Chrome: β Full support
- Firefox: β Full support
- Safari: β Full support
Development
The project consists of two parts:
extension/
: The Chrome extensionlanding/
: The landing page built with Next.js
Extension Development
cd extension
npm i
npm build
Loading in browsers
Chrome/Safari
Load the extension/dist
directory as an unpacked extension:
- Open Chrome/Safari
- Go to Extensions page
- Enable Developer Mode
- Click "Load unpacked" and select the
extension/dist
directory
Firefox
Load the extension temporarily:
- Open Firefox
- Go to
about:debugging
- Click "This Firefox"
- Click "Load Temporary Add-on"
- Select any file in the
extension/dist
directory
Implementation Notes
The extension uses different approaches for background processing:
- Chrome/Safari: Uses Service Workers (MV3)
- Firefox: Uses Background Scripts (MV3 with scripts fallback)
This is handled automatically in the code, but when testing make sure to verify functionality in both environments.