Just found a case (or I don't understand federation properly). https://lemmy.world/post/2966430 (title: Atlas Fallen - Review Thread)is on !games@lemmy.world On top of the post is a cross-link post with a URL from lemm.ee Clicking on that shows that same post in !Games@sh.itjust.works However, if you click on the community title, it will load !rns@lemmy.pineapplemachine.com No clue why that is happening. Following the same pad on the web UI leads to the correct communities
daniyyel
joined 1 year ago
You might have Cloudflare add a request header to the origin request, like x-cloudflare-key: <somesecret>, and then configure nginx on the server to block everything not containing that header.
For now yes, but over time probably no. Multiple communities around the same subject are created on different instances. They'll compete to become the most active one. Then everyone will subscribe to that one, and it will grow even more. However, if over time you don't like that one any more (e.g. don't agree with the mods) you can start a community with the same name somewhere else and compete again to become the most active one (or not, and stay small if that is preferred).
Moyee can also be bought at Albert Heijn. Is that the same roast/quality? I quite like the single origin.
No, it's fixed now in the last beta. Thanks!