Quark's
Come to Quark’s, Quark’s is Fun!
General off-topic chat for the crew of startrek.website. Trek-adjacent discussions, other sci-fi television, navigating the Fediverse, server meta (within reason), selling expired cases of Yamok sauce, it’s all fair game.
If you're using Ublock Origin, disable that for your home lemmy instance.
I have a custom rule you can add to prevent that from happening (in lieu of disabling UBO), but it's on my other computer. I can update post with that later.
I have all tracker blockers/adblockers/etc disabled on my personal domains, so I don't think it's that.
Looking at it closer, if I pull up a post on my instance and open the image in a new tab, it gives this link: https://startrek.website/pictrs/image/2f9f0c5e-c579-465b-a0cc-734ce953a3a5.jpeg
But when I go to startrek.website and pull up the same post, the image URL is different, it's https://startrek.website/pictrs/image/7a02c5c7-9a8f-424f-9b56-f37664e6a8b8.jpeg
Even more curious is when I view the post on lemm.ee, since if I open the image in a new tab by clicking on the image, it pulls up the actual image but when clicking on the link to the image under the title it goes to the same wrong URL that my instance has
I'm getting this too, as well as some image posts occasionally not federating, and lots of error messages about "voting failed", "failed to mark as read", etc.
I know there were some expected temporary performance issues after switching hosts, but would that still be happening a week or so later?
Some of the image stuff for me is just my device caching urls that change, but I don't know why so many urls are changing
I'm not getting the failed to vote thing, but maybe that's because you are using startrek.website as your instance instead of another; probably just timing out because whenever I pull up the site it is always a bit slow to load
I post a lot, and multiple people on other instances have messaged me this week complaining that our images show up intermittently for them too.
I don't know enough about the technical side of lemmy to even hazard a guess though.
Yeah, all I can tell is that the url of the file on the server seems to be changing and devices are caching the old url. Using a different image hosting service like imgflip/catbox.moe/selfhosted image server for the image uploads would probably solve that problem, but that's pretty much the extent of my knowledge