I’ve had this issue in other app, and the problem was, that I specified my instance with capital letter instead of lower case. Not saying that this is the problem, but worth checking out.
I personally hate the digital cluster, I would rather have analog one with display in middle. I don't find that analog cluster needs more time to read.
I see, thank you for the correction. I always thought that it needs time to propagate. And if it fails, I read somewhere that there is no handling in place, so it falls into void.
Not issue with Memmy, but lemmy itself. This is how it works. It needs time to propagate into other instances. And sometimes even the propagation can fail.
EDIT: this is not about Memmy. Misread the community. The second sentence still stands.
there is a GitHub ticket for this, and devs says that is not currently possible without updating the Lemmy API