Good luck and thank you for keeping the cogs turning.

OMG, posts load instantly now, used to take 3 to 15 seconds. I’m in US East Coast for reference.

If you think anything on the Internet can ever be forgotten… Your going to have a bad time. Passwords, one of the most protected data types, are compiled from beaches into huge databases so that hackers can use them to try to log into website. There are literally dozens of not hundreds of those password databases on the public Internet to be downloaded, not to mention private or dark web collections. If passwords are not safe, what makes you think publicly available social media would be any different?

Even if somehow the whole federation agreed to purge all post every year, things like the Internet archive and Google cache of pages would retain the data.

Agreed. Had to get a travel one to go with me on trips…

There are many variables that makes a yes no answer impossible. Currently there are too many instances for a lawsuit to be brought to each. The instances are in different countries, do different laws would have to be navigated for each. For example, in the US, Google has like to piracy websites. Google doesn’t allow housing of piracy on their platform. Google does some removal of listings but it is but exhaustive.

Google is not being held liable, and I bet if an instance happens to cache piracy content due to a user interacting with another insurance, Google and ISPs would be interested in helping that instance so president isn’t set that creates liability for traffic that happens to traverse servers, if it is but being served by the server.

This is a very ELI5, and isn’t a full discussion of all the variables. A difficult question even limited to one country’s laws.

Realistically, the while point of a federation us to make it impossible to shut down, or censor world wide, the community as there are simply too many different servers. This works against corporate attacks as well as legal.

It will likely depend on how popular Lemmy becomes as well as the server physical location \ DNS registry that of used.

Having a piracy channel on an instance located in a country that does not recognize intellectual property, and a DNS registration in a TLD that doesn’t respond to piracy complaints should be pretty bullet proof. Only thing that companies could do at that point would be to try to get a court order to have the DNS entry blocked by US \ EU \ etc DNS providers, or a court order for ISPs blocking the server IP address. These could be easily circumvented by changing the server IP if it happens and updating the DNS.

Thank you for the answer. I have delt with scaling DBs with tons of data so the alarm bells were ringing. DBs tend to be fine up to a point and then fall over as soon as the isn’t enough ram to cache the data and mask issues of the DB architecture. With the exponential growth of both users and content to cache, my gut tells me this will become a problem quickly unless some excellent coding is done on the back end to truncate remote instance data quickly.

Sadly I am better at breaking systems in wonderful ways than building systems for use, so I can’t be too helpful other than to voice concerns about issues I have ran into before.

A quick question related to the DB, is the data broken into many smaller tables or is most data in one or two tables? If it is all in one, we may run into performance issues as soon as the DB becomes to large as queries run against whole tables unless promised really well.

As an offensive security worker… I can’t help but read people listing out their attack surface 😂