Very interesting writeup - the level of disclosure is interesting and appreciated.
The visualization is quite slop though. I was trying to follow along with the "Live Action Stream" but rendering issues mangle the text for a few of the list items (and does not scroll). Text on the node diagram is extremely tiny. I appreciate it even in it's current form, but a little attention to detail would have gone a long way here.
The visualization is absolute useless slop. A Text-Form timeline would have been way more useful. I couldn't hear having to scroll by hand for something that's just textual information.
Agreed! Also, from a UX perspective, I think it’s a weird choice to center the real-time nature of it. I think to a user the most important thing is just understanding the step by step process. Would have been nice to click through steps rather than making it all real-time.
Very fun! A few tips for others that I learned via struggle:
- Use Space to air dash, do it every time after releasing a swing to position yourself for the next swing
- Use WASD while swinging to steer away from your anchor point for a nicer swing curve
- Otherwise, use pointer to pick your anchor (holding space did not work well for me)
I have recently fully switched to a flip phone running AOSP.
After years of fiddling with OneSec and others this really has been the only solution that has worked for kicking my screen addition.
Best thing - with AI I can quickly build APKs for whatever I actually need! I build an app to give me turn by turn directions and (ironically) an app to talk to Claude w/ web search. I feel like I'm living in a world of truly personalized software.
I find the interface itself (number pad with t9, tiny screen) to be the most important part of dissuading compulsive use. Would highly recommend!
I got it for about $40 a year ago, but it looks a bit more expensive now ($90 on Amazon). It was a bit of a pain to root it, but I was able to follow some online guides - I've been meaning to publish a repo with exact steps. Let me know if you order! There are a couple similar phones that work well, the important thing is getting AOSP and not other firmware.
I'm looking at a number of options, mostly those recommended at /r/dumbphones on Reddit. There are the Lightphone II, Mudita Kompact, and Clicks Comm there.
Elsewhere: Punkt MP02, Kyocera Dura series, Cat B22 / S22, and a few of the Nokia / HMD phones, preferably flips.
Most are AOSP, HMD/Nokia are S30+. KaiOS also turns up (an AOSP variant).
What other firmware don't you recommend?
And what was your primary motivation? Just simplifying your phone, or security /privacy / other on top of that?
Hi! Sorry, not great at responding to hn comments, feel free to dm!
My primary motivation is helping my anxiety by strictly limiting my inputs in most life contexts (when I'm with friends, walking around) so that I can be more present. While having a device just in case of emergency or for the convenience of scheduling to meet up, etc.
My primary security is that only about 20 people have the number (people that I'm meeting up with, I'm not very stingy about it), and I don't get any OTP to the phone. I think this is more of a feature, it feels really nice to have a feeling of disconnection and privacy when I go out. I still use my old iphone and it's number via my mac.
I've had a good time with AOSP! From my very limited understanding, KaiOS could be a bit limiting? But honestly I don't know.
Curious if you try these other options! TBH for what I want, I think having a very low price (~$50 is ideal) is a huge feature because I feel like it gives me the permission to experiment without really worrying about it. Worst case I can brick it, order another, and swap the external SIM.
[Colma](https://www.colma.ai/) solo venture, working with my dad who has been in digital marketing for 30 years and has a small agency.
Takes any website, does deep research on who's searching, what your offers are, etc, and then makes a plan and recommendations to get you more visibility on Google, ChatGPT, etc.
These days, there's really no excuse for someone with a website to not be doing these things to get more visibility, and I've found generic LLM advice to be pretty bad. Contact if interested or curious! Currently in pilot stage with a few agencies and website builders.
I run a local print-only zine in SF called Lower Haight Local ! We print 1,000 copies a month with a local printer and have 20-30 neighbors contributing art or writing to each issue. We have a block party to distribute it each month.
I find that despite print no longer being the fastest place to get news, the physicality of it connects neighbors in a way online publications or social media cannot replicate. It’s pretty special - if you’re interested in getting your own zine off the ground or want to contribute, reach out!
I typed in the address of my childhood home, and breathed a sigh of relief when it showed a random home with solar panels and 'clean modern sustainable living' which my childhood home was not. Even added solar panels.
General design was correct, and it included the name of a town just nearby.
Not a surprising result, but made me reflect on what a weird world we now live in.
I quite like this! I've been incrementally building similar tooling for a project I've been working on, and I really appreciate the ideas here.
I think the key decision for someone implementing a flexible UI system like this is the required level of expressiveness. To me, the chief problem with having agents build custom html pages (as another comment suggested) is far too unconstrained. I've been working with a system of pre-registered blocks and callbacks that are very constrained. I quite like this as a middleground, though it may still be too dynamic for my use case. Will explore a bit more!
Thanks! Really interesting to hear you're working on something similar.
You're right that the level of expressiveness is the key design decision. There's a real spectrum:
- pre-registered blocks (safe, predictable)
- code execution with a component library (middle ground)
- full arbitrary code (maximum flexibility).
My approach can slide along that spectrum: you could constrain the agent to only use a specific set of pre-imported components rather than writing arbitrary JSX. The mount() primitive and data flow patterns still work the same way, you just limit what the LLM is allowed to render.
Would love to hear what you learn if you explore it!
Will do! I'm using a JSON DSL currently, I wonder if there's a best choice for format that is both at the correct level of expressiveness and also easy enough for the LLM to generate in a valid way. I do think markdown has advantage of being very trivial for LLMs, but my current JSON blocks strategy might be better for more complex data.... will play around.
Honestly this comment is the exact reason why this is such an interesting allegory - I didn't know Proton existed! And looking at it, it might be perfect for my use case. Appreciate the tip - will take a look!
The visualization is quite slop though. I was trying to follow along with the "Live Action Stream" but rendering issues mangle the text for a few of the list items (and does not scroll). Text on the node diagram is extremely tiny. I appreciate it even in it's current form, but a little attention to detail would have gone a long way here.