davexunit

Do you know Abbott and Costello?

I think there are a number of people who mean well that aren't aware that they are creating the means for state control of computing.

Yeah I think the OP is being naive about the risk here.

I don't use passkeys but the thing that raised a red flag for me while reading the article that the OP is responding to is the "non-copyable" property. It's not possible to prohibit delegation[0], so the idea that a key can only be used on one specific device necessarily involves a form of DRM/wishful thinking.

[0] http://www.erights.org/elib/capability/delegations.html

> Indeed, just now I generated a passkey using free and open source software, and then I emailed it to a friend, and now we can both access the same website using that passkey. At no point did I have to ask anyone for permission, not the website, not the FIDO Alliance; not even my friend, who kindly let me monopolize her time without objection. What’s more, I don’t have to type any numbers by hand to use a passkey; I don’t have to remember any magic words; passkeys just work.

This (before they go on to describe actual passkeys) sounds like object capabilities to me. Capabilities combine designation and authorization so if you don't have it, you can't use it. It's the type of security that we should be moving to.

Passkey attestation sounds like a nightmare for user privacy and for anyone that doesn't use a major corporate operating system.

Are you saying that, aside from carrier grade NATs, dat otherwise achieves 100% direct connections?

There's a distinction to be made between p2p as a network topology and p2p as a redistribution of power and agency. It's true that relays are an unsatisfying fallback to deal with the networks we have, but they still allow for meaningful p2p in sociopolitical terms. Relays that support the spirit of p2p need to be federated, stateless, and end-to-end encrypted.

This article is slop "written" by Claude.

https://github.com/vivienhenz24/vivien/commits?author=vivien...

This reminds me of the Block Chat story from Habitat Chronicles.

https://habitat-chronicles.com/2007/03/the-untold-history-of...

I don't see how mTLS would work for Radicle or other decentralized systems because, as far as I understand, both parties need to have their certificates signed by a shared root.

Okay, I'm gonna go work on something good. Will return with questions.

Why would I read something you couldn't be bothered to write?

> Not slop, though.

What would you call 2k commits in 2 months by a single committer if not slop?

You're right to be suspicious: it's slop.

This appears to be vibecoded but not disclosed as such. 2k commits from a single author starting from June 1st with really long commit messages and source code comments. The GitHub org has 19 additional projects that are all recently created.

edit: Yup, found a very long blog post that says it's made with LLMs near the end https://yogthos.net/posts/2026-07-02-jolt.html

What are the best books/papers/blog posts to learn about Morphic's architecture? I'm not a user of any Smalltalk implementation but I'd like to learn more as the Smalltalk approach to UI is very interesting.

Can't have wind power. Can't have bike lanes. Can't have trains. Can't have healthcare. Love this country!

The moment I see anything LLM-generated it's an instant close tab.

Posts like this remind me how much JavaScript could benefit from something like Lisp's quasiquote. JSX is a terrible creation but templating in JS is pretty unpleasant without quotation operators. That said, I think Mithril's 'm' function did it the best of all libraries I have seen.

No it's not.

This project is 5 days old going by the commit history and seems to be entirely vibecoded.

I'm not sure what they mean by "native" here but (ref extern) is for host references, JS or otherwise. The i31 type is for "immediate" values, things that can fit in 31 bits and thus don't need to be allocated on the heap.

We're so close to a full circle moment. Next up is "npm stable", a curated set of packages (a "distribution", say) known to work well that are supported for a couple of years with security patches.

I sympathize with the developers. Mobile OS push notifications are a big impediment to the adoption of p2p technology and it's hard to do anything novel in the chat space because there's a million chat apps.

Hoot is also not a 2 day old vibecoded project.

Such a refreshing take after all the marketing nonsense from Bun. Zig is a glimmer of hope in a world of slop.

This was a nice little experience report. Most of the deficiencies in Hoot can be blamed on me.

> The error messages can be cryptic.

Apologies! Happy to receive issue reports about specific things that we can prioritize.

> It's even more incredible to know that it's running on a stack the team created themselves, not relying on Emscripten.

Building our own toolchain has proven again and again to have been the right choice. Emscripten would not have been useful for compiling Scheme to Wasm GC. Hoot is one of the few Scheme-to-Wasm implementations that takes advantage of the GC support (and the most mature of them all.)

> My initial understanding of Hoot was that it could compile any Guile program to the Web.

This is indeed the goal. However, that's a big compatibility surface area and we are not there yet. Help wanted! When we reach a critical mass of existing Guile code that "just works" then Hoot will be mature enough to become part of Guile itself as its official Wasm backend.

The OCapN group is actively working on a milestone for 1.0, the first interop target. It's getting close! https://github.com/ocapn/ocapn/milestone/2

I was wandering around the expo floor at PAX East last year when I noticed Earthion at the Limited Run demo arcade. I had a lot of fun playing it on the floor so I bought the full game on Steam. It's a quality shmup! For me the difficulty really spikes on stage 3 and that's where I got stuck, though I did make it to stage 4 once or twice. The initial release had some bullet visibility issues that were improved in subsequent updates. The default CRT filter is fun but I turned it off almost immediately for more visual clarity.

Sure am glad I moved everything off of Gitlab awhile ago. Trainwreck of a company.