steps to reproduce:
- create a community
- change its name
- 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
I too think it’s possibly a software bug rather than a cache issue. We don’t cache anything if you are signed in, and if it was a cache issue it would show both of the old names on the page rather than only one changing.
while i’ve got you here… i noticed another related issue: i changed my display name and bio a while ago, and the change has not propagated to other instances. compare:
(currently all remote instances show my old name…)
edit: … and another issue: the link parsing of those URLs is overzealous, hijacking the parts that match (i’m guessing, approximately) the regex
u/\w+@\w+\.\w+User profiles are only updated every 24 hours so that is normal. The url parsing is handled in lemmy-ui, you can check the issue tracker or open a pull request.
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.