• 0 Posts
  • 18 Comments
Joined 1 year ago
cake
Cake day: February 10th, 2024

help-circle








  • 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.





  • 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.