OP here, I say “Xeets”

I didn’t make this, I just think it’s cool. Source code here, live version here.

It still blows my mind how this is still a question and not a default “no.”

If you’re here on Lemmy, odds are you don’t like walled gardens, and would rather roam free on the vast open plains.

If Threads federates, Meta’s basically giving its users a path out of its walled garden, into the free world.

If we, as the natives of that free world, say “Everybody defederate with Threads,” we’re just building our own wall around Meta in response to the walled garden opening its gates.

If we want people to roam wild and free in the fediverse, and we don’t like walled gardens, how does it make any sense for us to respond to one of the world’s walled gardens letting its people out by building our own wall to keep them in?

Apparently the simulation is written in C++, doesn’t that mean it’s C++ Elegans?

Some thoughts:

• If somebody puts it on the Internet in public, by definition that means if you have a computer, you can see it.
• If you can see it, you can make a copy of it.
• If you can make a copy of it, you can put that copy on your own computer.
• If you have it on your own computer, you can order that computer to run any computer program on it, including training an AI.

If you don’t want people to use the information you post in a certain way, the best way is to not post it at all.

The second best way is to post it in a private place, that is only accessible by a small number of humans, tell them you don’t want them to post it in a public place, and hope they follow your wishes.

I probably misunderstand how the fediverse works, but my worry is that the small instances won’t be able to hold an ever-growing amount of data forever.

Let’s pretend you run a small Lemmy instance (~100 users).

If you federate with a large instance, you (i.e. your instance) will only receive new posts from communities that your users subscribe to, or users that your users follow [1]. These are deduplicated, in the sense that if all 100 of your users subscribe to the same community, you only need to download and store one copy of that community’s posts in your database.

[1] AFAICT. The current implementation of Lemmy seems to handle federation using the activitypub_federation crate. I skimmed the docs of that crate, but they aren’t 100% clear about this.

the posts I’m posting here today might get lost in time because the instances that annex it will have shut down by then?

You have the same problem with any data you put online anywhere: The people currently keeping your stuff online might delete it anytime they decide it’s not worth the trouble to keep it online.

If it’s important to you that certain information stays online, keep a copy on a disk in your house; check back periodically to be sure it’s still online, and if it’s not, you can always use the copy in your house to put it online again somewhere else. If it’s very important to you, keep multiple copies on multiple disks hosted by multiple companies on different continents.

50 years from now on

Predicting what will happen in tech in 50 years is a pretty daunting challenge.

50 years ago, in 1973, all the computers on the ARPAnet (the predecessor of the Internet) could be easily listed on a single piece of paper. The home computer was still years from birth. The Zilog Z80, Intel 8080, Motorola 6500 and the MOS Technology 6502, which would play key roles in early home computers and gaming consoles, were just beginning to enter the market.

No.