hi,
thanks for this grate addon, now I can block all this brown garbage that the stupid YouTube music algorithm recommends to me... But i found one issue, i let AI describe it so you dont have to understand my english writing
When using the context-menu blocking feature on an artist detail page, YTM Block appears to use the currently playing track/artist as the blocking context, even when that playback is happening in another YouTube Music tab/window.
What happened
I had music from one of my favorite artists playing in another YouTube Music window/tab.
In a separate tab I opened this artist page:
https://music.youtube.com/@DeutschrockOfficial (dont go there, they are evil just an example i dont want to promote them in any way)
I then used YTM Block on that detail page intending to block the artist displayed on that page.
Instead, the extension apparently blocked the artist that was currently playing in the other tab/window.
As a result, it immediately started skipping through essentially all songs from my favorite artist. The rapid skipping became so aggressive that the browser nearly became unresponsive. I was also concerned that the resulting stream of automatic YouTube Music requests could potentially look abusive to YouTube.
Expected behavior
When the blocking action is invoked from an artist/album/song detail page, YTM Block should use the entity belonging to that page or the element on which the context menu was opened, not the globally/currently playing entity from another tab.
For example, on:
music.youtube.com/@DeutschrockOfficial
choosing Block Artist should block Deutschrock, regardless of what happens to be playing elsewhere.
If the extension cannot reliably determine which entity the user intended to block, it should ask for confirmation, for example:
Block artist “Deutschrock”?
It should especially not fall back silently to the currently playing artist from another tab.
Suggested safeguard
Before adding an artist to the blocklist:
- Prefer the entity associated with the clicked DOM element/current detail page.
- Never obtain the blocking target from playback state belonging to another tab.
- If the target is ambiguous, show a confirmation dialog containing the exact artist/song/album name.
- Ideally, prevent a newly created block rule from triggering an uncontrolled rapid-skip loop.
This is potentially destructive because a single mistaken context-menu action can block an unrelated artist and immediately cause dozens of tracks to be skipped before the user realizes what happened.
thanks in advance and keep up the good work
hi,
thanks for this grate addon, now I can block all this brown garbage that the stupid YouTube music algorithm recommends to me... But i found one issue, i let AI describe it so you dont have to understand my english writing
When using the context-menu blocking feature on an artist detail page, YTM Block appears to use the currently playing track/artist as the blocking context, even when that playback is happening in another YouTube Music tab/window.
What happened
I had music from one of my favorite artists playing in another YouTube Music window/tab.
In a separate tab I opened this artist page:
https://music.youtube.com/@DeutschrockOfficial(dont go there, they are evil just an example i dont want to promote them in any way)I then used YTM Block on that detail page intending to block the artist displayed on that page.
Instead, the extension apparently blocked the artist that was currently playing in the other tab/window.
As a result, it immediately started skipping through essentially all songs from my favorite artist. The rapid skipping became so aggressive that the browser nearly became unresponsive. I was also concerned that the resulting stream of automatic YouTube Music requests could potentially look abusive to YouTube.
Expected behavior
When the blocking action is invoked from an artist/album/song detail page, YTM Block should use the entity belonging to that page or the element on which the context menu was opened, not the globally/currently playing entity from another tab.
For example, on:
music.youtube.com/@DeutschrockOfficialchoosing Block Artist should block
Deutschrock, regardless of what happens to be playing elsewhere.If the extension cannot reliably determine which entity the user intended to block, it should ask for confirmation, for example:
It should especially not fall back silently to the currently playing artist from another tab.
Suggested safeguard
Before adding an artist to the blocklist:
This is potentially destructive because a single mistaken context-menu action can block an unrelated artist and immediately cause dozens of tracks to be skipped before the user realizes what happened.
thanks in advance and keep up the good work