![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/0943eca5-c4c2-4d65-acc2-7e220598f99e.png)
LoL! That is an unusual guess, I don’t think I have heard of “Marxist Leninists” in popular media in a while!
LoL! That is an unusual guess, I don’t think I have heard of “Marxist Leninists” in popular media in a while!
I think the original analogy works better.
If an EU country goes rogue, other EU nations can’t just isolate it and bar it’s citizens from entry. There is no expulsion from the EU AFAIK. But Lemmy instances can block another instance fairly easily and unilaterally - like how nations can refuse visa to citizens of a rogue nation. And Lemmy instanced are expected to federate with most other instances, just like countries are expected to grant visas to most other countries - unlike joining the EU, which is a whole big process and all EU members have to agree (there are no vetoes in Lemmy federation).
But most importantly, the EU members are required to act as one in many circumstances - most laws apply across all EU members, EU negotiates trade deals as a block, etc. That is not true for Lemmy instances. Each is completely independent and makes its own laws - and must only comply with some very loose principles (which boil down to “don’t be a total jerk”) to not be isolated from other instances. This is much closer to the kind of independence countries have, than EU members.
I think it’s not helped by the fact that most early adopters are “techies” who enjoy talking about the underlying tech.
The average user doesn’t really need to understand this whole fediverse thing to sign up and use Lemmy. We could just have a website with a big sign up button that randomly (to load balance) selects an instance from a whitelist and signs the user up there to get them started. But instead we have GitHub docs with detailed comparisons of various instances, and long discussions about underlying protocols and what the federation means and how that’s different from centralized platforms.
I have worked on non-trivial (aka took 10-12 people over a year to even deliver an alpha) greenfield projects, where I literally made the first check-in into the repo.
The only 500+ line PRs I raised was auto generated boilerplate code, or renaming something.
I don’t understand the optimism of devs who spend weeks writing code without bothering to test anything they’ve written. Unless you’re writing utterly trivial BS, how does one have this level of confidence in their code? And if you did bother to stop and test, why on god’s green earth would you not raise a PR? Why wait till you have thousands of lines of code before asking for feedback?
I don’t have experience with a sarong, but a saree is basically the same thing.
The difference is in the shape and size of the piece of cloth. That’s how you can tell a saree, bedsheet and towel apart. There is also usually difference in material (but fine silk towels exist, as do coarse cotton sarees), patterns/weaves (but there are towels and sarees that share pretty similar patterns) and quality of materials used (but again, ridiculously high quality silk bedsheets are a thing). The real difference is the shape and size - sarees are always 5.5m x 1.15 m (‘standard’ 6-yards), or 8.2m x 1.15m (9-yards, worn only on special occasions now, and only in a few specific regions).
In a pinch, a saree works as a towel or a bed sheet or a cover sheet of any sort, really. However, good luck getting a towel or bedsheet draped onto your body - you’ll look like you’re in a sack. They just don’t have the right shape!