Do we have coolguides yet? This is a good place for it.
Yup.
@coolguides@kbin.socialWhy isn’t that clickable?
So what about instances that block other instances? I.e Beehaw. Will they still receive updates?
“has anyone from my server interacted or searched for the post by it’s URL” is misleading. I struggled with this yesterday. Turns out you have to search in a very specific way.
In both kbin and Lemmy, you can’t just go to the community’s URL (which is utterly bizarre). You must search the full magazine name. In Lemmy, you weirdly need the
!in front when searching it to find it. In kbin, you don’t need that, but you do need to search the magazine in the “neutral” search mode, not magazine search mode (lol wut?). Actually, in Lemmy you also have to use the “normal” search field and not the community search field.And of course, both have a discovery issue. People want to be able to search a partial string like “hobby” without having to know what instance their community might be on or if the full name might be things like “hobby_discuss”, etc. They should not need a separate tool to do this search. That’s just a barrier to entry.
Anyway the whole thing is a usability barrier that needs to change. It also makes smaller instances actively harder to use, which is a bad incentive. We don’t want people to experience small instances as “buggy” (even if it’s working as intended).
Anyone currently trying to create a sub should have an account on every major instance and subscribe to their new sub to ensure it shows up in the search. And yes, that is just completely silly (and unscalable beyond the biggest instances).
In Lemmy, you weirdly need the ! in front when searching it to find it
This hasn’t been my experience on Lemmy. I’m regularly able to use for example !anime_tiddies@madeup.server or https://madeup.server/c/anime_tiddies in the search bar and it resolves it both ways. Sometimes you need to wait a few seconds for it to populate though.
I will simply post /c/animetiddies and wait for the server architecture to unbreak itself until my link becomes valid. Since that is obviously the way it would be.
Thank you. As a newcomer I find this very helpful.
Devs got to start adding this chart to their FAQ pages. Cleared up a bunch of questions I had.
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.
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.
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 ?
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.
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?
This would increase server load and traffic by a huge amount though, and would the benefit really be that big?
There are already quite good places to find communities for stuff you’re interested in, and less niche stuff will be federated “automatically” by these rules unless you’re on a small instance.
Good community lists:
https://lemmyverse.net/communities
https://browse.feddit.de/Reddit communities now on Lemmy:
https://sub.rehab
https://redditmigration.com/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 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@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?
wait… so if one of us follows an NSFW, we all get to see boobs? noice!
Oh, look at Mr. Fancy Pants with his Subscribed tab. If there’s a personal front page on kbin, I’ve not found it yet. :P
Do you mean https://kbin.social/sub ?
most people on the internet have way too smooth brain to comprehend this
therefore Lemmy is complex and scary
