One thing that can be handled much better today than back then was MIME / attachment types and having agents assemble "fancy" email structures irt.
One thing that can be handled much better today than back then was MIME / attachment types and having agents assemble "fancy" email structures irt.
I built this repo as a Helene response repo, trying to use an llm to help get resources over text message. https://github.com/realityinspector/supply_drop_ai
wonder if you could get to news over sms, use an llm to compress to minimum viable text?
- Components: https://hyperflask.dev/guides/components/ - Bundling view and controller in the same file: https://hyperflask.dev/guides/interactive-apps/
I think these may be footguns though. Components for example are just a regular macros under the hood. Why not use macros then?
I'm also curious about the choice of Flask. I started with a similar approach for /dev/push [1], but ended up moving to FastAPI + Jinja2 + Alpine.js + HTMX once I figured out FastAPI wasn't just for APIs. I wanted proper async support. I love Flask, but don't you find it limiting?
I made an announcement post here: https://hyperflask.dev/blog/2025/10/14/launch-annoncement/
I love to hear feedback!
one thing: the fish cursor on the site is frustrating pls allow disabling.