ckwalsh
Decide one of them is delivering something, run into each other at the exact same spot, and call the police to resolve it?
> who tf uses prompting to "pretty please don't cheat on this"?
People who don't understand how LLM's work. Kids, teachers, your next door neighbor. CEOs and government officials.
I am not trying to argue that the author doesn't understand how LLM's work; they clearly do. Their prompt was written in a way that leaves those assumptions implicit, in a similar manner to those non-technical folks using LLMs every day.
> the best practices for ages...
We cannot expect the entirety of humanity to understand / use LLM best practices. We need to figure out how to ensure LLMs operate as the majority of humanity expects despite how they are implemented, and until we can do that, do our best to prevent them from being used in an unsafe manner by the nontechnical population of humanity.
Im guessing those private investors specifically requested not to be named.
I’m guessing the urls in that db were either generating a ton of backend load, so they were pushed to devices, or perhaps are customized on a per user basis for some reason
They saw some benefits to Rust, tried it, and continued to measure. They identified the Typescript/Rust language boundary was slow, and noticed an effect on their contributions. After further research, they realized there was a faster way that didn't need the Rust dependency.
Good stuff, good explanation!
Meta’s WWW codebase is its oldest, and still written in Hacklang. Lots of internal tooling is also written in Hack.
I wouldn’t be surprised if there are more committed lines of Hacklang than any other language (although, a good chunk of that is codegen, vs other core languages where codegen is part of the build process).
"package/dependency management" - Everything is checked into a monorepo, and built with [Buck2](https://buck2.build/). There's tooling to import/update packages, but no need to reinvent pip or other package managers. Btw, Buck2 is pretty awesome and supports a ton of languages beyond python, but hasn't gotten a ton of traction outside of Meta.
"linting, formatting" - [Black](https://github.com/psf/black) and other public ecosystem tooling is great, no need to develop internally.
"why is type checking the exception" - Don't know about Astral, but for Meta / Google, most everyone else doesn't design for the scale of their monorepos. Meta moved from SVN to Git to Mercurial, then forked Mercurial into [Sapling](https://sapling-scm.com/) because simple operations were too slow for the number of files in their repo, and how frequently they receive diffs.
There are obvious safety benefits to type checking, but with how much Python code Meta has, mypy is not an option - it would take far too much time / memory to provide any value.
1. Access memory that hasn't been explicitly allocated to your program 2. Access memory that was was previously allocated and freed by your program 3. Access memory that could be modified by a separate thread / function of your program, outside of some locking mechanism.
I'm sure there's a more academic definition, and stronger guarantees, but those are the basics.
Now, these guarantees impose restrictions on how code is written, and runtime overhead to enforce. There are many cases where a human can write optimizations and ensure those guarantees in a way the compiler cannot verify. This is why Rust has an "escape" of writing "unsafe Rust", where the compiler does validate those guarantees. Unsafe Rust includes expanded primitives, such as "Box::leak()", that enable writing these optimizations, and may explicitly leak memory without maintaining a reference
If a program is written using purely safe Rust, it should not be possible for a malicious input / request to corrupt internal data structures, read memory that shouldn't be read, or all the other "interesting" things that get highlighted by Heartbleed and other big security vulnerabilities.
Note that I say "should not be possible" - the Rust compiler can and has had bugs that break those memory safety guarantees under certain conditions. They aren't common, but it's unfair to say "Rust is perfect and 100% safe"
I strongly recommend everyone learn Rust, at least to the point where you "grok" the borrow checker and what it's trying to enforce, even if you have no intention with regularly using Rust. After learning Rust, I found the patterns the borrow checker enforces incredibly useful when writing C++, and ensuring I don't make silly memory mistakes that may result in a crash or vulnerability.
You're probably right that RSA 4096 "just worked", and some library in their stack doesn't have elliptic curve support. And again, if N is small, the verification performance doesn't matter that much.
Nice find and writeup!
This spooks me. I take this to mean either:
- They are still using the compromised key for validation, meaning if you have access to any old token, you can still mutate that, maybe needing to play around with the issuing times
- They built an allowlist of all permitted tokens, and check that list first. In which case, might as well use random session ids instead of JWTs, and at the same point where the allowlist is being checked, mutate the request to inject a JWT that the backend can use.
Also, kind of curious why the switch to RSA4096 instead of elliptic curves, since they are generally faster / smaller.
It's definitely gone down a few times, but I've learned a TON tinkering with it. super easy to spin up a new hobby project, a nice web UI for seeing what the heck is going on.
I've completely borked it a couple times and survived one micro pc migration. Can't recommend it more
I have used Mosh for years and recently heard of ET, but when I tried it I experienced noticeable hangs that I don’t get with Mosh, and I went back.
I heard from several people that “ET is the new Mosh”, but it won’t be for me unless I can figure out/resolve those hangs
I was on the jury of a federal fraud trial with 2 defendants with 15 charges, ~30 million in losses.
We were thorough and went through each count separately, including reviewing some of the evidence, and were done in maybe 8 hours spread across 2 days.
We ended up with a mixed verdict: one count not guilty for both, another not guilty for one. I fully believe they were aware and committed fraud for the not guilty counts, but the prosecutor wasn’t able to cross the “reasonable doubt” threshold in our minds for those specific instances.
Only thing we weren’t super careful about was the first requirement for Mail/Wire fraud, which is “Mail and wires” were used.
It was amusing that the prosecutors brought in a bank IT guy to explain that “the internet uses wires”, but not really something we questioned.
I’m not suggesting granting additional protections to manufacturers, but codify an expectation of “if you abandon it, other people can come in and potentially salvage it”
I’m running several web apps, a git server, Plex, pihole, private CA, and keykloak, all on top of microk8s. It’s overkill, but I appreciated the opportunity to fiddle around and learn K8S without stress of external obligations.
I have two ingresses, one internal and one external facing. The external one is exposed via cloudflare and a micro vm (for multi level subdomains that cloudflare doesn’t support for free).
dyndns is handled by the router. It writes to a pseudorandom hostname, and cloudflare references it by CNAME.
It doesn’t get any significant amount of external traffic, but is good enough for family to use for the web apps + a yearly march madness pool (that can’t be hosted on yahoo/ESPN/etc due to a custom family rule set).
If reunification is determined to be impossible, the state goes to court to sever parental rights. This determination normally takes a year plus, and usually means the parents have checked out or are no longer trying to resolve the issues. Only once parental rights are severed is the child considered "legally free", and is eligible to be adopted into another family. In the ideal case, this is the family they were staying with before parental rights were severed, but not necessarily.
I haven't looked into the details of this article, but I assume these funds will be used for kids that have had parental rights severed, and were either adopted or "age out" of the foster care system.
Once in foster care, most kids are traumatized. Once parental rights are severed, it is incredibly difficult for parents to "re-adopt" their kid. I sure hope no parents are so short sighted to put their child through hell to reduce the cost of college.
* Before hunters were corner cutting, the land was more desirable and I could have sold it for $X
* With hunters now corner cutting, the land is less desirable, due to the hunting activity, and can only be sold for $Y
* $X - $Y = $7 million
- You don't have to maintain the infra yourself. It is maintained by system experts, vs the necessity to learn such knowledge yourself
- You are going to get features earlier, as Tailscale is the leading implementation, and Headscale is trying to maintain compatibility
- You have a promise of a certain level of support depending on your plan, rather than relying on an open source community with no responsibility to provide support
It feels like Tailscale isn't trying to gatekeep the technology, they are trying to sell all the things that simplify/provide value for people who would like to use the technology.
Before this morning, I would be in exactly your shoes in terms of "this is pretty cool, I'm going to keep using it"
This morning I tried to turn it on, and the car immediately veered left into the oncoming lane on a straight, 2 lane road. Fortunately, there were no other vehicles nearby.
I immediately turned it off in the settings, and have no intention of re-enabling.
Closest I can find is his concept of "First Order Retrievability"
I was on the jury of a federal fraud case, where the defendants took millions of dollars in customer funds and used it to make bad business decisions and/or placate earlier customers.
It was very clear to us that even though they lived a very simple life (old car, $1,500/month rented house), they wanted to build the biggest company in their industry, and fraudulently used their customer's funds to do it.
These exercises happen several times a year.
I'm not 100% sold, but I'm leaning that way, hence my phrasing of "While the technology is interesting and has some intriguing use cases".
I feel like the "good" use cases aren't particularly sexy however, and thus are in danger of getting lost. Additionally, there's a ton of people that want to throw "the blockchain" at a problem, and end up overcomplicating spaces that have no need for it.