HN user
You may be new here. This is Simon’s de facto benchmark for models. I happen to find it a really good one.
Small aside: It’s crazy to me that while it’s improved over time it does seem like most of the models haven’t been trained specifically to defeat this one.
I’ll never forget watching Gary Bernhardt give his talk on JavaScript.[0] Was my introduction to asm.js, and the rabbithole associated with compiling code to run in the browser.
12 years on, it’s shocking how much of his fiction became reality.
[0] https://www.destroyallsoftware.com/talks/the-birth-and-death...
People keep adding different slurs. Awful and disgraceful.
Relevant. Loro a lovely CRDT library, explored implementing VCS semantics with CRDTs.
Do you foresee this changing anytime soon? Would love to contribute but also I think community adoption and contribution would go along way in terms of businesses less worried about single points of failure.
It’s hard balance to strike for sure. And it’s getting weirder by the day with agents.
This is nuts. But give me some rope here, how much of react renders in Vello. Like is Vello taking the place of the shadow DOM here or is the entire DOM being render on a WASM thread somehow.
I have so many questions.
Just came here to say this is awesome to see more folks do novel stuff with XDP!
After reading loophole labs post [0] a few months ago. I was hoping someone would cook on this for security research.
Click the ⌘⌥1 on the top right of the terminal or enter it on the keyboard for some fun code golfing.
I’m now just curious about your project
I stand corrected on this front
Genuinely didn’t know it was hidden behind a beta flag. Ty for this!
Liquid Glass is now mandatory if you care about security. Sigh.
I wanted to like it too, but some of the new UI modals of iOS 26 are just awful.
Now do this in containers with gMSAs. It eliminates the need of passing around Admin creds. Which I cannot stress enough. You shouldn’t be throwing your DA credentials into your random Linux machine’s Kerberos cache.
Amazon open sourced a project trying to solve similar problems.
https://github.com/aws/credentials-fetcher
Nifty, but was clearly made with AWS assumptions and we had to roll our own with the various hooks we needed for our cloud infra.
UV and the crew at Astral really moved the Python packaging community forward.
I would love to see them compete with the likes of Conda and try to handle the Python C extension story.
But in the interim, I agree with everyone else who has already commented, Pixi which is partly built atop of UV’s solver is an even bigger deal and I think the longer term winner here.
Having a topologically complete package manager who can speak Conda and PyPi, is amazing.
I came here to say, this is exactly what I do also.
Unifi accidentally made a fantastic baby monitor.
The recent APIs they’ve built makes me hopeful that I could run an AI model against the footage eventually and build those Ai features for myself.
I really wish Mermaid would just ratify a layout spec. Make it optional. Use it. Great. Don’t use it. The layout engine does its thing.
For what it’s worth. I have noticed oddities like this where digitizer partial failure and data being unavailable even after unlocking the device.
Only thing that fixes it, is a hard reboot.
I wonder if that is related to this flaw.
Will DM after I’ve had a chance to dig.
Depends on the industry. But many large enterprises in the Fortune 500 are actively trying to move away from your traditional VPN. (F5, Pulse, Cisco, etc).
Even with VPNs the question should be, what are we gating behind that VPN anyway. Does it actually give us the granularity of controls we want or is this all security theater. (Also what about hybrid infra, between the datacenter and cloud)
FWIW, my ideal architecture is Wireguard into Corp. (Ala CloudFlare Warp, Tailscale, etc) Corp doesn’t hold a ton of sensitive assets. Or put another way, it’s a lower trust tier.
And then using something like Teleport, Octelium, etc to reach production assets.
Admittedly no vendor product I’ve come across yet has bridged this gap nicely. The überProxy tend to focus on the application protocols they support. While the wireguard clients cares more about session control of the tunnel.
Reading through the docs. I feel like a lot of people are missing the value here. This could be a diamond in the rough if it actually delivers on its docs.
What enterprises want is to move away from perimeter based security models towards the promise that Google überProxy/BeyondCorp popularized many years ago. Which has been lost in the buzzword soup. It’s very simple.
1. A clean separation between Prod, Corp, and the public internet. And the UX to hop between them as an employee is as transparent as possible. (Often times network segmentation comes with additional painful friction for engineerings.)
2. One pipe to observe, and clearly attenuate permissions as traffic/messages flows between these boundaries.
3. Strong proofing of identity for every client, as an inherit requirement.
The problem is everyone outside Google has incredibly diverse protocol ecosystems. It makes those three promises incredibly difficult to deliver on as a vendor. (I’ve evaluated many)
To build a proxy that is protocol aware, only solves half the problem. It gets you some coarse grain decision making and a good logging story.
To build a proxy that is also able to perform type-inference at the request layer, allows for a much richer authZ story. One where businesses can build an authorization layer at the proxy better than their in-house apps could even do natively. (As it turns out, having all the predicates of the request available to a policy engine is super useful).
The docs are a little verbose, the marketing maybe isn’t amazing. But this is inherently a complex problem. No one has fully solved.
Teleport was first to the market to OSS and commercialize a lot of these ideas. StrongDM also is doing really interesting work in this space. I wish Hashicorp had invested more in this space.
Disclaimer: my opinions are my own.
Very nice. You could throw this on a Spotify Car thing.
Would love to see this land on a Pi Zero 2 inside a husked out iPod classic and a skinable UI to boot.
@gvy_dvpont (@dupontgu ?), did this a few years ago back with a Pi Zero one, but I believe the project has suffered a bit from hardware compatibility decay.
3.1 - Car Thing was likely never going to be profitable but it was continued investment in that social contract. You can bring a Spotify UI everywhere. Even places where maybe it wasn’t needed or already served. But kept the mind share of its customer base. I used mine on my desk for example and was asked about it constantly.
Premium customer since 2013. Spotify would only give a refund in the form of Spotify Premium credits. And ironically canceled my subscription in the process of giving me the credit. SMH. Likely will GitHub Actions export my playlists and let the subscription expire.
I feel Spotify is really losing sight of its core competencies and its actual value proposition at this point. Will be interesting to see how this shakes out.
Spotify was amazing in recent years for 3 reasons: 1. Early pioneers in good ML based music taste making aided by teams of people who knew the various genres.
2. Spotify’s ability to do this well came from its strong investment in metadata which gave them a corpus of insight into what people listen to and why. Somewhat analogous to the rich tagging TikTok does to its videos on support of FYP.
3. The ubiquitous and continuous client support made it so easy to bring Spotify everywhere, that any alternative was going to mean more friction. In a way Spotify Connect is their iMessage blue bubbles moat. The ubiquitous and branded clients available on tons of hardware and every OS was their social contract. It was cool to use Spotify and not cool to be an Apple Music or Tidal user. The slow but continued atrophy of client support only builds distrust in this narrative. And that gap is closing when compared to other services.
If they had taken the opportunity to make it like an AirPort Express and included airplay and maybe chrome casting audio. It would replace my airport expresses in my UniFi stack immediately. I’d buy 3. But also the device limitation is brutal.
Came here to say +1. The fact that motorcyclists are including in this is absurd.
This resonates a lot. I really wanted to get on the Hugo train but I just couldn’t. I’ll probably give it another go someday.
For now it’s straight HTML,JS, and tailwinds for CSS.
Then I let Parcel do all the minifaction magic when shipping to GitHub pages.[1] Which is the only “magic” in this equation. I could pull it out if it ever broke.
I think this response lacks the context of the current state of the video game industry. In my mind this is no different than nVidia providing white glove engineering support and optimizations for titles to run on their GPUS.
There is a reason nVidia has generally won the consumer GPU arms race over the years over AMD. They go out of their way to support studios and titles, compared to what AMD does imho.
It shows that Apple recognizes it needs to lower the barrier of entry for studios to considering targeting Macs. Because compared to the larger gaming market most studios have very little incentive to build and maintain this because Mac’s could account for 1-3% of your player base. Is that worth 1-5 ICs worth of time if you are a small studio. Probably not.
This smells more like a result of staff reductions than anything else.
While not a guitar effects box another project that does low latency audio things with an RPI at it’s core: https://monome.org/docs/norns/
Open source version: https://monome.org/docs/norns/shield/
I believe the Olivetti Valentine famously on display at The Met and the MoMA at one point, were actually just retooled/modified Lettera 32s.
In any case, these little machines are brilliant and I’ve owned around 4 of them over the years.