179 karma · joined July 8, 2025
I'm not sure I'm sold on this argument considering the docker image for GH Actions is made by "myoung34" and half the actions are community written, have terrible documentation and feel like abandonware too.
Once we got the email that they were going to charge for self-hosted runners that was the final nail in the coffin for us. They walked it back but we've lost faith entirely in the platform and vision.
I'm at a much smaller outfit now so we have more freedom but I'd dread to think the arguments I would've had at the 4000+ employee companies I was at before.
PipeDream is a CLI utility that wraps the stdout of terminal games (like Frotz/Zork or Colossal Cave) and generates visualisations using the Gemini API.
The early version just generated isolated images, which felt disjointed. I built a state-aware navigator and an AI director that attempts to solve this by mapping out physical paths and cardinal directions. When you use the new --img2img flag, PipeDream uses the previous scene as a structural guide. If you walk North, the new room maintains the lighting, style, and architectural geometry of the previous room. It makes exploring feel a bit more cohesive than a slideshow.
I also added aggressive smart-caching. If you backtrack to a previously visited room, it bypasses the LLM entirely and loads the cached state, which keeps API costs down per session.
To try the built-in demo (API key required, free tier works fine): pip install pipedream-fiction export GEMINI_API_KEY=YOUR_GEMINI_API_KEY pipedream-gui --img2img
If you want to try it with a real game, you can install Colossal Cave via uv tool install adventure and run pipedream-gui --img2img adventure.
You can find more examples of usage on the repo: [github.com/cpritch/pipedream]
I recommend running it with the --img2img flag enabled. It costs slightly more per generation, but the visual consistency is entirely worth it. I’d love to hear your thoughts, feedback or suggestions.
It uses a state-machine so the visuals stay somewhat consistent as you traverse. It's fully playable now but not validated against many games. It generally costs in the cents/pennies per session thanks to caching.
To try the built-in demo:
`pip install pipedream-fiction`
`export GEMINI_API_KEY=...`
`pipedream-gui`
Let me know what you think
BSL/BUSL seems like a good fit for licensing here. It's technically source available instead of open source but just adds the layer that a competitor can't be built using your core. Otherwise the core is free to modify and fork. AGPL might be an option but I fear it would scare off a lot of companies in the space who have policies against AGPL licensed code but you'd get to keep advertising as OSS.
Usually management backs off if they have a good understanding of the impact a change will make. I can only give a good estimate of impact if I have a solid grip on the current scope of work and deadlines. I've found management to be super reasonable when they actually understand the cost of a feature change.
When there's clear communication and management decides a change is important to the product then great, we have a clear timeline of scope drift and we can review if our team's ever pulled up on delays.
Competitors typically have to snapshot/aggregate because their graphing libraries are heavily CPU bound. Being able visualise level 2/3 data without downsampling is a big win. Also being able to smoothly roll back through the last 12hrs of tick-level history would be really neat too.
I'd say the bare minimum feature set outside of that is going to be:
- Non linear X axis for gaps/sessions
- Crosshairs that snap to OHLC data
- Logarithmic scales, Candlesticks, Heikin-Ashi, and Volume profiles
- Getting the 'feel' nice so that you can quickly scale and drag (people are real sticklers for the feel of these tools)
- Solid callbacks for events for exchange integration, people hate leaving their charts to place an order eg (onOrderModify etc)
- Provide a nice websocket data ingestion pipeline
- Provide an api so devs can integrate their own indicators, some sort of 'layers' API or something.
Sorry if I can't be of more help as I'm just a hobbyist in this area!
Off the top of my head, look into Order Book Heatmaps, 3D Volatility Surfaces, Footprint Charts/Volatility deltas. Integrating drawing tools like Fibonacci Retracements, Gann Fans etc. It would make it very attractive to people willing to pay.
I think you might be confusing creation ex nihilo with combinatorial synthesis which LLMs excel at. The proposed scenario is a fantastic testcase for exactly this. This doesn't cover verification of course but that's not the question here. The question is wether an already known valid postulate can be synthesized.
This took two seconds to make https://codesandbox.io/p/sandbox/5ry4rl
I do agree though that subgrid makes the HTML more readable though so I'm all for it.
Using this image - https://www.whimsicalwidgets.com/wp-content/uploads/2023/07/... and the prompt: "Generate a video demonstrating what will happen when a ball rolls down the top left ramp in this scene."
You'll see it struggles - https://streamable.com/5doxh2 , which is often the case with video gen. You have to describe carefully and orchestrate natural feeling motion and interactions.
You're welcome to try with any other models but I suspect very similar results.