You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a way to stop the redirection of youtube links to piped-material? Recently, I've been getting a lot of issues with videos not loading/playing and constant stutters for buffing. If I were to clear my cache and try to sign back in, half the time it won't let me sign in; it just goes back to log in/sign up. When I refresh after that, it says error:"session is a required parameter".
I have a VPN, but terminating that has done nothing for this issue.
The text was updated successfully, but these errors were encountered:
On Saturday, October 28 2023 Anno Domini 03:39 AM India Standard Time, RionKatt wrote:
Hi
Is there a way to stop the redirection of youtube links to piped-material? Recently, I've been getting a lot of issues with videos not loading/playing and constant stutters for buffing. If I were to clear my cache and try to sign back in, half the time it won't let me sign in; it just goes back to log in/sign up.
Does it show an error in the console or the network logs?
Videos not loading or constant stuttering is usually a problem on the instance's side or YT rate-limiting the respective instance. It's not PM's fault.
When I refresh after that, it says error:"session is a required parameter".
Were you on the feed page (what was the path in the URL) when you faced this error?
I have a VPN, but terminating that has done nothing for this issue.
Hi
Is there a way to stop the redirection of youtube links to piped-material? Recently, I've been getting a lot of issues with videos not loading/playing and constant stutters for buffing. If I were to clear my cache and try to sign back in, half the time it won't let me sign in; it just goes back to log in/sign up. When I refresh after that, it says error:"session is a required parameter".
I have a VPN, but terminating that has done nothing for this issue.
The text was updated successfully, but these errors were encountered: