Agreed that the homepage should not indicate otherwise, but on the plus side with a tool like Bento you can edit the HTML file locally, remove the script tag at the bottom that does that, and never worry about that tracking again!
The docs aren't very polished yet but it's quite usable!
It bundles a JSX transpiler, a code editor, and supports saving to a file or localstorage. It supports "ejecting" to separate the shell (handling saving files, transpiling, editing, etc) from the JSX and the JSON data.
I also threw together an iOS app in which you can save these mini apps, allowing for longer term saving of data and code edits without relying on localstorage alone, making the save/refresh loop seamless. It includes a sandbox, preventing any saved mini apps from making network calls, but allows the user to enable network usage on a per-app basis. I'd like to include more QoL features like a native editor, but haven't prioritized that yet.
I checked it out and it looks cool. It's a much more general platform than Bento. If you can make it do presentations, I'm sure the actual quality of the output would be better than Bento as it's React as compared to reveal.js.
> as simple as installing Claude in the VM and connecting via an SSH terminal
I've done exactly this, and it works pretty well!
1. I setup a VM in UTM (but this could be any kind of containerization thing). I don't even bother with a non-root account in there (the agent has free rein to install packages, write files, etc).
2. I SSH into the container.
3. I install Claude or whatever there.
4. I setup git things in a way where I can push/pull to move code between the container and my host machine.
Upsides: the agent is isolated from the rest of my host system, only being able to read/write what I've explicitly handed to it.
Downsides: the agent is isolated from the rest of my host system, so it's more limited in capability.
For context, my engineering team is fairly small – no guarantees this scales well for larger organizations. I capture the reasons for decisions on why code was written a particular way or why a particular architecture was decided upon in commit messages. We follow a squash-and-rebase flow for commits, so each PR is ultimately a single commit before merging. During that squash process, I'll update the commit message to sometimes be a few paragraphs long. Later when I'm curious why we made decision in the past, I can use git blame to navigate back until the point where I can find the answer.
I’d love to see a variation on the concept that minimizes information on each card. It would of course result in a larger deck, but would reduce visual noise while playing games.
I think one colored suit symbol and one rank is the most needed. Some cards could have symbols like Uno’s “skip” card as their rank.
I also do my best to stick to a "one strike and they're out" personal policy.
But I also have apps that push marketing through notifications _and_ are urgent on a reoccurring basis (usually delivery or rideshare apps). For those, I'd love if there was a system notification setting (per app) for "allow notifications from this all for the next X hours" _and_ a simple UX to make that happen.
How did you decide which colors/sizes to offer this time around? Seems like a reasonable mix, but I also wondered if regular gold could have broader appeal. Perhaps it wouldn't help though, since you'd have to make different SKUs based on band width, assuming women would get the narrower one and men would get the wider one?
I personally prefer leaving the measurement in the instructions for two reasons.
1. I'll often use the ingredients list (and quantities there) before cooking to ensure that I have everything I need ahead of time. Depending on what ingredient it is, I might not mise en place it. In those cases, a step that says "add ingredient" would require me to go reference the list in the beginning, losing a bit of context.
2. It's not often, but I've followed a few recipes that require a particular ingredient in 2 different steps in different amounts.
recipes that don't separate their ingredients into steps like crust/filling/icing when using common ingredients like butter are just poorly written recipes.
I've started building a similar app before, except with more of a focus on the timestamps than the text (prioritizing time tracking over note taking). I ended up switching gears to different side projects and never came back to this one.
That being said, a feature I'd begun to implement that you could consider adding is what I called Context Tags. It looks like in Notetime tags are applied to notes to provide better organization. Context tags in contrast would be applied to timestamped lines within the note. When moving to the next line, the new one would default to having the same context tags.
That's it! That's the whole feature. This let's a user tag the first line in a category, such as "work" or "project A", then gain that categorization for any subsequent lines (until the user specified a new category).
that's an interesting approach
this implies that the context can change from one subject to the other within a single note? is that a useful use-case to you?
Genuinely, I'd love to see this approach be taken: allow for a set of characters to be used as list delimiters. I personally like the set to be comma, semicolon, and newline, but of course this set would need to be varied depending on other syntax (e.g. in SQL, we wouldn't want semicolon to be used for this).
Having newline be a valid list separator is particularly nice because it solves the "trailing comma" and "comma-first" style workarounds in a visually elegant way. The newline already provides a visual separator; we can already tell that we're at the end of most lists by way of having another keyword appear next without needing to rely on a lack of commas, for example:
Agreed that the homepage should not indicate otherwise, but on the plus side with a tool like Bento you can edit the HTML file locally, remove the script tag at the bottom that does that, and never worry about that tracking again!