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.

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.

There is an open ticket or multigroups: https://github.com/LemmyNet/lemmy/issues/818, so you might want to give that a thumbs up to show interest.

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.

I agree. I too prefer the website as a progressive web app. Though I'm playing with the idea of making a cross platform app highly inspired by relay for reddit. But with my history of procrastination that probably never will get finished.

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.

Got my first phone in 1997, and I have yet to experience a charger needing to be replaced.

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'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.

I mean. Even when I take off my tinfoil hat, kbin is very immature software made by a single guy, so it wouldn't surprise me at all if he spent a lot of time polishing pulling content in, and very little time on pushing out.

Had almost the same journey, except I've never heard of fark before.

Tvilsomt. Fediverset er fortsatt for komplisert for hvermannsen. Om man klarer å lage en mer smidig og forståelig måte å abbonere på tvers av instanser, samt å søke opp innhold og grupper på tvers av instanser vil jeg tro at det er langt mer sannsynlig at fediverset blir "mainstream".

Må si jeg er glad for at jeg valgte lemmy.world. (dog opprettet også en konto på lemmy.ml men har ikke brukt den). Vil heller leve med litt trolling og slikt enn å være i et ekkokammer/"safe space". Viktig å får utfordret mine syn på ting og tang i ny og ned.

There is an open ticket or multigroups: https://github.com/LemmyNet/lemmy/issues/818, so you might want to give that a thumbs up to show interest.

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.

It seems to be kind of hit and miss. I tried getting [email protected] into lemmy yesterday. It kind of worked on lemmy.ml but only showed older posts. On lemmy.world it didn't work at all, and still doesn't.

A very big forum I that I was on the moderator team of about fifteen or so years ago had a rather neat solution. You could freely upvote, but you could only downvote 5 comments every 24 hours. It actually worked rather well.

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

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.

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.