AI 产品解读Anti-censorship proxy extension that unblocks access to Telegram, WhatsApp Web, Google Meet, X.com, and YouTube in regions where they are blocked
Users in countries with internet censorship cannot access popular messaging and social media services; this extension provides a browser-level proxy to bypass those restrictions
Install extension → click browser action icon → popup shows messenger shortcuts → select Telegram/WhatsApp/etc. → extension routes traffic through proxy (configured automatically from backend at uboost.space/ubst.space) → user accesses the blocked service directly in their browser
Browser proxy configuration via chrome.proxy API to route traffic through backend proxy serversOne-click messenger shortcuts (Telegram, WhatsApp Web, Google Meet, X.com) from the popupYouTube enhancement: ad pre-roll handling, video quality management, UI customization via content scriptsWelcome/onboarding pages on first install and updatesGoogle Analytics telemetry for usage tracking
- 目标用户
- Users in Russia and other countries with internet censorship who need access to Telegram, WhatsApp, YouTube, and X.com / Remote workers and freelancers relying on these services / General users wanting to maintain communication with contacts
- All main JS files (261.js, 343.js, default_popup.js, service_worker.js, content-*.js) are heavily minified/bundled with Sentry instrumentation, making deep code analysis unreliable
- The proxy credential provisioning mechanism is opaque — API endpoints use template variables (${e}, ${t}) obscuring actual server addresses
- Cannot determine if dynamic configuration fetched from uboost.space/ubst.space backends might introduce login or paywall requirements at runtime
付费分析未识别到付费功能
Store description explicitly states 'Абсолютно бесплатно - никаких скрытых платежей' (Absolutely free - no hidden payments). No payment API calls, billing endpoints, Stripe/Google Pay integration, or upgrade prompts found in source code. All 'subscription', 'premium', 'upgrade', 'payment method' keyword matches originate from minified Sentry/library bundle code (sentryDebugIds), not payment logic. CSS classes like [data-vpnn-locked] and .ytp-vpnn-lock-icon suggest UI-level locking of YouTube quality settings, likely a feature-state toggle rather than a paywall.
- 置信度
- 65
- 支付平台
- --
- 来源
- AI / 中
- 需要登录
- 否
- 登录理由
- No login UI or account creation flow found in the extension source code. All keyword hits for 'login', 'login required', and 'auth' are from Sentry error-tracking library boilerplate (sentryDebugIds), not actual authentication logic. The 'webRequestAuthProvider' permission in manifest.json line 12 handles HTTP proxy authentication challenges programmatically — it does not present a user-facing login form. The store description states 'Без сложных настроек - установил и забыл' (install and forget) suggesting no account setup is required for the core proxy workflow.