Big instances surfing up content from smaller instances is invariably going to cripple them unless larger instances start locally caching that content.
Formerly /u/neoKushan on reddit
Big instances surfing up content from smaller instances is invariably going to cripple them unless larger instances start locally caching that content.
Ultimately, you need some way of routing the traffic to the correct place. Having all 3 services on the same domain, listening on the same ports is going to be a nightmare to manage because something needs to be clever enough to route the traffic to the right service without any information to go off of, other than maybe headers. Expensive firewalls can technically do this but it’s not fun to configure and is really brittle.
As inferred, you could use the same domain but you’d have to configure your services to listen on a different port so you’ll end up with something like https://domain.tld:8443 for Mastodon and https://domain.tld:8444 for lemmy.
You can technically use subfolders, i.e. domain.tld/mastodon
and domain.tld/lemmy
but you’re not going to get the results you want and I can’t say for sure that the software will deal with it nicely.
This is why we tend to use reverse proxies and configure them to route all traffic from subdomaina.domain.tld to one service and subdomainb.domain.tld to another service. It’s just easier.
And he’s another example of the classic Reddit moment. Prior to him they had a CEO everyone hated and Steve came in after she left, except it later transpired that she wasn’t the cause of the issues the community revolted about.
Is that because of some kind of event sourcing, though? That’s not an uncommon way of handling these things.
Good to know! I expected that an influx of users would propel development, hopefully that momentum keeps up.
Yup, also browse “All” communities (not local/Subscribed) by “Hot” for an equivelance to the Reddit homepage and to discover other communities.
As one of those new users, I’m loving the potential of Lemmy and I’m enjoying finding my way around, but it definitely needs some UX enhancements, especially around federated communities.
I’m seeing the same thing, also in Firefox but I suspect it’ll happen on any browser. I’m with you, I think it’s because it keeps loading in new posts but doesn’t unload the old ones. It’s probably an easy fix