I recently made a video post using a link that I got from xcancel on a Twitter post. I can see the video when viewing from Lemmy, but when using PieFed, Voyager, and Blorp the video does not load.
The post I’m referring to:
~~https://piefed.social/c/starcitizen/p/2034751/in-my-experience-there-s-no-such-thing-as-luck~~
Edit with working link:
https://piefed.social/c/starcitizen@lemmy.world/p/2034751/in-my-experience-there-s-no-such-thing-as-luck
I have the same problem in both Firefox and Vivaldi on Linux and Windows. I’m getting a 403 error:
I see this in Vivaldi:
video.twimg.com/ext_tw_video/2051274778753781760/pu/vid/avc1/1280x720/DgFq_l1TNDVergoC.mp4:1 Failed to load resource: the server responded with a status of 403 ()
I saw this in FIrefox:
The resource at “https://video.twimg.com/ext_tw_video/2051274778753781760/pu/vid/avc1/1280x720/DgFq_l1TNDVergoC.mp4” was blocked because Enhanced Tracking Protection is enabled.
So, I turned off Enhanced Tracking Protection and I get the same 403 as in Vivaldi.
While my Firefox is on a VPN, my Vivaldi is not, so it’s not a VPN issue.
This doesn’t help you but it confirms you are not alone.
However, if I enter this into a private window, it plays: https://video.twimg.com/ext_tw_video/2051274778753781760/pu/vid/avc1/1280x720/DgFq_l1TNDVergoC.mp4
If PieFed sends a referer header, maybe X rejects it because it doesn’t like PieFed. Or maybe it doesn’t like the headers passed by PieFed? I’m guessing.
I ran this curl on my PieFed server and did not get a 403, but rather a 200
curl -I “https://video.twimg.com/ext_tw_video/2051274778753781760/pu/vid/avc1/1280x720/DgFq_l1TNDVergoC.mp4”
HTTP/2 200
I ran the curl on my desktop computer, connected to the VPN, and I got a 200.
So, not my VPN or IP address. If it fails in the browser but works in a curl, maybe it’s the referrer related to hotlink protection??