v2.0.0 — drop accessibility YouTube Shorts blocker, DNS-only release#15
Merged
Conversation
After v1.0.4 through v1.0.10 iterating on accessibility detection for YouTube Shorts, the approach proved too fragile: every YouTube redesign shifted view ids and class names, and chasing the changes turned into a treadmill of regressions (tabs back-pressed away, frame rate drops, unblocked in-player scrolling). Removing the entire codepath and pointing users at ReVanced's "Hide Shorts" patches for that case. Removed: - ShortsAccessibilityService.kt and its res/xml config - AndroidManifest <service> for the accessibility service - accessibility_service_description / _summary strings - YouTube Shorts and Shorts-detector-debug cards in MainActivity + activity_main.xml; corresponding fields, listeners, and isShortsAccessibilityEnabled / refresh* helpers in MainActivity Updated: - README: drop YouTube Shorts from title and feature list, replace "two engines" callout with a "why no YouTube Shorts" callout that recommends ReVanced, drop Engine 2 / detection-rules section, swap the YouTube-accessibility FAQ for a "What about YouTube Shorts?" pointer, drop accessibility install step - BlockingRules: comment now points at the README/ReVanced rather than the (now-deleted) accessibility service - versionCode 11 -> 12, versionName 1.0.10 -> 2.0.0 DNS blocking (Reels / TikTok / Snap / X) is unchanged. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
After v1.0.4 → v1.0.10 iterating on accessibility-based YouTube Shorts detection, the approach proved too fragile to ship reliably. Each YouTube redesign moved view IDs and class names, and chasing them turned into a regression treadmill (tabs back-pressed away in v1.0.6 and v1.0.9, frame rate drops in v1.0.7 and v1.0.8, in-player scroll unblocked in v1.0.9). Removing the entire codepath and pointing users at ReVanced for the YouTube case. DNS blocking (Reels / TikTok / Snap / X) is unchanged.
Removed
ShortsAccessibilityService.ktandres/xml/accessibility_service_config.xml<service>block for the accessibility service inAndroidManifest.xmlaccessibility_service_description/accessibility_service_summarystringsMainActivity+activity_main.xmlisShortsAccessibilityEnabled/refresh*helpers inMainActivityUpdated
BlockingRulescomment — points to the README / ReVanced instead of the (now-deleted) accessibility service.Why a major version bump
This drops a previously-shipped feature. Anyone updating from 1.0.x and relying on accessibility-based YouTube Shorts blocking will lose that capability — major version bump signals the breaking scope.
Test plan
🤖 Generated with Claude Code