Lemmy Support

4950 readers

8 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 6 years ago

MODERATORS

dessalines@lemmy.ml

bug: missing cache invalidation when renaming community (reddthat.com)

submitted 2 weeks ago by al_gore_rhythm@reddthat.com to c/lemmy_support@lemmy.ml

8 comments fedilink hide all child comments

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

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

[–] al_gore_rhythm@reddthat.com 1 points 2 weeks ago (6 children)

oh, i assumed this is a function of the software, but you think it is a configuration issue on this instance?

ping @ticoombs@reddthat.com

[–] ticoombs@reddthat.com 2 points 2 weeks ago (5 children)

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.

[–] al_gore_rhythm@reddthat.com 1 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

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+

[–] ticoombs@reddthat.com 2 points 2 weeks 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.

load more comments (1 replies)

load more comments (3 replies)