The digital safety act will probably affect us at some point but if we bring more clarity to how downvotes and censorship on the frontends are done we should pull through. This may be an unpopular opinion but we need to decentralize the downvote services we have a bit more. Have them create a Decentralized TOKEN fund so the community can vote on how it is run and funded. Have the Decentralized HIVE fund, fund the TOKEN fund instead of the service itself. We need more transparency on how downvotes are done by the services we have. I think we have the services already that should satisfy the regulators but we need to bring more awareness and clarity on how it is done if we don't I fear we will destroy ourselves trying to protect ourselves. Frontends depending on where they are located may get effected more then HIVE itself since they are an access point. A frontend may at some point may have to start censoring more then they have been. Where they just don't retrieve a particular page or profile. An the Canadian government says we have freedom of speech we just don't have freedom of reach. Maybe @hivewatchers could help bring more awareness to the other downvote services that are out there and a post on what tools they use to determine what is plagiarism, spam, etc. We need to normalize some censoring and make people aware of how we are doing it so that regulators don't demand we regulate at code level. As long as we focus on frontends doing the hard censoring and downvotes doing the soft censoring we should hopefully be able to keep HIVE itself censorship free.