@eldersnake (#mziu3ca) Looks like the internal mapping of `nick -> url` for the `.Followers` of the `User` model is flip-flopping. That data structure needs to change, which is part of the refactor work I have for the Follow/Following subsections of the code. But hmmm I _might_ have to just disable this section of code for now? 🤔

@prologic (#mziu3ca) Okie dokie. Was worried I had sent it for a spin by using the same username (_again_), but then I can't be the only one that's done that before.

@eldersnake (#mziu3ca) No you're not the only one; but this code will have to change now, as the model can't cope with this 😂 For the time being I'm just going to mute the @twtxt bot on my own pod until I fix the code, it's getting late 😴

@eldersnake (#mziu3ca) In the meantime I figured out a quick/hacky way to fix this(_for the time being_): ``` "Followers": { "test": "https://7a987bae6af1.ngrok.io/twtxt.txt", "test_1": "https://7a987bae6af2.ngrok.io/twtxt.txt", "test_3": "https://7a987bae6af3.ngrok.io/twtxt.txt" }, ``` Basically the code tries to find a unique key for the "nick" to insert into the ".Following" map. Up to 99 before it gives up. It's a hack but it'll work and I just tested this on a test pod. What do ya think? Shall I roll this out?

@eldersnake (#mziu3ca) It _however_ does have the unfortunate side-effect of this: As one would expect.

@eldersnake (#mziu3ca) PR for this change =>

@prologic (#mziu3ca) I mean if it works... Although its interesting in my case it's with two different domains 🤔 that never happened with the twtxt.net _eldersnake_ and my personal pod. Just woke up so hopefully I make sense 😁

@eldersnake (#mziu3ca) I can’t explain that 😁 But if you’re happy enough with this change I’ll merge it now and push it to my pod 👌 See if it mitigates then issue 😂

@prologic (#mziu3ca) awesome, well it can't hurt for now. Besides the twtxt bot is spamming both our pods 🤣

@eldersnake (#mziu3ca) Rolling it out to my pod before merging…