Stimmed

I believe the setting is allowed by instance default instead of user setting in the app. It also fails to blur user avatars in nsfw posts viewed with blur enabled which results in porn being showed from the user avatars, even when the post its self is blurred.

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.

For best practice, my personal recommendation would be to not have any service public facing besides a VPN that requires MFA. segment self hosted services into separate VLANs based on how sensitive the content is. Disallow all traffic between VLANs unless required and only allow based on port number, specific resources needed. Don't forgot to disable outgoing Internet access unless required. Devices like Chinese made video cameras should never have an Internet connection.

My network looks something like: home vlan, work vlan, Netflix \ hulu streaming devices, cctv, wireless work, wireless home, wireless guest, iot, servers, network management. Would be way overkill for vast majority of people, but I would be hypocritical not to considering what I do and I do have a different threat profile than most.

Another thought: self hosted through VPN with MFA and nothing public facing is probably safer than cloud as long as you have cold backups.

It was meant more as a joke than criticizing hosting your own services. I personally have a VPN with MFA, and services that I host for my self that are segmented to a paranoid level (home camera system on own vlan, restricted from being able to reach any other vlan or the Internet, etc) with a deny all and explicit allows on per host and traffic type. The amount of work that went into building the network is probably overkill, and it is still susceptible to nation state and supply chain compromise but hopefully whoever gets in will curse me if they try to move around the network.

Realistically, every added service and host is added attack surface and chances for misconfiguration \ supply chain attack, but being alive is a risk too....

I'm guessing system admins and dev op is over represented here so some of our home networks may be targeted as a path into a corporate environment, but I'm guessing the chances are low. Sadly even the most secure networks are not an impossible target. The attackers are well ahead of defenders of networks. Attackers need exceptions, while defenders need everything perfect. Much harder to accomplish.

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

Bonuses are discretionary. Stock is questionable, especially if it is not immediately 100 percent vested, 401k tells me they are completely out of money and can't / won't source additional funding.

In tech, you should always be looking at the next job, even if you are comfortable where you are. Loving what you do, who you work with, work life balance can all offset certain amounts of money, but knowledge and experience is either always growing or growing stale. I'm guessing at early 30s, you are not in an exec position and changing companies with lead to faster career growth than sticking around for the company to turn around it's books and promote you.

Depends on the load, budget for capex and opex, and what the network will be running :)

I liked HP procurve before the Aruba firmware was introduced. For wireless, I used to like Ruckus 5 years ago. Cannot stand the move to cloud management that all the WAP vendors seem to require.

For auth, the click verify of duo is pretty nice if the security of a physical OTP device isn't needed.

For firewalls.... ASA if NSA isn't in the threat profile.

It is always good practice to set up certificates everywhere. I do it for all of my internal services. Each person has a different level of care for how important privacy and security are and some people have abnormal threat profiles.

With that being said, options are usually to run self signed certificates, roll your own certificate authority for your network, or get valid certificates from a service like letsencrypt.