It’s not really about the confusion, it’s just unnecessary complexity. Magazines and communities for example are completely equal concepts, the only difference is the name for some reason, probably marketing or some such.
It’s not really about the confusion, it’s just unnecessary complexity. Magazines and communities for example are completely equal concepts, the only difference is the name for some reason, probably marketing or some such.
I don’t think it’s even close to the same. It’s more like forum software everywhere calls a post a “post” and a reply a “reply” and not something else.
Both sites are link aggregators, both sites have sub groups that are meant for a specific topic that links can be posted to, this concept should have a name.
Yep, clients/UIs need to detect links to other instances and automatically reformat them to instance-local links. Configurable and indicated cleary that this happened, with a clickable icon next to it and resulting popup or some such.
Yeah honestly I’ve seen so many posts with multiple paragraphs explaining federation, while I’ve just been telling my friends two sentences like “it’s just like reddit but instead of one website there’s multiple independent ones (called instances) that all see each other’s content. All content on all those instances can and should only be accessed through the website you signed up on, and when you do that it works basically completely like reddit”
This leaves out a bunch of information of course, but if they want more, they can always be confused and ask or look it up themselves.
And it will work, since many people can’t distinguish decent behavior and trying to completely selfishly signal decent behavior without actually wanting to do anything.
There should be no vote, it should just be decided between the lead devs. Users will follow and largely not care.