al_gore_rhythm

joined 1 week ago
sorted by: new top controversial old
bug: missing cache invalidation when renaming community in c/lemmy_support@lemmy.ml
[–] al_gore_rhythm@reddthat.com 1 points 1 week ago* (last edited 1 week 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+

bug: missing cache invalidation when renaming community in c/lemmy_support@lemmy.ml
bug: missing cache invalidation when renaming community in c/lemmy_support@lemmy.ml
[–] al_gore_rhythm@reddthat.com 1 points 1 week 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

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

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
11
Information superhighway (en.wikipedia.org)
*Permanently Deleted* in c/nostupidquestions@lemmy.world