the community !linux@sh.itjust.works only allows posts without a language set (aka undetermined).

this is a community setting.

i don’t think you have any understanding of what ech is.

regardless, we didn’t do any changes to images today.

there was an issue with image uploads, that should be fixed now.

can you please be more specific and provide an example showing what you’re referring to?

in short form, we have HAproxy running on a hetzner cloud VM for Lemmy/Lemmy-UI, another HAproxy VM for the alt UIs, a VM for the alt UIs.

for the main LW box, which runs lemmy containers, lemmy-ui, pictrs and a database each for lemmy and pictrs, we have a physical box with an EPYC 7502P 32 core CPU, 128GB memory and NVMe SSDs.

considering that we’re coming from 0.19.3, this does still introduce quite a few bigger changes for LW.

this will be fixed by the upcoming lemmy update iirc.

if they keep doing so one-sided, especially after being told not to do so, please report them via @lwreport@lemmy.world.

there are various mentioned in !syncforlemmy@lemmy.world, the main one i was referring to was the one where in some cases posts in local communities won’t show comments.

partial breakage, the stuff that people on other instances have already been experiencing for a while.

iirc there are still some additional issues with sync arising with the update, but it won’t be entirely broken.

at this point i don’t know what people are even talking about, anyone signing up since saturday should get an email if their account was denied.

it’s also impressive how many people can’t follow simple instructions.

reddit blocks data center IPs, therefore fetching the page title automatically doesn’t work

if the page doesn’t show anything that indicates that the verification isn’t valid anymore.

this can be the result of trying to verify after 7 days have passed (currently hardcoded limit in lemmy) or when the email has already been verified.

this isn’t something we have actively disabled.

newer lemmy versions have new functionality there that will take the thumbnail from the origin instance rather than always generating it locally, which explains why things may sometimes look slightly different than on other instances. the ability to set custom thumbnail urls is also only on newer lemmy versions.

once we’ve done the update, which should happen this month, that will also be the same on lemmy.world. a few days ago i did another test migration and it only took about 20 min for the db migrations while my previous test before the db upgrade took almost an hour, although i might have had different settings before in the test environment.

it doesn’t make a difference which community you’re trying to post it to, it’s likely an issue with that particular image.

do you have any more context?

based on this i’d just assume that pictrs didn’t like the video you tried to upload.

that has nothing to do with this issue.

we’re not running any modifications that would impact caching and we don’t have any custom caching logic. we’re only caching what lemmy/lemmy-ui return as cacheable, which suggests that the issue is likely in one of those services, however, i couldn’t find it in either one.

it’s also rare enough that it’s extremely difficult to troubleshoot, as we see people report this maybe once or twice every few months but without any useful information that would allow us to look into this further than trying to find bugs in related code just from the general symptom of seemingly invalid cache.

additionally, the impact of this should be fairly low, as, unless this somehow impacts private messages as well, no data would be returned that isn’t already otherwise public. with this seemingly “just” being a caching issue, there is also no risk at impersonating other users.

nonetheless i agree that this should not be happening in the first place, even if it’s rare and the impact appears limited.

I already followed various code paths to try and see where Lemmy might be setting incorrect caching headers without finding anything and nothing in the relevant code seems to have been changed between 0.19.3 and newer 0.19 releases.

I’m still unsure if we’re just seeing it more frequently due to a larger number of users and us also having a “proper” caching setup and in practice it would happen on other instances as well or whether it’s somehow something that others just don’t see due to not being on 0.19.3.

we’re still unsure what might be causing this, but we’ll be updating to 0.19.9 soon. maybe that’ll fix this issue.

you seem to be lost.

this community is about lemmy.world, not a general support community.

not at all. nobody can revert edits, only the creator can edit it again.

moderators can restore removed (mod action) posts and comments, but not deleted (creator action) posts and comments.