Wilduck
Joined 17 years ago
Karma
908
Submissions
340
Member since
Aug 5
theerikswanson [at] gmail
erik [at] mandarin-melon.com
View on Hacker NewsRecent submissions
Comment · 2 months ago
When did spacetimedb pivot from being a gamedev backend to being something for AI agents to use? Are they also trying to pivot to a IaaS model?
Comment · 2 months ago
Glad the feedback was helpful! Feel free to email me at either email in my profile. I think your next steps laid out here are good ideas. In particular, fully documenting (with video or text) a handful of actual successful uses of your site / the programs seems like a great next step.
Comment · 2 months ago
Your reply to this comment got flagged dead for some reason (not sure why, it seemed like a good faith comment) so I'm responding with a couple thoughts here.
Looking at your set of steps, I'm definitely getting lost around step 3 "The program then guides you one step at a time. Each step is a small module: a short assessment (a few structured questions), a task, a referral, a verification, and so on. It adapts to your answers rather than dumping a wall of text." Am I wrong that this flow is not built yet? Or is completely inaccessible to me?
Like, looking at the program page https://dohmh.codify.nyc/program/71776 I don't see how I can follow any of the steps. You say this is drawn from DOHMH pages, so I found the corresponding one for this program: https://www.nyc.gov/site/doh/health/health-topics/stay-healt.... I think this page is miles better than what you've built for a few reasons:
1. It comes with context in the form of paragraphs of explanation 2. It doesn't use undefined words like "program", "agent", "target". No where on that page is a string like "PersonalPrepTaskAgent". 3. It provides links to more resources, also written in nice human readable language
I don't want to be too hard on your project though. I've had to interact with the Pennsylvania DMV website a number of times, and trying to understand how to meet the requirements for a residential parking permit when I moved into my house was crazy because I needed some non-standard documentation due to having out-of-state plates. I would have loved a someone to break down the steps to me in very clear, understandable language. But I'm not sure your site is doing that right now.
As a last note, I wouldn't say you're "spamming" the comments, but I might recommend reaching out to potential users directly and asking them for harsh feedback. Posting into the void here clearly isn't getting you enough actionable feedback.
Comment · 2 months ago
My man, you're posting this project all over the HN comments, but I think you need to step back and really think about what you're building and what the user experience is.
Your link to an example protocol: https://dohmh.codify.nyc/protocol/71776 makes basically zero sense to me. Similarly the program page. What do you expect someone clicking on these links to take away from them?
Comment · 4 months ago
It's because the author is comparing that incident to how they were prepared with the bulk of their analysis in advance. Ready to publish as soon as it happened.
Comment · 4 months ago
The downvotes are because the discussion isn't really about "which option do users prefer". It's actually about returning user choice. As the original comment said: "If I want a separate tab, I can Cmd+click and Browsers don't have the reverse option for opening in the same window."
So when you say "Nope!", you're being downvoted because you're implicitly saying "actually users don't deserve choice".
Comment · 4 months ago
You don't, you just cheese the level by slamming into the wall just to the left at the start and skip most of the course.
Comment · 5 months ago
This is one of a bunch of issues that have been popping up since a vibe coder took over the bulk of development on this project. There's a (probably also AI generated) list of a big portion of the issues here: https://github.com/benbjohnson/litestream/issues/1221. That proposal has been open for a few months, and it seems (from my POV) unlikely to be resolved any time soon.
Comment · 5 months ago
I've been following litestream for a while, and it seems like the project has been hijacked by a vibe coder. I wouldn't trust it for critical tasks anymore.
Comment · 7 months ago
Thanks for the kind words! I hadn't heard of tatoeba before, so thanks for sharing that as well.
Comment · 1 year ago
Is that a "hard problem" though? Really?
Comment · 1 year ago
Personally, as a DM of casual games with friends, 90% of the fun for me is the act of communal storytelling. That fun is that both me and my players come to the table with their own ideas for their character and the world, and we all flesh out the story at the table.
If I found out a player had come to the table with an LLM generated character, I would feel a pretty big betrayal of trust. It doesn't matter to me how "good" or "polished" their ideas are, what matters is that they are their own.
Similarly, I would be betraying my players by using an LLM to generate content for our shared game. I'm not just an officiant of rules, I'm participating in shared storytelling.
I'm sure there are people who play DnD for reasons other than storytelling, and I'm totally fine with that. But for storytelling in particular, I think LLM content is a terrible idea.
Comment · 1 year ago
Really cool project. A quick note, I had to dig in your FAQ to find your definition for LOQ:
> "What does 'LOQ' mean in your results? > > Limit of Quantification (LOQ) is the lowest concentration we can reliably measure. Results below LOQ are marked "<LOQ" - this doesn't mean zero, just below our measurement threshold."
IMO this definition should be on every results page, since most of the pages have more LOQs than anything else.
Comment · 1 year ago
Viewport size and deciding where to paginate makes a naive approach to this surprisingly difficult. That being said, if you can control the css / html, you can often solve these problems with a short media query and some hints at where to break pages (e.g. https://developer.mozilla.org/en-US/docs/Web/CSS/break-after).