318
Voyager app users
102
Radiation fog in Dane County, Wisconsin [OC]
(vger.social)
cross-posted from: https://vger.social/post/6164807
Radiation fog - Dane County, Wisconsin
14
Lots of 429s and broken images from mander.xyz
(vger.social)
Anyone else noticing? It seems to be affecting other instances as well, since instances hot link to eachother.
The rate limiting seems to get much worse in the evenings.
lemmy.world:
mander.xyz:
{
"code": "object-request-error",
"msg": "Invalid status 429 Too Many Requests for Some(\\"01/90/24/ad/1d/8d/7e/8a/82/ee/7104ff150707.png\\") - {\n \\"message\\":\\"Too many requests\\"\n}"
}
Definitely for the PWA and f-droid builds, but idk how happy Google and Apple would be to have an app doing this in their stores. IANAL
spoiler u
did
spoiler u
know
spoiler nest
can
spoiler dog pic
spoilers?
Hi there!
So, I've investigated this problem many times, and in the case of your example post its the same issue I've seen before.
On your instance (mander.xyz), the image is not available. As an example, try to load the following link (in your browser):
https://mander.xyz/post/15080092 (MUST OPEN IN BROWSER)
As you can see the image is broken, because the image is not cached on mander.xyz, and also the original link is broken.
However, when you tap the "link" button in Voyager you are viewing the post on feddit.org where the image is cached. That's why this works:
https://feddit.org/post/538582 (MUST OPEN IN BROWSER)
This also explains why the image works for some people and not others. Because at some point the original image link broke, and some instances had the image cached by then, but not others.
That's also why usually the image will work on the origin server (in this case, feddit.org). Because the image was originally posted there, and that server was the first one to cache it (before the origin image broke).
I've thought about some workarounds for this scenario. Voyager could theoretically request the post payload from the origin lemmy instance (AP URL) and then use that cached image URL. However, this reduces privacy somewhat because your lemmy app is now connecting to an arbitrary lemmy instance.
Maybe it will be a setting in the future.
As others said, other apps are also affected by this issue because it's not a Voyager specific issue.
Another side note, this could potentially be fixed in Lemmy backend. Lemmy devs could fetch the cached image from the upstream Lemmy server instead of using the original image URL, if it is broken.
Edit: I made a request in Lemmy issue tracker. https://github.com/LemmyNet/lemmy/issues/4899
Hahahah
the onion
😢
Ironically Lemmy captcha does
They don’t try to kill you. They just try to propagate. If it kills you on the way, 🤷♂️
Yes, that's possible in the next version of Lemmy.
But it will probably be some buried option to enable (unless you're a mod). up up down down left right left right b a start. I don't want people to unintentionally view abusive comments (would risk store listing).
If they want our loyalty, make fucking better cars
I mean, in the spirit of the post, make fucking cheaper cars
Cars have been getting expensive AF
Good. Also you shouldn’t need a relationship with a corporation (account) to get information from government agencies…
view more: next ›
This is an iOS bug that got introduced within the last year. Basically, the indexed DB API just crashes. You can restart the app when this happens and it should be fine. Hopefully Apple fixes it soon…