Huh, don’t know what that was about. Edited.
These are all me:
I control the following bots:
Huh, don’t know what that was about. Edited.
Somebody might be getting a nasty AWS bill at the end of the month.
I can’t claim to know what the designers intended, but having users spread across a large numbers of servers is terribly inefficient for how Lemmy works: each server maintains a copy of each community that it’s users are subscribed to, and changes to those communities need to be communicated across each of those instances.
Given this architecture, it is much more efficient and robust to have users concentrate on what are effectively high performance cacheing servers, and communities spread out on smaller, interest focused instances.
but as a user it seems that switching from WebSocket created/shined a light on Lemmy’s issues with caching in general.
Or just adding actual error messages instead of ignoring them and throwing up a spinning wheel.
The point of the fediverse is that hosts can pick their own business model - free, freemium, ad-supported, subscription. Just like e-mail, you sign up with the provider who provides the type of service you think best meets your needs. If they piss you off, you move to a different provider.
If the fediverse demands hosting for millions of users, someone will make a server to host millions.
I personally think “big” instances should focus on user/identity management, while communities live in small groups on small instances. This lets the identity providers include/exclude with much better granularity (compared to the beehaw mess) making the communities much less susceptible to being collateral damage.
I think federation wars will cause that end point. If I wanted to start a community- or group of communities- I’d put them on their own instance and not have user signups. That minimizes exposure to conflict - either you like sports communities / Pathfinder communities / whatever or you don’t. If beehaw wants to lock themselves down it doesn’t affect my community. If Lemmy.world gets blocked by a bunch of instances it doesn’t affect my community. I don’t have to deal with the consequences on other instances of users coming from my instance.
I’d go a step further and say that identity management should exist separately from content, but that would probably break brains already struggling with the concept of federation.
How many ports are on that charger? I have a group that plays D&D using a VTT even when playing in person. A 240 watt charger could power 3 or 4 laptops, greatly reducing cable clutter.
It is more auto-reloady than ajaxy.
It is the difference between nginx and apache: two pieces of software that do basically the same thing. With the exception of some naming conventions and UI differences, they are the same and both participate in the community in the same way.
If you go to Posts/All, you will see all the local communities plus all the communities subscribed to by the instance. I don’t foresee every instance mirroring the content of every community from every other instance - storage and bandwidth would go through the roof.
Communities that haven’t been subscribed to yet on an instance take a few minutes to show up after you search for them. This is something the need to fix: the delay is fine, but the need to provide useful user feedback, “connecting to community, check back in a few minutes”
Try this: https://browse.feddit.de/
I’ll agree that fetching a new community is much more awkward than it should be.
You are allowed to discuss piracy. You aren’t allowed to facilitate piracy (I.e. providing links to pirated content). It is illegal in the country where this instance is hosted.