Lemmy.ca's Main Community

3283 readers

9 users here now

Welcome to the lemmy.ca/c/main community!

All new users on lemmy.ca are automatically subscribed to this community, so this is the place to read announcements, make suggestions, and chat about the goings-on of lemmy.ca.

For support requests specific to lemmy.ca, you can use [email protected].

founded 4 years ago

MODERATORS

160

We're now upgraded to 0.19.4 (self.main)

submitted 10 months ago* (last edited 10 months ago) by Shadow to c/main

35 comments fedilink hide all child comments

Sorry for the brief bits of downtime here and there, I snuck in a quick upgrade of us to the latest lemmy 0.19.4 now that a few bugs have been patched out.

More details here! https://join-lemmy.org/news/2024-06-07_-_Lemmy_Release_v0.19.4_-_Image_Proxying_and_Federation_improvements

you are viewing a single comment's thread
view the rest of the comments

[–] Shadow 3 points 10 months ago (1 children)

Try a private window as well, that will rule out any plugins or extensions causing it.

It really sounds like a cache issue though if you don't run into this on other instances. There's nothing special about our code.

[–] streetfestival 2 points 10 months ago (1 children)

Thank you, you've been very generous with your time and I don't want to take any more of it up. I tried cache clearing, private window, computer restart. I have one non-lemmy.ca account (lemmynsfw.com). I can view lemmy.ca communities fine from my nsfw account and there are no issues in general, but directly using lemmy.ca and using my lemmy.ca account no longer work (as described above). This stuff is beyond my comprehension but if it's only affecting me (which it seems to be based on the lack of other reports) than it's hardly an problem for the instance

[–] Shadow 3 points 10 months ago (1 children)

Try another instance on 0.19.4 like https://lemmy.ml/ and see if it happens there too. If so, it's your browser not liking something in the new version =)

[–] streetfestival 4 points 10 months ago* (last edited 10 months ago) (1 children)

Thanks! I recreated this issue with Safari and with lemmy.ml on both browsers. I think it's an issue with 0.19.4 interacting with something on my end, as I don't have the issue on any instance that isn't on 0.19.4 (and no other user seems to be affected). As a stop-gap solution, I've setup an account on beehaw.org. (Edit: another stop-gap solution: https://old.lemmy.ca/)

[–] Shadow 4 points 10 months ago (1 children)

https://github.com/LemmyNet/lemmy-ui/issues would be the place to go next

[–] streetfestival 4 points 10 months ago

I haven't used github before. I reluctantly updated FireFox to 127 (it was previously 109) and that fixed it. Thanks again =)