I don't even think all apps supported redgifs. I'm making a web app and… how in the fuck am I supposed to support that website? Other image hosts have an extension like .gif in their URL so that's easy, but what about redgifs? Am I supposed to hard-code something specifically for them? That doesn't sound right.
Don't forget that NewPipe × SponsorBlock is a fork that adds SponsorBlock. Also there's ReVanced to make YouTube bearable while still having access to your curated feed.
There's no Android build yet since it's easier to just focus on features first and deployment later, but I do plan on having a SSR build, a PWA build and an Android build.
It would surprise me if that was the explanation since this can be easily fixed by Lemmy.world itself by not sending two Accept-Control-Allow-Origin headers, thus breaking web clients.
Right now, I'm forced to route my own calls to my server on the app I'm making because Lemmy.world is misconfigured.
I guess that for instance below 0.18.1, it makes sense, since Lemmy had a bug at that point that didn't allow web clients to connect.
I'm making a web app at the moment for personal use. So far, you can scroll posts, sort, filter, upvote, downvote, view one comment page, view a user's posts, view a community's posts, subscribe / block users and communities... and that's about it
Ironically, since it doesn't have the blur NSFW post feature yet, it's a much better client for browsing NSFW communities than established clients :D
Absolutely not ready for prime time yet; there's no deployment, you have to build it from source and it you can't even comment. https://github.com/NatoBoram/Leanish
I don't even think all apps supported redgifs. I'm making a web app and… how in the fuck am I supposed to support that website? Other image hosts have an extension like
.gif
in their URL so that's easy, but what about redgifs? Am I supposed to hard-code something specifically for them? That doesn't sound right.