I’m not sure that there is much for actual server side support for cross posting just yet, but there is a way, at least on the web UI: if you click the two overlapping squares under you post title, it’ll open a new post with a link to the previous post and its content quoted underneath. It feels more like a work around for cross posting, but it does work.

I was referring to Rule 3 of the community:

3. Not regarding using or support for Lemmy

TL;DR: There is no singular answer to your question, imo. Essentially just run the instance transparently, reliably, and actively, and it will be attractive to people.

I’m not sure that there is one “best way” to grow an instance. An instance is essentially the fundamental governing framework for how the users interract with each other. You structure the rules around how you believe the users on your instance should interact, and those who agree with those rules will be drawn to them. Ideally, for sustainable growth in an instance, you also need reliable server infrastructure – the instance should be responsive, and have a reliable uptime. An instance’s admins must also actively moderate content. An instance with inactive moderators is not sustainable, and will quickly delve into hosting unwanted content on the instance which is undesirable for users.

This post possibly violates Rule 3 of !asklemmy@lemmy.ml.

Y’all don’t update your services?

Homeserver admins (…) can see who (…) you’ve talked to and when it happened.

I’m assuming that since it is federeated, even if one server was very diligent with not keeping such metatadata, the issue would still remain with the other server if it did not follow the same practices?

It would put the more popular instances under enormous stress, if they had to serve every single subscriber from any other instance.

From what I understand, media (images, videos, etc.) is not cached. Does that not mean that, in the worst case where every post contained an image, the instance would be serving every subscriber, anyways?

I don’t really understand this reasoning. Some server would still need to receive those requests at some point. Would it not be better if those requests were distributed, rather than pounded onto one server? If you have a server caching all the content for its users, then all of its users are sending all of those requests for content to that one single server. If users fetched content from their source servers, then the load would be distributed. The only real difference that I can think of is that the speed of post retreival. Even then, though, that could be flawed, as perhaps the source server is faster than one’s host server.

Please correct me if I am wrong, but this feels like a flaw with how Lemmy (perhaps other fediverse apps as well, I’m not sure) is designed. Why do I need to store all posts made to a community that one of the users on my instance subscribes to? Would it not be better to simply store my user’s posts, and comments, and the posts made to any communities hosted on my instance? Why do I need to store information from other instances, and users?

it is storage that requires more attention

Please correct me if I am wrong, but this feels like a flaw with how Lemmy (perhaps other fediverse apps as well, I’m not sure) is designed. Why do I need to store all posts made to a community that one of the users on my instance subscribes to? Would it not be better to simply store my user’s posts, and comments, and the posts made to any communities hosted on my instance? Why do I need to store information from other instances, and users?