this post was submitted on 17 Jul 2025
3 points (100.0% liked)

Lemmy Support

4940 readers
1 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 6 years ago
MODERATORS
dessalines@lemmy.ml
3
bug: missing cache invalidation when renaming community (reddthat.com)
submitted 1 week ago by al_gore_rhythm@reddthat.com to c/lemmy_support@lemmy.ml
8 comments fedilink hide all child comments
 

steps to reproduce:

  1. create a community
  2. change its name
  3. load own user profile

expected results:

  • community's new name is displayed both in the "Moderates" and "Subscribed" boxes

actual results:

  • new community name is displayed in the "Moderates" box
  • community's old name is still displayed in the "Subscribed" box

additional notes:

  • the renamed community's new name becomes visible after subscribing to some other community
  • sorry for posting this here, but, i don't want to give microsoft my telephone/ID/firstborn/etc which is required to open an issue on github these days
you are viewing a single comment's thread
view the rest of the comments
[–] ticoombs@reddthat.com 2 points 1 week ago

This might be another bug relating to federation, but might also be relating to caching on their end. Or because every Lemmy application keeps their own archive, it's possible the user display name doesn't federate on a change but only on a post that they can see? (Or not at all, or only on a timed refresh?)

Lets check after 24/48 hours on those links and we'll see what they say after that.