I'd prefer to stay within the [hacker ethics](https://www.ccc.de/en/hackerethics), and protect private data. For non-private/personal data, sure. But individual people need their privacy protected.
Me too, I'm hacker ethics all the way, which is why I'm saying anything network connected should really realize the "All information should be free." dream, and then private data should be far away from the internet, on computers/drives not even connected to the internet. The whole E2E encryption is a ticking time bomb people rely to keep their data safe from others, but nothing that you don't physically have close to you can be truly secret forever, and even then it'll be hard.
The last point is pretty clear, and the text below clarifies it:
> To protect the privacy of the individual and to strengthen the freedom of the information which concern the public the yet last point was added.
The privacy of individuals is important, regardless where they store their private data. Their account information -- what they buy, their medical information and so on is stored on servers and could be hacked.
I think the second point is equally clear, and further up on the list.
I agree that what people buy, their medical information and so on should be private, hence it should only be offline and not stored/handled on computers connected to the internet at all, the internet should be for public data exclusively, is my argument in the initial comment. Medical information would be only on effectively airgapped computers, as that data should be private, as you say.
So you say it is okay when someone you trust, uses that trust to upload your personal files from your air-gapped system to the internet, for everyone to freely share it, because now the data is "public"?
To me private file stay private, even if they get leaked onto the open or closed internet, because the public has no right to know them, they are private data of an individual. They might no longer be secret, but they are still private.
I'm talking about liking waffles, then you appear asking why I hate pancakes. Fun.
> To me private file stay private, even if they get leaked onto the open or closed internet
We have very different definitions of what "private" means. Once it's leaked, it's no longer private, and pretending it can go back to being "private" after being on the public internet, is doing no one any favors.
I just find it very interesting that someone equates secrecy with privacy. In my opinion, and in the current law there is a distinction.
If private data got leaked, like revenge porn, it is a breach and that private data that belongs to an individual is still private, and still needs to be protected. This is what GDPR and other legislation is about. If secrecy and privacy is the same, someone that isn't able to protect their data sufficiently will not have any privacy, thus any leaking of data is now the fault of the person that got their data leaked, not of the person that broke the trust and leaked it.
Your conclusion seems rather extreme to me. So of course data that got leaked, and is no longer secret is still private, because 'private' means who should be in control of that data, not about if the person has control or not.
I also don't follow your point about waffles and pancakes, because this is a pretty big disagreement we have here. To me this dialog is more like you are saying "I don't like laws", and I say "While I agree that some laws are stupid, other laws are pretty useful, for instance people shouldn't be allowed rob other houses, even if they are able to do that or even where invited." And then, instead of agreeing, you sort of say, "No, I really mean that. If someone isn't able to defend their home properly or give out invitations to someone, it is okay to steal from them."
> If what you're saying is true and accurate, then US-based AI labs are in big trouble.
Well... I would think that the whole AI industry in the US are working towards public bailouts... Which I guess they'll get under the current administration... So they'll be fine... Nobody there really seems interested in actually creating a profitable business anyway...
Element X is in some cases still a downgrade from Element. For instance there doesn't seem to be a way to create local key backups anymore. Also, that calls between Element and Element X are incompatible means both apps need to be installed in order to receive calls from all contacts.
Still, I love Matrix and hope that these issues will be resolved in time.
Manually importing/exporting keybackups is on the todo list (albeit towards the bottom). Supporting legacy calls is not (unless someone contributes it); the intention is to converge asap on native Matrix group calls.
I had to deal with Intel Quark SoC X1000 on a Galileo board years ago, where the LOCK prefix instruction caused segfaults. Since the SoC is single threaded, the lock prefix could just be patched out from resulting binaries, before the compiler/build system was patched.
Well... Maybe just have a BIOS on your system that fetches a markdown, pushes it to a LLM to generate a new and exciting operating system for you on every boot.
reply