Send to lool

Right-click any image, video, link, or text and send it to your lool chats, contacts, or email.

# Send to lool A Chrome extension that adds a Send to lool item to the browser's right-click menu for images, videos, links, and selected text. Picking it opens the share menu of your self-hosted lool instance, allowing you to quickly send web content to your chats, contacts, or email. How it works - Right-click any image, video, link, or selected text on a webpage. - Select Send to lool. - The extension safely packages the content and opens your configured lool instance. - A floating share menu appears inside lool, letting you pick the exact chat, contact, or email thread to send it to. Privacy & Data Usage This extension is designed with privacy as a priority and adheres to Chrome Web Store's Limited Use requirements: - No Data Collection: The extension does not collect, store, or transmit any personal data, browsing history, or analytics to any third party. - Direct Connection Only: It only connects to the specific lool base URL you configure in the extension settings and the URL of the media/content you explicitly right-click. - No Remote Code: All code is contained within the extension package. No external scripts or dynamic code execution are used. Permissions Justification - `contextMenus`: Required to add the "Send to lool" option to the browser's right-click menu. - `scripting`, `tabs`, `activeTab`: Required to open or focus your lool tab and pass the selected content to the lool page. - `storage`: Required to remember your configured lool base URL and preferences. - `host_permissions: <all_urls>`: Required so the extension can read the media URL from the page you are actively right-clicking on, and so it can interact with your self-hosted lool instance (which could be on any domain). Setup & Installation 1. Open `chrome://extensions` and enable Developer mode. 2. Click Load unpacked and choose this folder. 3. Right-click the extension icon and select Options. 4. Enter your lool base URL (e.g., `https://chat.example.com/lool/`) and click Save. For Developers The extension is built using Manifest V3. - `background.js`: Handles context menu clicks, fetches media blobs from the active tab, and injects the payload into the lool tab. - `substack.js`: A content script that adds a "Send to lool" button to Substack's native share menus. - `options.html/js`: The settings page to configure the lool URL. - Icons: Generated via `icons/generate.html`. Save the three PNGs into the `icons/` folder before packaging. To package for the Chrome Web Store, zip the *contents* of this folder (ensure `manifest.json` is at the root of the zip). ---- # 1. Single purpose description Copy and paste this exactly: > Send selected web content to a user-hosted lool instance. # 2. Permission Justifications You will see a list of permissions. Paste these exact texts into their respective boxes: * activeTab: > Required to read the active tab's URL and inject the necessary scripts into the lool instance to trigger the share menu when the user initiates a share. * contextMenus: > Required to add the "Send to lool" option to the browser's right-click context menu for images, videos, links, and text. * host permission use (or `<all_urls>`): > Needed so the user can capture images and links from any webpage they right-click on. It is also required to communicate with the user's self-hosted lool instance, which can be hosted on any domain. * remote code use: > The extension does not execute any remote code. All JavaScript logic is entirely contained within the packaged .js files. * scripting: > Required to inject the content sharing script into the user's lool web app to open the destination picker (`window.Shr.sheet`). * storage: > Required to locally remember the user's configured lool base URL and their auto-send preferences. * tabs: > Required to find the user's open lool tab, focus it, and read its URL to verify it matches the configured base URL before sending the payload. # 3. Data Usage Certification Scroll down to the "Data usage" section. You will see a checkbox that says something like: > "I certify that my data usage complies with the Developer Program Policies..." Check this box. (Your extension only processes data locally and sends it to the user's own server; it does not collect or sell data). # 4. Publisher Contact Email & Verification This is on a different page in the dashboard: 1. Look at the left-hand sidebar in the Developer Dashboard and click on Settings (or Account). 2. Under the Publisher section, enter your email address (the one you want Google and users to contact you at). 3. Click Verify. 4. Go to your email inbox, find the email from Google, and click the verification link. 5. Go back to your extension's edit page, refresh the page, and the error will be gone.