I mean. I'm not talking about the actual cost of making the device but rather the total cost. Ie the cost to their bottom line.

The cheapest would probably be to make a single device with a replaceable battery, and weld the battery in place outside of Europe, but that would probably be so blatant that they would get in trouble.

It probably boils down to what costs the most, making a universal model for everywhere, or making a European model and a separate "screw you" model for the rest of the world.

Cool shot

That would be up to the admin of each individual instance owner how to handle that on their instance.

Combine that with the fact that most experienced admins can work a lot faster in a CLI compared to GUI, and the fact that a CLI allows you to replicate previous actions with no effort.

The post lagging seems to be front end only. So far I've had no issue simply refreshing the page when it hangs.

Good to know. I'm always and forever missing small stuff like this.

The upvote jumping is caused by issues with the websocket implementation. As far as I heard they are going to get rid of websockets completely in the next version and have static page rendering instead.

Same thing happened to me earlier today. It popped up about 10 times while I was writing a comment.

It's a lowercase l followed by a lowercase w as far as I can tell.

Getting rid of websockets would help a lot. But you still might not be able to have standalone nodes. You might still need a cluster of nodes with a master and slaves due to the federated nature of lemmy. Such that only one node at a time can handles federation events with other servers. I don't know enough about the protocol to know if that is the case or not. Just as an example I'm thinking of situations where one node gets a federation event for example for a post, then a different node gets a federation event with some sort of change to that post, and handles it faster than the first node. That event would then fail because the post hasn't been created yet.

Yeah. I'm in the same boat. My SQL skills aren't impressive either since there are other people at work that handle optimization. Haven't used rust either (yet) so cannot really contribute there either. Though I'm considering potentially starting work on a cross platform mobile app. I haven't worked with mobile apps for a good six or seven years, so I feel like it's high time I get back up to speed. (But knowing me, I'll end up making something half finished and the start procrastinating)

Yeah. But horizontal scaling (well horizontal scaling in a system like this where you need clustering so the instances talk to each other) is hard. And I think there are a lot of other things that need to be polished, added and worked on before that. It would probably also need somebody with knowledge of clustering to start contributing. I think step 1 needs to be that the dev team needs more help properly tuning the database use. The database is very inefficient, and they lack the skill to improve it:

We are in desperate need of SQL experts, as my SQL skills are very mediocre. ^{https://github.com/LemmyNet/lemmy/issues/2877}

So getting help improving the database is probably the #1 thing that can be done to deal with the scaling problem.

Thing is, lemmy doesn't support clustering/horizontal scaling. So there are limits to how much increasing you can do. You can beef up with a database cluster, add a separate reverse proxy, and increase the specs of the hardware lemmy is running on (but hardware can't be expanded limitless), but that's about it. Once you hit the limit of what a single instance of the lemmy software can handle, you cannot scale anymore. Pretty sure you will hit the limit long before you reach thousands of dollars.

I mean it's the same on reddit, just that they have to have slightly different names.

I'm pretty sure that duplicates will sort them selves out organically over time.

I disagree with your statement that centralization is almost a law of the universe. Anything big online these days is decentralized, it's just done transparent through CDNs, so you as a user don't notice as opposed to the fediverse where it is visible to the general public.

To add to that. It would not surprise me if that is the most efficient way of doing things. Let the client handle all of the filtering. Sure it increases traffic, but it reduces server CPU load greatly.

Not only do we not need to attract everyone, we cannot attract everyone. At least not short to mid term. If everybody on reddit suddenly jumped on the lemmy bandwagon, the whole network would go down faster than you could blink.

From my understanding you are correct. Each instance is responsible for serving all of the content of the communities created on it. So many small instances with a smaller amount of communities = good, a few huge instances with lots of communities = bad.

I'm not sure your second paragraph is correct. First of all, it's "just in time" so will only be replicated if somebody on that instance is following it. But more importantly, I read a statement from a server owner somewhere that the software purges older content regularly (and refetches is "just in time" when somebody tries to view the old content) to keep storage size down.