Onlytaboocom Link — [patched]

Feature spec: OnlyTaboocom link (assumption: link-sharing/preview feature for OnlyTaboocom) Goal Allow users to paste an OnlyTaboocom link and get a safe, privacy-preserving preview + useful actions (open, copy, download, report). Assumptions

OnlyTaboocom is an external content site; links may point to user-generated media. Must avoid embedding or auto-loading remote media to protect privacy and bandwidth. Minimal metadata available via oEmbed/OpenGraph; fall back to HTTP HEAD for content-type. Respect robots headers and site CORS; do not fetch full remote content server-side unless necessary.

User stories

As a user, when I paste an OnlyTaboocom link, I see a compact preview with title, thumbnail, uploader, date, and safe actions. As a user, I can copy the raw link or open it in a new tab. As a user, I can download media only after an explicit confirm (no auto-download). As a user, I can report the link for policy violations; reporting sends anonymized metadata. As a developer, I can configure server-side fetch behavior (strict: only HEAD + metadata; permissive: fetch oEmbed/OpenGraph). onlytaboocom link

Behavior & UI

Input: single OnlyTaboocom URL. Output card (compact):

Thumbnail (deferred): show placeholder; display thumbnail only after user clicks "Load preview". Title (from OpenGraph / oEmbed / fallback: hostname + path). Uploader (if available). Date (if available). Content type badge (video/image/text). Size estimate (from HEAD Content-Length if available). As a user, I can copy the raw link or open it in a new tab

Actions:

Open (new tab) Copy link Load preview (fetch OG metadata + thumbnail; requires user consent) Download (explicit confirmation; show filename and size) Report (opens report modal with categories and optional comment)

Accessibility: keyboard-focusable, ARIA labels on buttons. Rate-limit server-side fetches per IP/session.

Privacy & Safety

Default: do not fetch remote thumbnails or media until user clicks "Load preview". Server fetches strip identifying request headers; use proxy that removes IP and cookies. Logs: only store URL hash + minimal metadata; no personal identifiers. Rate-limit server-side fetches per IP/session.