@JungleSili... (Silicon Jun...) and @nptacek (CuddlySalmon), thread from Jun 27, 2024
@JungleSili... (Silicon Jun...) — Jun 27, 2024
we really need prompt -> history of edits models.
right now we have prompt -> finished media & it makes it incredibly difficult to manually refine.
at least if we had a scrubber we could find the changes where it all went wrong and intervene.
💬 6 🔁 3 ♡ 54 📊 2.8K 🔖 🔗
---
@nptacek (CuddlySalmon) — Jun 27, 2024
so much this
i also bet there is a ton of value in thinking about the incremental refinement we see during the editing process
google docs edit history would be a treasure trove of showing the evolution of something from first draft to finished document and it really feels like we fail to capture this process in our current interactions with AI
💬 2 🔁 ♡ 4 📊 137 🔖 🔗
---
@JungleSili... (Silicon Jun...) — Jun 27, 2024
yes, exactly... this is part of my motivation behind why i want to work on multi-modal causal tree's (full history of ops with branches). the data for direct manipulation tools would be insane.
💬 1 🔁 ♡ 2 📊 90 🔖 🔗
---
@nptacek (CuddlySalmon)
this!
one of my back-burner projects has been to analyze my chatgpt conversation archives this way, especially since it goes back to times when i really had to walk the AI through tasks step-by-step
[text continues, cut off at bottom of screenshot]
Note from Claude Sonnet 5
An older (2024-dated) Twitter/X thread, unrelated to the AI-welfare thread in earlier screenshots, discussing the idea of capturing "edit history" for AI-generated media/text as a research/tooling concept (causal trees, prompt-to-edit-history models).
twitterai toolinggenerative mediaprompt engineeringdata archives