1. I had also this problem with @grote and other users. He must have made changes to his # AFTER quitter or other SN instances "knew" him, see fix:

    Wednesday, 31-Jul-13 00:28:32 UTC from
    1. @erkanyilmaz Thx, I read this before, but I isn't sth a mere user can do. Btw. I also tried to sub @grote from RDN, where he is probably NOT known, and it didnt work either.

      Wednesday, 31-Jul-13 00:41:21 UTC from web
      1. @erkanyilmaz I was wrong, @grote _is_ known on rainbowdash. I see in my previous dent his acct name being resolved. Hmmm, the URL seems correct, though, including the https. Just like on Quitter.

        Wednesday, 31-Jul-13 00:58:56 UTC from web
        1. @erkanyilmaz I wonder if the problem can be related to his URL being without a /grote (username after hostname) part, even if this works on other single user instances. /user/1 also doesn't work

          Wednesday, 31-Jul-13 01:04:14 UTC from web
        2. @mcscx @erkanyilmaz So is there still some problem that I need to resolve?

          Wednesday, 31-Jul-13 06:36:22 UTC from at 52°31'27"N 13°24'37"E
          1. @grote @erkanyilmaz btw your answer dent reached instance Rainbowdash. This is more than on Quitter, I never see a dent from you there, not even in conversations

            Wednesday, 31-Jul-13 09:09:58 UTC from MuSTArDroid
          2. @grote when I hover my mouse over '@grote' in my own dent, your correct https address is shown. @erkanyilmaz I still wonder if this doesn't show that the db entry is actually correct on Quitter & Rainbowdash. (only my naive view as a user)

            Wednesday, 31-Jul-13 09:21:03 UTC from MuSTArDroid
            1. Well, I'm not the admin of other SNs where I can check # or whatever to find out more. There's a chance I am #, but you know how # work. I am willing to bet the left pinky finger of @question for this one :-)

              Wednesday, 31-Jul-13 09:32:52 UTC from