That’s crazy cheap, I pay close to 400€ (!!!) monthly for Tirzepatide (GLP-1) and close to 50€ for Lisdexamfetamine (ADHD) in Spain. Truth be told, the ADHD meds are covered by the Social Security health insurance or I’d be paying double that, but I don’t think GLP-1s will ever be covered here.
I keep working on Rigel.sh as a side project (a next-gen remote desktop solution with no latency and online-first for teams and hobbyists) but I wanted to write a Redis-compatible cache but using JS instead of Lua for scripting so I’m also working on that.
It doesn’t seem to be very good, but don’t worry, just keep prompting Claude and I’m sure you’ll get it sorted out.
Jokes aside, it’s cool but it’s not useful if it’s the first time I visit and I see I have 10+ past visits from all around the world… obviously this is not reliable and I wouldn’t use it for anything, much less anything serious.
Why actually try to understand a problem space? Far easier to prompt a turd into existence, polish it up with a cliché marketing page, and collect public validation from your fellow “hackers”
Thanks for checking it out! We’ve identified the root cause of the inaccurate visit counts you saw and have now fixed the issue — the accuracy of DevicePrint should be much better now. If you have any remaining odd results, let us know!
“Hey Claude, users are noticing my product is fundamentally broken. Please shuffle some code, increase the confidence label to 99.6%, and spam the HN thread claiming I identified the root cause of a bug. Frame it as a small edge case. Do not under any circumstances empirically validate the supposed fix.”
Snark aside, I still see 9 previous visits from various countries, down from 900+ previously. It does correctly identify me as being in incognito mode, but if I switch to a normal tab I see a completely different set of previous visits.
“It’s almost unbelievable that we entrust ourselves - squishy, sometimes hapless bags of water, meat, and bones - to navigate protocols of such profound complexity needed to safely take advantage of radioactive materials.”
Maybe it’s just me but I feel like that all the time, not specifically about radioactive stuff, but about other highly complex and regulated environments where a simple mistake can have catastrophic consequences. As an example, just look at how the aerospace industry operates, there are so many talented scientists and engineers working in every aspect and yet many incidents take place every year due to trivial human errors, from pilots misunderstanding something to technicians not tightening a bolt enough.
Of course it’s not like we can trust anything (anyone?) else other than other humans to do this stuff, but it blows my mind how easily we forget about it.
If you map out everything you have to do in a single day, and then work out all the things that you have to avoid for it to not go wrong, it's kind of terrifying.
Robot designers and toddler-minders will know some of these.
We're so used to so many failsafes that the "bare minimum to operate" for many things is frighteningly simple (very early electric wiring, for example).
I can’t believe the Bob CLI is just another fork of the Gemini CLI, no wonder Anthropic has the moat in agentic development CLIs, at least they are developing their own.
Looks cool but as others have said, it’s really hard to just try all similar projects because all of them promise the same thing but I haven’t seen any of them provide any benchmarks.
Claude Code keeps all the conversation logs stored on-disk right? Why not parse them asynchronously and then use hooks to enrich the context as the conversation goes? (I mean in the most broad and generic way, I guess we’d have to embed them, do some RAG… the whole thing)
Yep, parsing logs + async RAG works fine if you’re staying inside a single tool.
The issue we ran into when building agent systems was portability. Once you want multiple agents or models to share the same evolving context, each tool reconstructing its own memory from transcripts stops scaling.
We’re less focused on “making agents smarter” and more on avoiding fragmentation when context needs to move across agents, tools, or people — for example, using context created in Claude from Codex, or sharing specific parts of that context with a friend or a team.
That’s also why benchmarks are tricky here. The gains tend to show up as less duplication and less state drift rather than a single accuracy metric. What would constitute convincing proof in this space for you?
I’m slowly working on rigel.sh, a next generation Remote Desktop solution. Not AI related, but I got tired of janky desktop streaming / remote management solutions (I use the windows app on my Mac and Raspberry Pi Connect online) so I decided to build my own.
You install a client on the system you want to manage and enroll it with a single command, just like Tailscale. I’ve built a nice web application were users can manage and access their devices, setup monitoring and configure alerts (for now it only tracks basic stuff like CPU/RAM…)
The whole thing uses WebRTC for p2p connections and it’s very snappy because all the graphics pipeline is fully custom (all the enconding/decoding is platform-specific too) and I’ve managed to get latency and quality on par with Parsec in many scenarios (I still have some work to do here because it’s not my thing)
I plan on making the whole thing open source with a permissive license and also offer a paid SaaS early in 2026 (I think early February?). I plan on offering a hobby free tier and then paid business/pro features but time will tell!
I haven’t event built a landing page yet but if you are interested write me to ramon@rigel.sh
Hey thanks for the comment! Not sure about that right now, I plan on making a Show HN and maybe some content on Reddit and Product Hunt (I’ve built a startup before but in the B2B space and sales are very different)
Website: AI generated, slop
Comment replies: AI generated, also slop
“Fair point — that’s totally valid…” come on, are we supposed to just pretend this is an acceptable submission? I’m all in for vibe coding but at least be upfront about it and don’t waste other people’s time and energy.
reply