I wrote a tutorial about how you can import Strudel without embedding it. They publish JS modules so you can just import them and build an app around them: https://good.vibes.diy/blog/you-can-just-make-music
Since Fable, my legit infrastructure project has turned into the sort of thing I can do 95% on my phone. It’s reliable enough instead of doing big reviews, I’ve just been giving it smaller tasks, and dozens in parallel.
I created a skill that’s focused on getting PRs merge-ready, and now my attention is fully back where it should be, on deciding what changes will make the product better.
Our entire stack is Apache 2.0 open source, including the agent docs, so if you wanna try sitting at a higher level of abstraction, install the skill in your repo or just clone our whole project and start adding features: https://good.vibes.diy/blog/beast-mode-skill-for-claude-code
The only reasonable solution shape I've seen is the one that trusts the parents to set an operating system setting that says whether or not the user is allowed to access adult content. And so it doesn't actually verify age, it just verifies parental intent.
I would not be opposed to that solution. If that's what we can get passed, I'd be happy.
Personally, I'm more in favor of a version that integrates with a government issued digital id that attests a user can legally see the provided material. The publisher would have to implement the check, because my version also includes the technical capability to disregard the law. You then just have to be ready to be charged with a crime.
I think the reason I prefer this is that my country almost already has the infrastructure for this system.
Thanks for sharing your perspective. It’s reminding me of how I was feeling about crypto in the early days. I begin specifying a project on those lines way back when and the ideas behind it are still interesting. Maybe you’ll enjoy: https://www.wired.com/2014/07/document-coin/
Wow yeah, the wired description of it really rings a lot of bells in my head. I've got a lot of design work in a very similar direction.
Did you ever get a chance to turn it into something worth sharing? I'd be interested in an account along the lines of: "here are the decisions I made at the time, and now, with a decade of hindsight here's the ones I like and the ones I'd change if I were to try again."
One of the thing is we’ve seen at vibes.diy is that if you have a list of jobs and you have agents with specialized profiles and ask them to pick the best job for themselves that can change some of the behavior you described at the end of your post for the better.
Certain workflows prefer non-queueing, for instance the throng empowers the bartender to load balance different groups, delay drinks to over consumers, etc etc. So other cultures can have those workflows in places we might not expect, that is not necessarily a matter of respect. In pub culture, queueing disrespects the bartender.
It depends. Many places in the UK have a tradition of "virtual queuing" at bars; they don't stand in a line because that would usually block the space, but everyone remembers who was before them. Usually the barkeep remembers as well, but sometimes they ask "who's next" and people defer to those ahead. But load balancing also happens.
You're conflating efficiency norms with respect norms. Never mind that the core reason for no queues in bars is space efficiency and historical norms, allowing the bartender to select regulars, better paying customers, etc. without being stressed for time.
But in any case, your edge-cas applies when someone exists to manage the queue. That's not the case for e.g. elevators, self-checkout lanes, DMV lines, or, I'd argue, that vast majority of queues encountered regularly.
reply