I’m proud of my state!!
Anyone that shows up at the ER in America legally has to be accepted and stabilized before discharge. They will be sure to bill you though.
Oh also
I keep seeing Starlink pics claimed as drones…
Of course! Thanks for the kind words. I’ve been enjoying the late summer weather so no big updates lately, but when things cool down (literally) I will have more time for some things I want to add/fix :)
cross-posted from: https://vger.social/post/6164807
Radiation fog - Dane County, Wisconsin
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}"
}
🧐
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
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…
lemmy.ml is an important testbed for new releases at scale. Many many issues have been caught by the dev team deploying there. lemm.ee too for that matter.
I do agree that Lemmy.ml should never be recommended as the “official” Lemmy instance, but (correct me if I’m wrong) the Lemmy devs don’t do that. They just say “A community of privacy and FOSS enthusiasts, run by Lemmy’s developers“ which is fair to disclose (although maybe that could remove that. Idk). join-lemmy.org doesn’t handle or recommend Lemmy.ml specially.
I think usually it’s random users saying “join Lemmy.ml it’s the official instance” and we need to nip that in the bud… but it’s not Lemmy devs’ fault.