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.
Hey, that’s like an IPFS gateway
It would help on other websites and on some in-app ads from mobile devices
You should try it, you’ll see it’s not that bad. It has an overlay that pops up when you open a link with it, so it’s actually a pleasant experience.
https://play.google.com/store/apps/details?id=com.ensoft.imgurviewer
Hi! I noticed an issue with the headers sent by Lemmy.world.
Headers sent from and to this website’s official UI look like this:
HTTP/1.1 200 OK
server: nginx/1.18.0 (Ubuntu)
date: Fri, 07 Jul 2023 23:35:17 GMT
content-type: application/json
vary: accept-encoding, Origin, Access-Control-Request-Method, Access-Control-Request-Headers
content-encoding: gzip
access-control-allow-origin: *
access-control-allow-methods: GET, POST, PUT, OPTIONS
access-control-allow-headers: DNT,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Range
access-control-expose-headers: content-encoding, content-type, vary, Content-Length,Content-Range
X-Firefox-Spdy: h2
Which is fine. However, headers received by custom clients look like this:
HTTP/2 200 OK
server: nginx/1.18.0 (Ubuntu)
date: Fri, 07 Jul 2023 23:33:50 GMT
content-type: application/json
vary: accept-encoding, Origin, Access-Control-Request-Method, Access-Control-Request-Headers
content-encoding: gzip
access-control-allow-origin: https://natoboram.github.io
access-control-expose-headers: content-encoding, access-control-allow-origin, content-type, vary
access-control-allow-origin: *
access-control-allow-methods: GET, POST, PUT, OPTIONS
access-control-allow-headers: DNT,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Range
access-control-expose-headers: Content-Length,Content-Range
X-Firefox-Spdy: h2
There’s two access-control-allow-origin! This still breaks web clients.
Firefox has built-in ads (that you can disable) on the home page.
Not as hot garbage as Brave cryptoscamming and replacing ads with their own and hijacking affiliate links, but it might be of interest if you want to try Firefox.