First hearing of tangled, tried signing up and this first time user experience needs to be tightened up. Currently unwilling to sign in because of the friction I ran into using a password manager. From what it looks like they:
- ask you for an email
- send you an email
- ask you for a username
- except you cant actually log in with this username directly
- im being forced to learn some new social url protocol
- why does the auth flow pass me through a new ui/url that seems owned by the project but visually disconnected (eg, different branding/colors for the form)
- my password manager couldnt bridge the gap
I'm notoriously fickle about dealing with signup/login friction, but the project sounds cool so hopefully my feedback is more actionable than curmudgeony.
Discovered data-star a little around that time, maybe a little after HTMX. I'll probably dabble with personal projects, but no stomach for the business to try something in that vein again. "Nobody ever got fired for picking ~SAP~ React" and all that.
HTMX is excellent. We made it a long way at Convictional[1] with HTMX + AlpineJS, but the eventual transition of our product into lots of live collaborative surfaces had us feeling like we had pushed the envelope as far as we could under modern startup constraints. Unfortunately, frontier models have really hurt development with budding tech that doesn't have the training data presence of things like React.
- I tried it on a repo that has very obvious boosting tells, like 99% of stars from week old or less accounts and it had higher trust signal than my own very much so real project. The issue to star ratio gave 5/5 despite the issues being core contributor created.
- In same vein as above, it seems to prefer open issues over closed ones in the scoring.
Have you considered scoring contributors/authors/issue creators separately to use as a proxy, instead of measuring the core things that are being gamed?
Hard to trust a project that is clearly github star boosting out the gate, consider that you're putting yourself at risk of account suspension for reports.
Ive been surprised at how effective (for personal projects) this type of rote promotion by link sharing can be. It feels fruitless initially but i guess whatever-engine-optimization keeps paying to be consistent.
awesome-lists like you see on github seem to be missing, which would be a good inclusion. Although I think many of those curators are suffering a wave of slop right now so maybe not.
Every task automatically gets git worktree isolation to support the parallel work. The VM sandboxing is project scoped and more about isolating agent workloads from user-space for those who want to --dangerously-skip-permissions for example.
No problem, I actually went through a similar path of trying milkdown/tiptap/a few others as the core for my own editor needs but kept running into into issues where the abstractions got in the way eventually. I was thinking about using ProseMirror for a custom 'one big text file' concept so I guess Ill close the door on that idea and give this a try.
Blood in my case, and it would probably be obvious. In general though I think a lot of these questions are answerable by paying attention to the changes in your body, how you're feeling, researching, and raising thoughts/concerns/etc with your primary cary provider when that comes up short. No need to go searching for issues if there isn't some leading indicator that sticks out to you as something to be curious about, or there isn't some related family medical history.
I recommend getting a colonoscopy if you have any symptoms. There is a lot of stigma that prevents people from being proactive about this type of issue.
My anecdote (M, 35) is that I got one after experiencing symptoms that turned out to be unrelated, but they did find pre-cancerous polyps so now I will be getting them more regularly. I received received meaningful early detection and peace of mind. Also aside from the prep, its a very convenient procedure. You get put under anesthesia and do a quick time travel.
Ha, it obviously picked up on the ouija board concept with the colors and copy. I think the detail expansion shown is a great illustration of another thing they tend to do - uncanny valley of 'sky is blue' type product descriptive copy that reminds me of dribbble shots or landing page template demos from a few years ago. Technically correct language that doesn't communicate much emotionally.
I've built/am building something similar, but I spent the first half of my tech career as a UI/UX designer before becoming a software engineer and I'd _like_ to think it shows, but there is something about designing-in-code with agents that leads to homogenous outputs if you don't spend equal time on visual design as on the technical parts.
This has unfortunately been going on for years at this point, for as long as there has been an OSS-to-profitability pipeline gamed for startups I'd guess. I wouldn't be surprised if it has progressed to fake contributors/discussions/issues/forks as well. Seems like an inevitable outcome for any platform with social signals.
I have a terminal manager project[0] I'm currently using xterm for, but very curious to try libghostty. Have mainly been hesitant because it hasn't been promoted from an internal ghostty dependency (only awareness of the place was from this article by the creator[1]), but from the sounds of it here people are finding it stable enough. Gonna give it a whirl today.