SEJeff

I’d note that Xandem while a total flop commercially, does own patents on tomographic motion detection.

It’s a shame honestly, it was a really cool product.

Cool but lxd is still a competitor to docker. I’ve read the move code for some work reasons. No lxc, as you said :)

For folks interested in the current state of the art on sandboxing, here is a stab one of my former coworkers did:

https://github.com/firedancer-io/firedancer/blob/main/src/ut...

He researched chromeos process virtualization, moby (docker upstream), and chrome tab isolation. It’s all done ebpf magic on top of seccomp at its core.

docker and lxd are competing projects. Docker does not use lxd to launch containers. lxd was written by the lead dev (at canonical) of lxc which was not as polished as docker but sort of kind of did the same thing (ran better chroots)

They both use Linux kernel features such as control groups and namespaces. When put together this is referred to as a container but the kernel has zero concept of “a container”.

Systemd also has a newer feature named sysupdate which allows systemd to manage the host operating system. It has some really nice features around integrity and trusted boot.

https://man.archlinux.org/man/systemd-sysupdate.8.en

Here is a discussion about why they chose it for building an appliance like operating system for GNOME:

https://discourse.gnome.org/t/why-did-gnome-os-choose-system...

Alternatively, there is also bootable containers:

https://docs.fedoraproject.org/en-US/bootc/getting-started/

This reminds me of Singapore, where the national stockpile of sand is a literal state secret: https://www.harvarddesignmagazine.org/articles/built-on-sand...

These folks are trying to do what you are suggesting here:

https://www.nationalpopularvote.com

It is an interesting idea.

You’d genuinely be shocked how many hardcore tech folks own and run hobby or semi-commercial farms.

I run a biodiverse fruit orchard.

The point of this post is really to read the comments. It was amusing to see Rob Pike so dismissive of fuzzing when fuzzing finds a lot of issues humans miss.

The Drombeg stone circle is like stone henge’s grandfather.

First name checks out :)

I promised a coworker up north a bit in Meath that one day I’d come visit him and got that chance about seven years ago. Along the way we did the tourist in Dublin thing and part of it was the trinity long room and book of kells. Amusingly, a cabbie was asking me what I loved about Dublin and I said the history. He asked what in specific and I told him that there is probably chewing gum on the ground older than the founding of the United States. He got super offended and told me they clean the streets in Ireland, but then I mentioned the Aran Islands, Newgrange, and the Drombeg Stone Circle… What is “old” in Ireland is 3000-5000 years old. What is “old” in the USA is a few hundred years old at best.

Such a lovely place and people.

You will see a half dozen or so talks about firedancer and probably 35-40 or so of us total (I’m at the company that does security for firedancer, Asymmetric Research. We were founded by former jumpers).

You can make the determination on your own, but there will be an obvious large showing of firedancer folks and some exciting updates for the project.

Sure, and cpus supporting it will proliferate. Shockingly to no one reading hacker news... Both software and hardware continue to improve with time generally speaking. This was a huge software improvement on hardware that supports that functionality. It is a huge win for anyone wanting to use these algorithms where they can afford hardware that supports it.

We should celebrate Amazon's improvements and we should celebrate these improvements. Both are great for the future of technology, regardless of why they were initially developed. Improving tech and keeping it open source is good for all.

I didn’t use it because I didn’t find it relevant. They’re using hashing and EC algorithms and they’re improving them.

Rumors of Jump’s demise are greatly exaggerated. Check the torrent of firedancer talks at Solana Breakpoint literally next week and decide yourself.

Folks have said jump is gonna die for 20+ years. They’ve been around 30ish…

That team is full of world experts in high performance computing.

It’s a new from scratch implementation of a validator for Solana the fastest blockchain by several orders of magnitude. The slowest part is signature verification so they sped up hashing to improve performance of the entire system.

They follow a first principles approach (the lead has a few physics degrees) and opted to speed up the cryptography. The beauty of this, despite the bad views on blockchain, is that they freaking sped up the cryptography of commonly used algorithms more than anything open or closed source that I personally am aware of.

It’s a win in cryptography, much like this Amazon post is, except it’s slower than the firedancer implementation.

It’s an optimization in hashing algorithms that is around twice as fast as the ones Amazon is posting in thus article for the same eliptic curves.

If the Amazon improvements are hacker news worthy (they are) this seems reasonable contextually.

Also, I worked for Jump for almost 12 years :)

The firedancer team at one of the better HFT firms wrote an AVX512 optimized implementation of ed25519 and X25519 that’s significantly faster than OpenSSL.

https://github.com/firedancer-io/firedancer/pull/716

Ditto for sha256: https://github.com/firedancer-io/firedancer/pull/778

And sha512: https://github.com/firedancer-io/firedancer/pull/760

If you’re an optimization nerd, this codebase is wild.

Yeah, it makes for VERY confused builds when you select on cpu features available.

I love that you can simply type `orb` and get dropped into a Linux vm. Some of the cpu features are super weird (cat /proc/cpuinfo and it is unlike literally any x86 cpu I've seen before), but unless you happen to build stuff that depends on lots of specific cpu features like I do, it works well enough.

I suspected that they used Cellebrite for this three days ago:

https://x.com/SEJeff/status/1813079033430876433

As much as it makes folks reel, this is working as intended. If you don't want them to crack your phones, consider setting a 10+ digit alphanumeric passcode instead of a numeric PIN.

Also, do not enable the biometrics such as FaceID. I'm very much of this opinion[1] that biometrics are usernames, not passwords.

[1] https://blog.dustinkirkland.com/2013/10/fingerprints-are-use...

Let’s not forget syscall filtering. Using custom eBPF for what is in effect a syscall firewall is something my coworkers did for one of our clients and it’s really slick. It’s like super seccomp.

Clearly, if you care about security here, the best thing is to just use vim.

What other instances? That was the really obvious one during model 3 “production hell” as they scaled up production mostly on hopium assuming they’d sell.

It was a month, not a few hours, and I have no idea where you got the $200,000 number. That is certainly not what Elon himself said. He said 1 month.

https://x.com/elonmusk/status/1323640901248393217

Please do ask your AG center, but they’ll tell you they’re safe to eat. I make a jam of sorts with the berries. They’re not real sweet but are totally edible

Wireless sensors, synthetic aperatire radar, aerial surveillance all are things that exist. These things have existed since Vietnam and are significantly better now than they were then. The record for Lorawan sensor mad range was ~1,300 km / 830ish miles. You could partition the rainforest into grids and use these sorts of sensors if you wanted to be excessively thorough. Not easy or cheap, but very doable with today’s technology and a bit of customization.

Note: my grandfather invented some of the rf sensor technology designed to be airdropped by the US military over the forests of Vietnam for this exact thing. It worked well for what it was designed for.

Lookup beauty berries. Their fruit is edible and makes a nice jam. True to their name, they’re beautiful when fruiting.

How did you apply? For something fast growing / invasive like a Bradford pear, or a honeysuckle, you really need to get Glyphosate into the roots for it to die. I was taught this trick by an Arborist:

Cut the tree down and leave 4-6” above the ground. Take a small drill and put a 3/8” drill bit in it. Try to find the small hole in the very middle of the trunk and drill down into it. This is how the sap flows through the tree. Carefully spray 3-4 good sprays of Glyphosate into the hole with gloves and eye protection. The tree and gravity will take this down into the roots where they will die. The small amount of Glyophosate will stay in the roots for approximately eight years, and it won’t leak out into the soil as it’s held by them.