| Blog | https://www.hilmargustafs.com |
| GitHub | https://github.com/lihram |
| 📍 | Denmark |
| Blog | https://www.hilmargustafs.com |
| GitHub | https://github.com/lihram |
| 📍 | Denmark |
guess what besties, it’s time to start an
😏✨ anger journal 💪👀
everybody with me now!!
@Dame_ I honestly didn't know about that article, thanks for sharing!
My position is pretty simple: allow users to disable processing that isn't on-device.
In the article you linked, they address all of my concerns, but I would still like to be able to disable PCC processing until I've seen what the security community consensus is.
Really glad to see they put so much work into securing it though.
y’all, what a fucking joy to /be/
so glad I got the help I needed. I hope you do too.
Apple Intelligence sounds like a privacy nightmare. I do enjoy the power of AI, but I want it to be under my control, and I want the data to be under my control as well.
I hope #apple does the right thing here and makes it possible for people to disable any AI that isn't running on-device.
AV1 is an increasingly important video format and it needs a memory safe, high performance decoder. We worked with the team at Immunant to develop rav1d, a Rust-based port of dav1d, a C decoder. This is the first of two blog posts about how the team approached this effort. Josh Aas, Head of ISRG's Prossimo project Complex data parsing is one of the most security-critical operations in modern software. Browsers must decode untrusted audio and video inputs encoded with extremely complicated formats in real time.
@rust_discussions I like this quote better:
"I'm picking up a lot about Rust-kernel bindings, and how the end result is much cleaner for both the C and Rust sides. So even if the resulting Rust work isn't merged, actually the effort spent creating the Rust interface would be a great help to both of them."