Yes because we’re in a server default subscription. A server decided list of viable communities, probably a list shared across the fediverse. Again a gayekeeping system by the system elites
We are in the !fediverse! community, only big one that exists.
It’s double centralization. This is recreating Reddit.
Lemmy has nothing to do with email. I’m sick and tired of this incorrect analogy being used to explain how Lemmy works and people stubbornly not understanding why it’s broken because of it.
If you think it through, what you’re asking is that the communities will exist only on one server. That’s Reddit with extra steps.
If people have to hunt each post storage location individually, then it will be as if they don’t exist to 99.99% users. What will happen is there will be one big one, and they most likely be all on the big instance, and federation becomes just a weird thing that does nothing because functionally that will be just like Reddit. Centralized servers, centralized servers under the control of a tiny priesthood.
Propagation and agglomeration is a problem for clients not servers. Server only need to propagate a “we have new stuff” message and it’s up to the clients to pull it and cache it. In any case, users should be able to click /c/books and see the content of all /book/ on all instances in a single location. Unless most users can do this with one click, there will not exist a fediverse wide community.
“multireddit” are nice to have but they do not address this problem Which a common view for all user of an entire community across the fediverse. “Multireddit” require client to pick and choose individual communities. This means less than 1% of users will every use it. This means there will never exist a fediverse wide community around topics.
There are many fatal problems on Lemmy, worst of all is you can’t click this link /c/books and see every /c/book on every Lemmy instance of the fediverse. This is out of convenience to moderators and it is killing Lemmy. One people figure out communities only exist on a single instance, the promise of federation is broken and they fuck off.
411, ygg, bunch of others that made me jump hoops to join and then had those shitty policies. I stopped using private trackers a long time ago.
I equate private tracker with shit tracker and not worth my time nor my seedbox bandwidth.
DHT should have made trackers obsolete. We should have torrents of torrent files.
They say they provide curation of content, keep out lawyers and provide an incentive to seed.
In practice none of these are provided.
What they really are, are entities who sell access to copyright infringement material.
They discourage network effect free sharing. They discourage posting content with investors rules and they impede seeding by creating a zero sum economy where nobody wants to download anything unless they really have to because you won’t be able too seed your ratio back to 1 as everybody tries to seed and nobody disappears.
It leads to the ridiculous practice of downloading whatever gets posted on the RSS feed, just so you can seed it to other people who blind download stuff just to seed it. Basically a pump and dump scheme where someone always end up holding the bag.
All this to motivate people to buy their ratio back. I’ve seen one recent case they were charging 20$ to free leech 80gb.
In other words private trackers are shit, kill private trackers with DHT
It’s nothing. You don’t recompute everything for each page refresh. Your sucks well the data, compute reputation total over time and discard old raw data when your local cache is full.
Historical daily data gets packaged, compressed, and cross signed by multiple high reputation entities.
When there are doubts about a user’s history, your client drills down those historical packages and reconstitute their history to recalculate their reputation
Whenever a client does that work, they publish the result and sign it with their private keys and that becomes a web of trust data point for the entire network.
Only clients and the network matter, servers are just untrustworthy temporary caches.
Moderation should always be client side. Server side should not be able to interfere or even read public content