More and more I find myself needing to reference old threads in Amp. To make it simpler, I added labels so you can have finer grain organization to your threads.
The icing on the cake: find_threads can use this as a search vector.
https://t.co/mS7hvDLdBR
@iamdavidhill Quite a bit actually. I think that I’m mot the only one working on the same project with worktrees and thread bursts to work a short lived sessions. And even with somewhat longer ones sometimes I want to check a previous session for similar or related tasks or threads to have ctx
@rekram11@thdxr I had to remove and reinstall opencode from the curl command to the bun approach and it just worked, seems that curl is not up to date with latest version?
@vanschneider As a local, my take is that it’s not a good move I would say. We even have “safe route back home programs for locals”. The city has deteriorated quite a bit. Although still a real cosmopolitan city and full of people and energy too, don’t know pros and cons 🤣
@shotgundotdev@dhh How is that screen? I’m eyeballing the 45” but not sure if I should pull the trigger… 98% working/productivity and coding and maybe 2% gaming from time to time
@jskalc@elixirlang I think that if users are expected to use LiveVue with forms is common to do so. I’m always up from removing friction from end users. Another possibility is ship a small mix/igniter task to install the protocol onto the user’s project.
@jskalc@danielbergholz@elixirphoenix Sure, i will try and see if I can prepare proposal for:
- Shared props
- Layouts & Persistent Layouts
Those and forms (ala Inertia) are my main pain points right now.
Let’s see if my kids leave me some time to work on this in the next few days 🙏😂
@jskalc@danielbergholz@elixirphoenix Would you also mind if I open discussion or something about shared props? Similar to what Inertia does? Instead of having to pass same props over and over (flash, etc)