AI 产品解读Block raid (host) auto-redirects on Kick.com
Prevents viewers from being automatically redirected to another streamer's channel when a streamer ends their broadcast and hosts another channel (a practice known as 'raiding' or 'hosting' that can be annoying to viewers who want to stay).
The extension injects a content script into kick.com pages. It monitors the DOM for raid dialogs (popups asking to join a host). When detected, it checks the user's settings (block mode, allow/block lists, schedule). If the raid should be blocked, it automatically clicks the 'Reject' or 'Cancel' button on the dialog. Users can configure settings via the extension popup.
Automatically blocks raid redirectsAllow/Block list management for specific streamersScheduled blocking (force block during specific time ranges)Notification when a raid is blockedMulti-language support (Japanese/English)
- 目标用户
- Kick.com viewers who dislike being auto-redirected when a streamer ends / Users who want to control which streamers' raids they accept
- The extension relies on Kick.com's UI structure (class names, dialog roles) to detect raids. If Kick changes their UI, the extension might break or need updates.
- The extension does not handle the case where a user might want to manually review raids; it blocks them automatically based on settings.
付费分析未识别到付费功能
The extension is free. There are no references to payment gateways, subscription management, premium features, or upgrade prompts within the extension code. The keyword 'subscribe' found in content.js is part of a list of UI labels to ignore/filter when detecting raid dialogs (e.g., distinguishing a raid dialog from a subscription prompt), not an implementation of a paid feature.
- 置信度
- 95
- 支付平台
- --
- 来源
- AI / 高
- 需要登录
- 否
- 登录理由
- The extension itself does not implement any login mechanism. It operates as a local content script on kick.com. While Kick.com (the destination service) generally requires login to watch streams or interact, the extension's core function (blocking raid redirects) can technically be triggered by the content script if the user is already on the site. However, the extension does not gate its own features behind a login. The extension does not collect data or communicate with external servers for authentication.