Telli.sh: Every Translator 1.30.0
Publisher verification summary
Published: September 30, 2026 (Korean Standard Time)

This is Telli.sh's own release verification summary, prepared from the
maintainer's implementation, automated-test and live-check records. It is
not an independent translation-quality benchmark or a guarantee that every
page on every supported host will continue to work.

Availability at the release check
- Web and API changes were deployed.
- Extension 1.30.0 was uploaded and submitted to Chrome Web Store review.
- Review was pending. The public store version was still 1.29.6.
- A submitted package is not yet a generally available store update.

Public destinations
Feature guide: https://telli.sh/every-translator
Store: https://chromewebstore.google.com/detail/tellish-every-translator/acmibhgmpgepnidlbfmolmobdpfbigol
Privacy: https://telli.sh/every-translator/privacy-policy

Implemented reading changes
- Paragraph and whole-block translation units.
- Spotlight display: hover/select prepares an action; Translate sends it.
- Fold/reopen reuses unchanged results; refresh requests another translation.
- Semantic text handling preserves the original and skips code/editable text.
- Whole-article processing retains a 20,000-character cap.
- Medium, Cnblogs, SegmentFault and 51CTO adapters added; Juejin and CSDN
  handling repaired/improved; Substack and DEV heading/nesting improvements.
- The catalogue reflects 36 implemented adapters, not placeholder names.
- YouTube scope: description and loaded comments, not subtitles or dubbing.

Live checks
- Korean translation was exercised on Medium, Substack, DEV, Cnblogs,
  SegmentFault, 51CTO, Juejin and CSDN pages. CSDN's normal security challenge
  was completed by the user, not bypassed.
- A Medium Clip save was checked for URL, title, selected material and derived
  summary output. This did not establish full-article archival coverage.
- The first new Clip connection check failed before its API endpoint was
  deployed. After deployment, the server check succeeded and the user
  confirmed success without reentering the stored token.
- An authenticated site request was submitted and its administrator status
  was checked through the request workflow.

Connection and request boundaries
- Clip is opt-in and saving requires an explicit action.
- A connection check creates no note and consumes no note quota.
- Candidate tokens are tested before replacement; failed replacement retains
  the previous token. Empty/unchanged Connect actions are disabled.
- Site requests require a verified account, apply user/domain deduplication,
  allow 3 new domains per rolling 24 hours, and apply an account limit of
  5 requests/minute. The short-interval limiter is process-local.
- Request input is bounded and submission does not fetch the submitted URL
  or launch an AI job. These controls are not complete DDoS protection.

Automated evidence for the 1.30.0 release revision
- Extension: 236 tests passed.
- Frontend: 126 suites, 1,176 tests passed.
- Targeted release E2E: 20 tests passed.
- Extension interface verification included 50 locales and narrow/desktop
  reading surfaces; website release pages included 15 locales.
- The recorded outcomes are revision-specific. Provider behavior, site
  markup, authentication and browser conditions can change after release.

Media disclosure
The blog and YouTube product illustrations use the real extension UI with
authored sample content and fixed translation responses. They illustrate
layout and are not measured provider performance or quality evidence.