Just checking you’re not in a state that passed one of those draconian porn verification laws? Redgifs is following suit with whichever states PornHub is blocking. Try launching the lemmy page in your browser directly and see what you get too.
this post was submitted on 26 Jun 2024
27 points (100.0% liked)
Connect for Lemmy App
2675 readers
1 users here now
A community for the mobile app Connect for Lemmy.
Links
founded 1 year ago
MODERATORS
Good call, hadn't even thought of that as a possibility!But nope (thankfully!), in a sane, blue, porn-friendly state, and looks like everything works for me in my browser.
Any NSFW settings within the app which might be blocking them?
Nope, I can see all NSFW posts that aren't linked to redgifs and maybe 25% of redgifs links load correctly, but 75% stay loading until the "Exception: failed to retrieve..." pops up as a banner at the bottom of my screen.
Try opening external, then deleting the "api" at the front of the link.
Opening external works; the bug is that the gifs don't load in the app
My browser also fails to open them, unless I make the following change:
NSFW WARNING!
Original link example: https://api.redgifs.com/v2/gifs/mediumaquamarinecharmingtahr/files/MediumaquamarineCharmingTahr-silent.mp4
Becomes: https://redgifs.com/ifr/mediumaquamarinecharmingtahr/
(Please forgive including NSFW link to demonstrate link modification)
There are 3 changes to the link: remove api, replace first two subdirectories with ifr, and remove last two items
Wanted to share in case anyone else has the same difficulty
It's the app, the same thing happened to sync a while back
{"error":{"code":"FileAccessDenied","message":"Access to this file was denied for your application.","status":403,"rtfm":"https://github.com/Redgifs/api/wiki/Embedding-gifs#file-access"},"docs":"https://github.com/Redgifs/api/wiki/Embedding-gifs#file-access"}
Did they manage a fix?
The last update was 4 months ago so no lol
Hi! This should now be fixed on Connect ver180(beta) as of today
There's a new update that appears to fix this issue fyi!
Try again, there was a new update about this.
Definitely seems to work better/more consistently now