1 guy made a community. He put some shitty posts there that were massively downvoted. He was banned and his community deleted. It's hardly "The_Donald" joining.
That's actually not how it works. Images are hosted by the instance the community is on. Other instances embed those images as links in the page. The image is downloaded from the original instance by the browser.
That's an open issue on Github. The devs are currently in the middle of trying to optimize performance so the whole network doesn't go down on the 12th. If you know any webdevs willing to have at it, great!
You should be able to federate with all available communities by default.
The trick is that your instance will not pull in all communities by default. Once 1 person subscribes to a community (a bit tricky for the first time, see here), all users on your instance will start seeing that community in their "All" feeds.
I don't think there's an easy straight-forward answer to that. This is one of those things that's gonna have to be the result of a process of trial, error and waiting for new solutions and development.
One thing that might happen is something like Foundry's server hosting ecosystem, where you have companies that specialize in hosting just Foundry as easily and simply as possible (I.E: moltenhosting). If that happens, then anybody setting up a new server is just a small payment away.
Can definitely be done. Just need someone to do it. I need to read more of the documentation and figure out how all this works before contributing, I don't want to waste the dev's time coaching a newbie. That's the last thing they need right now.
Yes, it's a known issue. The devs are absolutely slammed with optimization issues, and this will probably get addressed at some point.
Definitely yes on lemmy in general, definitely no to lemmy.ml. Pick a server you like the rules & admin for, maybe ask the admin directly, and direct everyone to that server. That way you can also host the PF2E community on that server.
Things are already getting way too centralized on lemmy.ml, we need to spread out a bit
@Barbarian
@lemmy.ml