It’s dumb that someone needs to interact with community in order for it to federate with your instance. Like, how are you supposed to find it in the first place? It makes it difficult for communities to grow on instances that are not mainstream which makes decentralization useless.
I just did some math and assumed there are 700 (some instances are blocking other instances) instances and 12 000 communities. 700*12 000 = 8 400 000, users across the platform need to copy url of community and paste it into search this many times to make the platform fully federate with everything. Numbers were taken from here: https://lemmyverse.net/
this number is only completely relevant for someone on an instance all by themselves or with no communities at all. And discounts instances that are or will de-federate either partially or fully. It also assumes some need to be a part of all 12,000 communities. I think tools like you linked solve this issue anyway. I personally believe to a certain extent every community being federated to every instance kind of defeats the purpose of federalization.
But that’s not my point though? The point is to federate with all sublemmies of FEDERATED instances. The problem is that when you federate other instance it doesn’t federate sublemmies of that instance automatically which limits interactions between instances by a HUGE amount
It’s a risk reward question then. That would 100% slowdown the initial federation if it needed to pull in every community and even if that was accepted, should every instance constantly poll any instance it knows about for new communities? Also you aren’t guaranteed to need all those instances anyway and then that’s just a waste of space and processing power. Correct, it limits interactions but only to what’s necessary which allows instances to be ran on lower powered hardware, allowing more people to join in. With the possibility of third party tools I don’t see much of an upside of building that into lemmy.
Sorry! My bad, numbers are incorrrect but I’m not sure how to calculate correct numbers lol. Wouldn’t it be 700x699 or 699x699 because instance wouldn’t have to federate with itself?
a continue inside an if statement checking if the bot domain is the same as the subscribing one would suffice
edit: or use a search algorithm to pop the domain from the stack before starting the loop, that would be more efficient
edit2: even better: assuming all bot names are the same, you just iterate over the stack (constant), and pop each domain (new stack minus popped domain) and feed it to the 2nd loop.
edit3: SCRATCH EVERYTHING. The bot names don’t even have to be the same, you just iterate over a constant stack of botname@domain entries and pop the iteration from it… feed the new stack to the second loop (nested) and done. Why did I take so long to reach this?
In order to avoid this restriction you would need a global instance discovery mechanism, which is extremely hard to implement without a central server that keeps a list of all instances in the network. And if you do implement instance discovery through a central server you really are losing the whole point of decentralization.
Additionally, it’s good that each instance does not federate with everyone else by default. If it did, it would have to process all activity and keep a local copy of all the content in the entire network. This would be insanely inefficient, and make it prohibitively expensive to run even a tiny instance with 1 user and no communities.
Decentralization isn’t useless if you can’t immediately see everything in the network, come on… We’re just spoiled by centralized services.
you would need a global instance discovery mechanism
I don’t think you do. Instances should merely reach out to other instances it’s federated with periodically to get a list of communities and some of their metadata. Ideally, they could ask all of those other instances to notify it when a community is added, modified, or deleted, and then store that metadata.
That should be pretty easy to implement, and maybe it already has, idk.
Sure, but this isn’t finding new instances, just new communities on known instances. Indeed, this is not difficult to implement. The reason it’s not done already is for resource economy. A lot of instances are already struggling to scale, making them process and store a lot more content with little value for most users of the instance isn’t feasible for a lot of servers right now.
A list of communities isn’t “a lot more content.” Just run it once daily and the problem is solved. Instances don’t need to store posts, just community names available on that instance.
If the issue is finding new instances, I think it’s fine for it to take some time the first time someone tries to find a community on that instance. But after that, it should immediately have a list of communities from that instance.
Ummmm… All you need is some bots on each instance that automatically will interact once with communities known on lemmyverse.net and boom, you have unlocked full federation for every user on those instances. You are not losing any privacy through that, it just skips the steps where user has to manually index a sublemmy before it federates and makes platform more usable.
Sure, but now this system has a dependency on the “centralized” lemmyverse.net service. And also your instance now has to receive and store a copy of almost the entire network’s content. Lots of instances are already struggling to sustain the load, this would make the problem even worse.
If a single instance decides that it can sustain the increased load and doesn’t mind depending on lemmyverse.net sure, nothing’s stopping them. But it shouldn’t be the default behavior for all instances.
Yet bittorrent dht is 20 years old. How can this supposedly decentralized service be unable to self organize. Is Lemmy some kitchen napkin high school fair project ?
Social media and torrents are pretty damn different. There’s a reason no federated platform has implemented automatic discovery, even ones with much more resources than Lemmy, like Mastodon.
I don’t know why you folks keep pointing at missing features and saying “Lemmy doesn’t have this pretty advanced network feature, so it’s not really decentralized”, or “it cannot organize”, or “it’s useless”… It’s basically two people’s passion project that only blew up in the past month because reddit fucked up. You’re not paying for it, are you? So I really don’t see how this attitude is warranted.
The tech is right there, it’s 20 years old. I’m pointing at it in response to people saying “this is too hard, we can’t have 700 instances sharing a few kilobytes of text !, You’re asking too much”
How is that not part of base code. Lemmy is completely unusable until this is fixed. The clock is ticking on Reddit’s implosion. If this isn’t fixed, the Reddit userbase will go back to Reddit for another 20 years.
Please don’t let Lemmy as useless as Mastodon, this is clearly design sabotage by silicon Valley big tech.
Calm down bro. Your negative energy is harshing the vibe here. Let’s try that again
I see, thanks for the info. The devs should prioritize adding a feature like that into the base code. It would really help reddit migrants get set up here.
See? I liked a couple of your comments in the other thread about downvotes being public information, but you’re sounding pretty defeatist and frankly, miserable in the past few hours. If you don’t want the reddit userbase to go back, the best thing you can do is be a user that other users enjoy interacting with.
Unless you wanna step in and start coding this thing 🤣
It’s dumb that someone needs to interact with community in order for it to federate with your instance. Like, how are you supposed to find it in the first place? It makes it difficult for communities to grow on instances that are not mainstream which makes decentralization useless.
I just did some math and assumed there are 700 (some instances are blocking other instances) instances and 12 000 communities. 700*12 000 = 8 400 000, users across the platform need to copy url of community and paste it into search this many times to make the platform fully federate with everything. Numbers were taken from here: https://lemmyverse.net/
this number is only completely relevant for someone on an instance all by themselves or with no communities at all. And discounts instances that are or will de-federate either partially or fully. It also assumes some need to be a part of all 12,000 communities. I think tools like you linked solve this issue anyway. I personally believe to a certain extent every community being federated to every instance kind of defeats the purpose of federalization.
But that’s not my point though? The point is to federate with all sublemmies of FEDERATED instances. The problem is that when you federate other instance it doesn’t federate sublemmies of that instance automatically which limits interactions between instances by a HUGE amount
It’s a risk reward question then. That would 100% slowdown the initial federation if it needed to pull in every community and even if that was accepted, should every instance constantly poll any instance it knows about for new communities? Also you aren’t guaranteed to need all those instances anyway and then that’s just a waste of space and processing power. Correct, it limits interactions but only to what’s necessary which allows instances to be ran on lower powered hardware, allowing more people to join in. With the possibility of third party tools I don’t see much of an upside of building that into lemmy.
wait, so if you federate with another instance through one community, you won’t get to see the rest of the feeds from that instance?
would subscribing to the domain directly (like kbin allows, maybe lemmy could in the future) reduce the number of actions to 700^2?
Sorry! My bad, numbers are incorrrect but I’m not sure how to calculate correct numbers lol. Wouldn’t it be 700x699 or 699x699 because instance wouldn’t have to federate with itself?
oh yeah, it is
n * (n - 1)bc ~700 bots need to do ~700 minus 1 actions
a
continueinside anifstatement checking if the bot domain is the same as the subscribing one would sufficeedit: or use a search algorithm to pop the domain from the stack before starting the loop, that would be more efficient
edit2: even better: assuming all bot names are the same, you just iterate over the stack (constant), and pop each domain (new stack minus popped domain) and feed it to the 2nd loop.
edit3: SCRATCH EVERYTHING. The bot names don’t even have to be the same, you just iterate over a constant stack of
botname@domainentries and pop the iteration from it… feed the new stack to the second loop (nested) and done. Why did I take so long to reach this?In order to avoid this restriction you would need a global instance discovery mechanism, which is extremely hard to implement without a central server that keeps a list of all instances in the network. And if you do implement instance discovery through a central server you really are losing the whole point of decentralization.
Additionally, it’s good that each instance does not federate with everyone else by default. If it did, it would have to process all activity and keep a local copy of all the content in the entire network. This would be insanely inefficient, and make it prohibitively expensive to run even a tiny instance with 1 user and no communities.
Decentralization isn’t useless if you can’t immediately see everything in the network, come on… We’re just spoiled by centralized services.
I don’t think you do. Instances should merely reach out to other instances it’s federated with periodically to get a list of communities and some of their metadata. Ideally, they could ask all of those other instances to notify it when a community is added, modified, or deleted, and then store that metadata.
That should be pretty easy to implement, and maybe it already has, idk.
Sure, but this isn’t finding new instances, just new communities on known instances. Indeed, this is not difficult to implement. The reason it’s not done already is for resource economy. A lot of instances are already struggling to scale, making them process and store a lot more content with little value for most users of the instance isn’t feasible for a lot of servers right now.
A list of communities isn’t “a lot more content.” Just run it once daily and the problem is solved. Instances don’t need to store posts, just community names available on that instance.
If the issue is finding new instances, I think it’s fine for it to take some time the first time someone tries to find a community on that instance. But after that, it should immediately have a list of communities from that instance.
Ummmm… All you need is some bots on each instance that automatically will interact once with communities known on lemmyverse.net and boom, you have unlocked full federation for every user on those instances. You are not losing any privacy through that, it just skips the steps where user has to manually index a sublemmy before it federates and makes platform more usable.
Sure, but now this system has a dependency on the “centralized” lemmyverse.net service. And also your instance now has to receive and store a copy of almost the entire network’s content. Lots of instances are already struggling to sustain the load, this would make the problem even worse.
If a single instance decides that it can sustain the increased load and doesn’t mind depending on lemmyverse.net sure, nothing’s stopping them. But it shouldn’t be the default behavior for all instances.
Yet bittorrent dht is 20 years old. How can this supposedly decentralized service be unable to self organize. Is Lemmy some kitchen napkin high school fair project ?
Social media and torrents are pretty damn different. There’s a reason no federated platform has implemented automatic discovery, even ones with much more resources than Lemmy, like Mastodon.
I don’t know why you folks keep pointing at missing features and saying “Lemmy doesn’t have this pretty advanced network feature, so it’s not really decentralized”, or “it cannot organize”, or “it’s useless”… It’s basically two people’s passion project that only blew up in the past month because reddit fucked up. You’re not paying for it, are you? So I really don’t see how this attitude is warranted.
The tech is right there, it’s 20 years old. I’m pointing at it in response to people saying “this is too hard, we can’t have 700 instances sharing a few kilobytes of text !, You’re asking too much”
How is that not part of base code. Lemmy is completely unusable until this is fixed. The clock is ticking on Reddit’s implosion. If this isn’t fixed, the Reddit userbase will go back to Reddit for another 20 years. Please don’t let Lemmy as useless as Mastodon, this is clearly design sabotage by silicon Valley big tech.
Calm down bro. Your negative energy is harshing the vibe here. Let’s try that again
See? I liked a couple of your comments in the other thread about downvotes being public information, but you’re sounding pretty defeatist and frankly, miserable in the past few hours. If you don’t want the reddit userbase to go back, the best thing you can do is be a user that other users enjoy interacting with.
Unless you wanna step in and start coding this thing 🤣