mirror of
https://github.com/laylavish/uBlockOrigin-HUGE-AI-Blocklist.git
synced 2026-08-06 02:12:35 -04:00
[GH-ISSUE #332] alternatehistory.com gets removed from Google search results #227
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: DYNR/uBlockOrigin-HUGE-AI-Blocklist#227
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @TheWitheredStriker on GitHub (Feb 23, 2026).
Original GitHub issue: https://github.com/laylavish/uBlockOrigin-HUGE-AI-Blocklist/issues/332
Before:
After:
No idea why this occurs. I checked the filter list and found nothing that seems to target it.
It's a XenForo forum. AI-generated content is not permitted on it.
@TimGeel1998 commented on GitHub (Feb 24, 2026):
I think this is because of the following entry:
google.com##a[href*="story.com"]:upward(2):remove()
the wildcard (*) takes everything in front of "story.com"
this includes alternatehistory.com
I think if you change the a[href*="story.com"] and change it to a[href$="story.com"]
it should only look for an exactly this ending of the string.
and it should no longer match alternatehistory.com
I found this on: https://www.w3.org/TR/selectors-3/#attribute-substrings
but i could be wrong as i have never done anything like this before.
@TheWitheredStriker commented on GitHub (Feb 24, 2026):
I think that's likely the cause! Would be cool to see it fixed.
@TimGeel1998 commented on GitHub (Feb 24, 2026):
I have created a PR (#334) to potentially fix this issue.
We'll see if it gets merged
@TheWitheredStriker commented on GitHub (Feb 24, 2026):
Thank you!
@TimGeel1998 commented on GitHub (Mar 6, 2026):
Hello @TheWitheredStriker the idea we had submitted in PR (#334) do not seem to have the effect we wanted.
You can read the replay there for more info.
I will try to think of a solution but i cant promise a fix in the short term.
@TheWitheredStriker commented on GitHub (Mar 6, 2026):
No worries. Keep me updated.