Chrome extension swaps DOM scraping for site's internal API, cutting AI Studio export from 150s to under 1s

·8 views

A developer built AI Studio Exporter, an open source Chrome extension, to export Google AI Studio conversations, which the site does not support natively. The first version scrolled the page and read messages from the DOM, which was slow, could miss messages, and captured only thumbnails of uploaded files. The second version instead calls the same undocumented internal API the AI Studio frontend uses, reducing exports of a 200-message conversation from about 150 seconds to under one second. Because the API's responses are unlabeled nested arrays, the developer built a decoder and tolerant helpers that degrade gracefully if Google changes the format. The extension runs a small script in the page's main context to get around a CORS restriction that blocks requests from extension content scripts.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Blogger Details Repeated Tampering With His Sonarr Setup by Torrent Site User

A developer published a blog post describing how someone repeatedly interfered with his Sonarr media-automation setup through torrent sites. The account is shared via a Hacker News link with only limited metadata available, so the specific methods and timeline are not confirmed here. The post has drawn a small amount of attention, with one comment so far. Readers wanting the full details of the incident are directed to the original blog post.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

Short link creator treats slug collisions as negotiations, not errors

The developer of a short link creator built custom slugs for AI agents, but initially returned a hard error whenever a slug was already taken. A collision with an abandoned link caused retry storms that saturated the rate limiter, prompting a redesign. Collisions now return the existing link with a flag, letting callers accept an auto-suffixed variant or reclaim a slug only if it has had no clicks in 90 days. The developer also found that agents losing their one-time manage secret create duplicate links for the same destination, and proposed making creation idempotent on destination and owner hint. The overall lesson is that link APIs should treat slug collisions, lost secrets, and moved destinations as normal operation.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Six documented ways to simplify a cluttered Zoho CRM

Zoho CRM can feel overwhelming when every user sees the same fields and records, so the platform offers several built-in ways to tailor the view for each role. Page layouts let a single module serve different processes, with distinct fields, sections and pick-list values assigned to profiles, though enabling this requires the Module Customization permission and edition checks. Layout rules can show or hide fields and sections or make them mandatory based on other entries, but they cannot remove fields and do not apply to imported, web-form or lead-convert records. Field permissions per profile let administrators set fields to read and write, read only, or hidden, with hidden fields blocked from viewing and editing rather than deleted. Custom list views, Kanban views and Canvas views then present records in task-focused formats, with the advice to keep columns under ten and build one view per daily need.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

NTP Clock Step Cost a Batch Job 40 Seconds of Its Budget, Field Notes Show

A developer's 20-minute batch job kept stopping early on a host where every API call was fast. The cause was deadline accounting that read the wall clock, which shifted during the run and made the job think more time had passed than it had. Switching to a monotonic clock would have prevented the early exits, and the author also points to a separate retry bug in parsing the Retry-After header. The author also notes the difficulty of confirming the clock adjustment's cause, since the affected server was not theirs to inspect. The post closes by describing how injecting the clock makes such failures testable on a local machine.

0 comments Read more at DEV Community