Is this the reason why my single-user instance can't subscribe to any https://kbin.social magazine? I'm not even getting an error, just "Subscription Pending". That sounds kind of broken and different to how Mastodon is dealing with that issue.

Do I somewhere need to apply to be able to subscribe to any /kbin magazines? If so where do I do that? Is there a email I can sent my application to? Or is the idea that if you have a single user instance you create a new user on every instance to find some meta-magazine where you can ask to be able to subscribe to a magazine on that instance?

Or are small instances not part of the design?

Here is mine https://gist.github.com/jeena/6179470a8d616455f30635a5c71f5f64 which had a similar problem with the comments, although I couldn't post comments on my own instance either.

For me the thing was that I had to add:

map $http_upgrade $connection_upgrade {
    default upgrade;
    ''      close;
}

and

        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection $connection_upgrade;

And also change the nginx in the docker to port 8080 so my normal nginx could keep running on 80 and handle all the ssl certificate stuff.

My setup is:

Browser -> native Nginx -> docker Nginx -> lemmy

I saw that github issue back then and I also saw somewhere that the cloudflare has been removed and that lammy could federate now. But in practice it doesn't work for some reason.

That is why I've been thinking that they might have a white list and I'm not on it but the bigger instances are. But there is no way for me to see that.

Oh I was just listening to a podcast where you were a guest in https://pod.fossified.com/2023/04/05/s01e03.html and I had to lough out loud when they asked you what they could do to bring more women into FOSS or what it was and your response was to not invite them to podcasts only to discuss the topic of women in FOSS :D