Right now the top bar only shows local magazines, as does the "Random Magazines" section.
Why is that and should federated Magazines be listed too?

For context: I am running a (right now) very small instance that has basically no local magazines. Therefore my topbar is nearly empty

I thought that my instance is having problems with sending posts to other instances, especially lemmy instances, so I tried something and these are my observations:

When I post an article to @kbinMeta not all servers that subscribed to the magazine get that article (seemingly). It of course appears at https://kbin.social, but not necessarily on other servers. This is not necessarily by design, it might be, that kbin.social is just struggling to keep up, but I've waited for about an hour and it did not show up on other servers and there are other posts from kbin.social users in kbinMeta at htts://lemmy.ml that got posted after I posted my article, but mine isn't there.
However when I mention a user from another server in a comment this server instantly gets the comment that mentions the user from said instance including the article, which was previously not present on the server.

So here is my Theory:

• I post something to @kbinMeta -> kbin.social gets the post (-> kbin.social broadcasts it to servers that subscribed to the magazine)
• I post something to @kbinMeta and mention a specific user from https://feddit.de
  • -> kbin.social gets the post (-> kbin.social broadcasts it to servers that subscribed to the magazine)
  • -> feddit.de gets the post directly

The part thats in paranthesis I am not sure about. Maybe it gets done and maybe not. If it is done then the queue on kbin.social for outgoing messages is just huge and a message is waiting for over an hour to get processed

Maybe some of you know more than me. I just that and this is my observation.

I set up an instance and got the feeling that outgoing federation is not really working. So this is testing that.

I just disovered that I (local admin) can edit the description, tags, etc. of a remote magazine (propably because I am marked as the owner on my instance)

For 1h my instance is hammered at 100% CPU. I just upscaled, but that didn't change anything. I now have a hetzner server with 4 cores and 4 processes for each of the messenger commands. I figured they just have to process a long queue so that makes sense, but only if the queue has an end...
The only thing I found to debug what the messengers are doing is this: php bin/console messenger:stats
which yields the same result each time I run it:

----------- -------
 Transport   Count
----------- -------
 async       100
 async_ap    100
 failed      2152
----------- -------

! [NOTE] Unable to get message count for the following transports: "sync".

Is there a better way to debug kbin messengers?