So long as they’re totally de-identified (not linkable to people), this is a good thing. Image a GPT that can diagnose you 10x as accurately as a human and 1000x faster. This can revolutionize medicine.
Generally, data science is evil and so is Google, but this needs to be done.
Dismounting soap box now.
That I am. I've been fucking around with it for a couple of hours now and I just can't figure out why it's not working. I'm pretty convinced that it's not me though. I tried using the fluffy app as well but I couldn't get that to work quite right either. I'm starting to wonder if there isn't something going on with Android 14 that's causing the issue but I really don't know.
Thanks. I joined. I think there might be an issue with the client now, but the link worked.
I followed the prompt for the encryption upgrade and that failed.
Maybe? Edit: removed unintentional redundancy
Not for me or that other person. I dunno dude. I never used matrix before though so perhaps I'm clicking the link wrong or something crazy.
Let me know when the link works
Or they could go with the good old "if you sacrifice privacy for security you will have neither" - Benjamin Franklin
GPT is fairly useful but I definitely don't trust it implicitly. Lol
A Rust procedural macro (proc macro) is a metaprogramming feature in Rust that allows you to define custom syntax extensions and code transformations. They operate on the abstract syntax tree (AST) of Rust code during compilation and can generate or modify code based on annotations or custom syntax.
Sandboxing a Rust proc macro refers to restricting the capabilities of the macro to improve security and prevent potentially harmful code execution. There are several reasons why someone might want to sandbox a proc macro:
Security: Untrusted code can be executed during the macro expansion process. To prevent malicious code execution or code that could access sensitive information, sandboxing techniques are employed.
Preventing unintended side effects: Some proc macros might inadvertently introduce side effects like file I/O or network requests. Sandboxing can limit these actions to ensure the macro only performs intended transformations.
Resource control: To manage system resources, a sandboxed proc macro can be configured to run within resource limits, preventing excessive memory or CPU usage.
Isolation: Sandboxing helps keep the macro's execution isolated from the rest of the compilation process, reducing the risk of interfering with other parts of the code.
Sandboxing a Rust proc macro typically involves using crates like sandbox or cap-std to restrict the macro's capabilities and limit its access to the system. This ensures that the macro operates within a controlled environment, enhancing the overall safety of code compilation and execution.
-GPT
I didn't get it either.
Seems to me if your code will be this unpredictable, you should only run it on an air gapped machine
Certainly not foxit PDF. I just had GPT analyze their privacy policy and it’s nothing short of a nightmare
I just use Kinkos or the local drug store for the rare photo print. Let them worry about their inkjet drying.
Business class laser printers are where it’s at. I don’t get why people still buy inkjets.
I believe there’s potential for great benefit for everyone.
I also believe that if my records are used to innovate I should get a cut and get an opportunity to opt in or out. I should have agency. I don’t like that I don’t.
I still believe that this is, on balance, a good thing.