fanboy, in your first post you told me to try adding a rule to see if it helped. i was skeptical that it would help since i figured that the easyprivacy-rule that caused the problem in the first place would still be in affect, which it was, and so the problem persisted.
the same with the second rule that you told me to try adding to my custom blocklist: the easyprivacy rule that caused the problem in the first place was still in affect and so the problem persisted.
maybe there is some mis-communication. did you mean for me to disable the rule in the easyprivacy blocklist that is causing "pov.spectrum.net" to be blocked? if so, i don't know how to do that.
as long as the rule that is causing "pov.spectrum.net" to be blocked remains in the easyprivacy blocklist, i don't think that adding more rules is going to disable that rule.
you can test things yourself by going to the spectrum login page, then clicking "sign in," which takes you to "id.spectrum.net." on the "id.spectrum.net" webpage, "ublock origin" shows that "pov.spectrum.net" is blocked.
you don't have to be able to sign in to spectrum.net. you still can see that "pov.spectrum.net" is being blocked on the "id.spectrum.net" webpage without logging in to a spectrum account.
incidentally, the "id.spectrum.net" webpage will show some kind of "error message" if you refresh the webpage. that "error message" comes up when the login was not successful, for one reason or another. it can be ignored.
maybe the way to solve the problem would be to make an "exception" for the rule that is blocking "pov.spectrum.net" for the "id.spectrum.net" webpage?
https://i.ibb.co/41H4wks/Spectrum-EP2.jpg