• 0 Posts
  • 15 Comments
Joined 1 年前
cake
Cake day: 2025年6月5日

help-circle

  • As far as I know, the problem is that Lenovo doesn’t make the SOCs that actually implement the security features GrapheneOS requires; Qualcomm does (assuming this phone uses a Snapdragon chip - I didn’t check). And Qualcomm only puts these security features into the most powerful SOCs, which are themselves only appropriate for flagship phones.

    I hope that some day more budget SOCs will get these security features too so that more people can reap the benefits, and I hope Graphene is pushing for this too, but I don’t think we’ll see it any time soon.

    That being said, I’m just happy Graphene has any partnership at all. One step at a time; once these phones are done they can focus on expanding their offerings more.









  • If you feel like learning a third shell, I find that Nushell is even easier to use than PowerShell.

    open stuff.json | each { get fieldName } | where { str starts-with "asdf" } | each { $in | str upcase }

    This gets all the objects in the given json file, then grabs the value of the field named “fieldName”, then filters all those values to find the ones that start with and, converts those to uppercase, and prints them to the screen as a nicely formatted list


  • Rust is a programming language which was designed to be memory safe without any of the overhead caused by traditional memory safety techniques employed by existing languages (namely, garbage collection and reference counting). It does this by shifting the memory management from happening at runtime to happening at compile time. The compiler forces the programmer to follow certain rules to ensure that their program can be proven to be free of errors such as use-after-frees and double-frees. Because of this design philosophy, Rust is a good fit as a replacement for C, because it can do everything that C can while ensuring the programmer doesn’t make any mistakes with regard to memory management.



  • As I understand, Anubis doesn’t make the user do anything. Instead, it runs some JavaScript in the client’s browser that does the calculations, and then sends the result back to the server. In order for an LLM to get through Anubis, the LLM would need to be running a real JavaScript engine (since the requested calculation is too complicated for an LLM to do natively), and that would be prohibitively expensive for bot farms at any real scale. Since all real people accessing the site will be doing so through a browser, which has JavaScript built in, and most bots will just download the website and send the source code right into the LLM without being able to execute it, real people will be able to get through Anubis while bots won’t. The total amount of extra energy consumed by adding Anubis isn’t actually that high since bot farms aren’t doing the extra work.

    Take that all with a grain of salt; that info is based on a blog post which I read like 6 months ago, and I may be remembering incorrectly.