I submitted a proposal to lemmy a while ago to fix this and it was closed. I rewrote the proposal as a Fediverse Enhancement Proposal and a lemmy dev said on the discussion thread that they would not implement it and don't see an issue with duplicate communities.
I don’t think there is even activity enough to worry about those things yet.
This problem is part of why there's not enough activity. Any activity that happens in the threadiverse is spread across multiple, duplicate communities. That makes it harder for communities to build up active userbases and makes users themselves less likely to post or comment.
As long as there are multiple communities for the same topic, users are going to post the same links to multiple communities. The software has to handle it better. I submitted a proposal to solve it, but one of the lemmy devs have said explicitly that they won't implement it and they don't think duplicate posts are an issue.
There are 500 million posts on Twitter every day. Do you read them all? There are 2.8 million subreddits. Have you browsed them all?
Nobody subscribes to every twitter acct or every subreddit so nobody is expecting to have every single post delivered to them. The fediverse has a legitimate problem where ppl don't actually receive all the posts of accts they're subscribed to. It's silly to compare what the OP is complaining about to not being able to see every post on twitter/reddit.
It's definitely possible. There are quite a few self hosting solutions that have UIs for installing/managing applications. The author is saying we need to make those better.
no just like federating with mastodon.social doesn't make your instance a part of the Gargron fediverse. Meta can't control non-Meta instances that federate with them
I use TiddlyWiki via TiddlyPWA. It's an offline-capable PWA with a very quick sync capability. It works beautifully on my phone and desktop. It doesn't have folders, but it does have nestable tags, which works really well for me. I don't think it supports markdown out of the box, but I'm positive you can find a plugin for it. Plugins are crazy simple to install; you just drag and drop a link into you wiki tab and confirm installation.
This is nonsense. The fediverse isn't cryptocurrency. Having 51% of the fediverse doesn't give you any more control than having 1%. If your instance(s) implement a feature that the rest of the fediverse doesn't like, they can defederate.
Other instances either react by defederating, but because they only have 49 percent, due to network effects, they get extinct
If 49% of the fediverse defederates from the other 51%, it is now 100% of a new, smaller fediverse. You can't just claim that "network effects" will cause them to go extinct. Whether those instances have enough userbase to sustain a cohesive network depends on the actual number of instances/users. And the fediverse has sustained itself for over a decade with less than the current 2 million accts and most of that time it had substantially less than 1 active accts.
It’s not sustainable to keep offering poorly designed solutions. People need to understand some basic things about the system they're using. The fediverse isn't a private space and fediverse developers shouldn't be advertising pseudo-private features as private or secure.
and having a bot thrashing a server indexing everything
This is a completely separate argument and one that we already have mechanisms for. Servers can use status codes and headers to warn about rate limits and block offenders.
It is also one thing to read/interact with a site as that adds value to the site as a whole
A search index adds value as well; that's why this keeps coming up. And, again, there are existing mechanisms to handle this. A robots.txt file can indicate you don't want to be crawled and offenders can be IP blocked
I don't think an admin's permission has anything to do with it. If you post publicly on the fediverse, your posts are public. You should have the option to opt out of any indexing (just like you do for the rest of the open web). But saying its ok for you to read this post if it happens to come across your feed but you shouldn't be allowed to find it via a search is ridiculous. Users get to make the choice with each post whether its public or not, but they don't get to control how people consume those public posts.
That is how the fediverse functions. Instances send posts to anyone who request it, unless a block is in place. ActivityPub is opt-out and the web has always worked this way.
be mindful of the culture
There is no "the culture" on the fediverse. Your talking about a subgroup, which has a different opinion from other subgroups. They don't get to define "culture" on the fediverse.
Those vulnerable groups should have the tools to protect themselves, but that shouldn't stop the rest of us from having a functional and discoverable system. The internet, and the fediverse specifically, have always been a semi-public space and searchability has been a part of that since the beginning.
That post wasn't claiming that a search engine would only be used by trolls; it was explaining that they shut down their project because a chunk of the fediverse thinks that and complain about any search engine projects. Discoverability is one of the network's biggest challenges and a search engine could really help with that.
before they end up with a seat on the activity hub team. Then we’re back where we started.
There is no activity pub team. There is an informal group discussing enhancements at https://socialhub.activitypub.rocks but anybody can join that and submit proposals. Any nobody is required to accept or implement those proposals. I have joined the forum and submitted a proposal myself, but nobody has implemented it or even seems likely to.
Also, not blocking threads doesn't make your instance a "meta controlled instance". Meta has no power over any instance other than Threads. Even instances that don't proactively block Threads can't be forced to use any hypothetical Meta extensions to AP. And its really unlikely that people who started servers on a minuscule network (most likely for fun or philosophical reasons) are going to follow Meta's lead just to have access to more people. Everyone who is here and everyone who started a server here knowingly did that on a network that is a tiny fraction of a percent of the size of other social networks; an increased userbase isn't some big reward for fediverse server admins.
Ok. Your point was that you can view Threads content without a Threads account and even if they required an account to view Threads content, users with other fediverse accounts could still see the content because that's how federation works.
Don't you have to have an Instagram account to use Threads? Every service on the fediverse makes you create an account. And all of them can put all its content behind that account; nothing in ActivityPub prevents that
They are different because most users weren't aware of XMPP. They weren't making a conscious choice to use an open standard. The fediverse, on the other hand, has grown specifically because people are seeing the value of an open ecosystem.
When google started removing XMPP support, users weren't aware and didn't care (other than losing contact with a few holdouts). If Meta implements AP support and then removes that support or modifies it so that it breaks some of expectations of the fediverse, most users will move to instances that don't use Meta extensions. Meta can not take your instance or make it use their extensions, so an open fediverse will always exist.
0x1C3B00DA @ 0x1C3B00DA @kbin.social Posts 14Comments 113Joined 2 yr. ago
I submitted a proposal to lemmy a while ago to fix this and it was closed. I rewrote the proposal as a Fediverse Enhancement Proposal and a lemmy dev said on the discussion thread that they would not implement it and don't see an issue with duplicate communities.
https://socialhub.activitypub.rocks/t/fep-d36d-sharing-content-across-federated-forums/3366