• If you are asking if the kbin.social instance/server can handle your existing content and future content, you will have to talk to the admin.

• If you are asking if the Kbin software can handle your content, sure, the software is only a software. Your data will rely on the capabilities of your hosting provider.

• If you are asking if there are Kbin instances that can handle your content, you will have to contact them individually and find a way to struck some deal.

You can check this list of the different servers/instances using the Kbin software –> https://fedidb.org/software/Kbin

Or, you can host it on your own: https://codeberg.org/Kbin/kbin-core

^_

I saw your reply but it is yet to federate in other instances.

I know magnet links are just links, but post sharing them are still copyright infringement right?

No. Again, you just posted a link. What determines a link as a potential Copyright infringement is the content it is linking to.

Let’s use an example: https://download.documentfoundation.org/libreoffice/stable/7.5.4/deb/x86_64/LibreOffice_7.5.4_Linux_x86-64_deb_helppack_en-US.tar.gz.torrent

It’s not a magnett link, but just the same, I linked to a torrent file. It is not a Copyright Infringement.

But if the link is a link to a content that violates the Copyright Law, then there is potential issue.

Linking by itself is vague. There are countries that don’t consider links as Copyright infringement, because again, these are just links. Only the host is causing piracy / infringement. However, there are countries that considers linking as an act of distribution of an infringement material, so it is illegal for these countries.

So there’s no way to scrape an instance to back it up as a third party?

If you have a script, then you can. You can submit links to web archive services and they’ll scrape the site to archive a copy of it.

I understand someone not wanting to have pirated content on their instance, but do you think mods will go out of their way to un-federate?

Oh yes, definitely. You can count on instances defederating/blocking instances tolerating Copyright infringement activities. There are various blocklists available for instances to use, and there are groups where admins share and discuss these things.

So, sooner or later, an instance tolerating Copyright infringement will find itself isolated and potentially an island.

It can remain online as a regular site. It just won’t be federated with anyone.

One more thing. There are blocklists and admins who will defederate instances just because they are not blocking certain instances. Thus, if I am running my own instance, I might be forced to defederate from an offending instance to avoid being defederated by everyone else.

Not really. Most fediverse software create a cache of content on their own servers to make it easier to display content for their local users.

So… this brings the issue of “hosting”.

For example, if I link to this Torrent file: https://download.documentfoundation.org/libreoffice/stable/7.5.4/deb/x86_64/LibreOffice_7.5.4_Linux_x86-64_deb.tar.gz.torrent (LibreOffice 7.5.4), this link (not the file), and this entire comment, will have a copy in every instance that creates a local copy of content they receive.

(Some fediverse instance even locally host images to avoid fetching images again and again.)

Now, if we assume that a simple link is “illegal”, even if it is not piracy (like in the case of LibreOffice above), then all the instances which created a local copy of this reply might be put in trouble.

The fediverse is fast in fediblocking users and instances which tolerate activities that may place most instances into legal issues.

As far as I understand if any fediverse instance decided to start having magnet links and stuff like that, eventually it would be taken down by DCMA notices and the like. But what could be done so a community like that could thrive?

No. Magnet links are just that, links.

Some questions:

1. Would other instances that federate with it get in trouble? They can always feign ignorance.

That depends. Again, magnet links are just links. No one would get in trouble for linking to a magnet link to download #LibreOffice or to download a collection of #eBooks released in the #PublicDomain or #CreativeCommons.

1. Could an intance which holds magnet links and trackers be backed up every day, so that as soon as one instance is taken down another one takes it’s place immediately?

That depends on the people managing the servers. If they want to create backups, then yes, otherwise no.

1. Could an instance be owned annonymously? Can you register a domain and keep a server running somewhere without repercussions?

Sure. As long as you don’t use payment methods that can be traced back to you, and you ensure that your connection is encrypted and you trust your VPN provider. Since you also have to pay for a good VPN provider, that VPN provider should also be accepting a payment method that can not be traced back to you. Not to mention, you should not use your regular computer, regular browser, and definitely avoid mobile phones as you’ll always be tracked with it.

1. Could a lemmy instance live in an onion domain, and still interact with the rest of the fediverse? Would that improve anything regarding the instance being taken down?

Yes. Any #fediverse instance can live in any darknet. Now, if they can connect to those in the Surface Web or Lightnet, all comes down to if the #Darknet they are using offers a bridge back. Or, their server directly connected to the Surface Web instead of passing through a bridge inside their Darknet.

1. What about running instances in countries that do not enforce piracy laws? Could someone in some random country that does not care maintain an instance, which all of the fediverse can access/comment/contribute?

You can do that. But that instance will more likely get defederated and included in various blocklists or fediblocks.

To sum up. Magnet links are just magnet links. There is nothing illegal about it.

The same with Darknets #TOR and #I2P. There is nothing illegal about it, unless your country passed laws about blocking it.

The real question is, which instances will have issues federating with instances that links to Copyright infringement materials. As linking (not hosting) is vague, the general reaction would more likely be to defederate that instance to be safe.

In the end, that instance’s reach will be less and less and less. Probably reach a point wherein it’s a lonely island.

^_

Quick question, just Lemmy?

Ultima series.

Hopefully that doesn’t happen.

1. For some topics, there are already existing, very active, communities before the subreddits with the same topic migrated over. Who should merge with whom? The existing large communities with subreddit migrators? Or, the subreddit migrators merging with th existing large communities … and conforming to the rules and culture in those existing large communities?

2. As mentioned, there are different cultures and rules that develops per community. There is no such thing as one-size-fits-all.

3. Even if communities “consolidate over time”, it will still split up no matter what. That’s how it has always been sincee the beginning of online communities.

4. IF communities indeed consolidate over time, if that server/instance goes down, the entire consolidated communities will be gone overnight, and all the content they collected together. We’ve already seen this happen just this year, forget about the previous years.

In short, don’t expect it. In fact, it should be supported to ensure that:
a. we don’t return to a centralise system
b. we don’t put all our eggs in one basket
c. we build redundancy, continuation, and resiliency.

^_

Please don’t take this the wrong way, just a friendly tip:

with kbin finally with Lemmy again

If you are talking about instances, use the entire name. Try to avoid mixing your references between software and instances, otherwise it will be confusing and can cause misunderstandings. ^_

Kbin has always been “with” Lemmy.

• Kbin: https://fedia.io

• Kbin: https://readit.buzz

• Kbin: https://karab.in (oldest Kbin)

• Kbin: https://u.fail

• Kbin: https://fediverse.boo

• Kbin: https://kilioa.org (SOLO instance)

• Kbin: https://forum.fail

• Lemmy: https://sopuli.xyz

• Lemmy: https://lemmy.blahaj.zone

• Lemmy: https://lemmy.world

• Lemmy: https://lemmy.ml

• Lemmy: https://beehaw.org

The one which was being hammered by registrations and bots was/is https://kbin.social and it is just one of many.

^_

Re: fragmentation

Also, this negative “fragmentation” view is biased. Before the subreddit migration, there were already existing and well-established communities in the fediverse. Suddenly, after the subreddit migration, it’s being called “fragmentation”.

For example, topics like Star Trek and Books. There are already large communities in the Fediverse before the related subreddits migrated. Yet, you will see people calling it “fragmented”, some even have the guts to call other communities to “merge” with the migrators.

This is wrong and very rude.

Having multiple communities is good. There is no one-size-fits-all. Also, we’ve been doing that in the entire history of the human race. That said, even if everyone merged into one mega church, it will still split up like it or not.

In other words, we need to stop viewing “fragmentation” as negative. In fact, don’t use that word. Don’t even think about it. Just setup your community and build it up. Create your own culture. Your own rules. System, team, and invite people who wants to join your type of community.

Multiple communities is healthy for everyone. It is a win for everyone.

And… haven’t we learned what happens when we rely on one service? One central platform?

A lot can happen.

1. It suddenly goes offline. We’ve already experienced this in 2023. A lot of large communities disappeared for almost a week because the instance encountered issues.

2. The instance owner might no longer have the resources to continue. Not necessarily on the financial side, remember, there is the technical side which will take an owner’s time.

Sure, they can get other admins to join. But, as an instance admin, would you easily trust access? Consider also the trust your users has given you in protecting their data and privacy.

There were instances who went offline because of that, and instead of transfering management to a new team, or selling their platform to someone, they chose to shut it down permanently because they value the data and privacy of their users.

So… if that instance that happens to be hosting a one-size-fits-all community goes offline…

Well…

1. Or, it can very well be something uncontrollable. Server farm fire, raid, who knows.

But if we let people build their own communities spread across different instances, then we are building redundancy, continuation, and resiliency. If one goes down, for whatever reason, we have existing communities we can move into and continue our discussions, with minimal interference.

^_