this post was submitted on 01 Jul 2023
306 points (100.0% liked)
Technology
37735 readers
54 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Piped js no longer working since YT started blocking Ad-blockers.
What do you mean exactly? I just tried it and it and Piped seems to work just fine.
EDIT: Found what someone else said. Basically have to bounce instances and find one that it'll work on, since they rate limit instances at times.....
Initial player response is not valid
org.schabi.newpipe.extractor.exceptions.ExtractionException: Initial player response is not valid
at org.schabi.newpipe.extractor.services.youtube.extractors.YoutubeStreamExtractor.onFetchPage(YoutubeStreamExtractor.java:904)
at org.schabi.newpipe.extractor.Extractor.fetchPage(Extractor.java:60)
at org.schabi.newpipe.extractor.stream.StreamInfo.getInfo(StreamInfo.java:78)
at org.schabi.newpipe.extractor.stream.StreamInfo.getInfo(StreamInfo.java:73)
at org.schabi.newpipe.extractor.stream.StreamInfo.getInfo(StreamInfo.java:68)
at me.kavin.piped.server.handlers.StreamHandlers.lambda$streamsResponse$0(StreamHandlers.java:55)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:833)
that's weird, it's working fine for me. maybe you could try hopping to a smaller instance and see if that helps? maybe it's also a regional thing im unaware of.