If the pros of having a camera are monumental, then couldn't the video and lidar be combined to be even greater?
356 karma · joined August 16, 2024
If the pros of having a camera are monumental, then couldn't the video and lidar be combined to be even greater?
It looks like its been found. The irony is, these model providers are now saying : "not like that!"
A prompt ran through a Wiggum loop over the course of a week/month and viola
Almost out of a Phillip K Dick novel
free, open source, MIT
Maybe the author left out something very real. Apple is a walled-garden monopoly with a locked-down ecosystem and even devices. They are also not alone in this. As far as innovation goes, these companies stifle innovation. Demanding more from these companies is not entitlement.
This could have come in any form, a platform as the author points out for instance.
I have a couple of ideas, how about a permissions kit? Something where before or during you sign off on permissions. Or how about locked down execution sandboxes specifically for agentic loops? Also - why is there not yet (or ever?) a model trained on their development code/forums/manuals/data?
Before OpenClaw, I could see the writing on the wall. The ai ecosystem is not congruent to Apple's walled garden. In many ways because they have turned their backs on those 'misfits' their early ad-copy praised.
This 'misfit' mentality is what I like so much about the OpenClaw community. It was visible from it's very beginning with the devil-may-care disregard for privacy and security.
This is a good call out. Ai really excels at making things which are coherent, but nonsensical. It's almost as if its a higher-order of Chomsky's "green ideas sleep furiously"
That’s a reasonable idea and something I considered. The issue is that AI assistance is often inline and mixed with human edits within a single commit (tab completion, partial rewrites, refactors). Treating AI as a separate Git author would require artificial commit boundaries or constant context switching. That quickly becomes tedious and produces noisy or misleading history, especially once commits are squashed.
> Why do we need a plugin or new tools to accomplish this?
There’s currently no friction‑less way to attribute AI‑assisted code, especially for non–turn‑based workflows like Copilot or Cursor completions. In those cases, human and machine edits are interleaved at the line level and collapse into a single author at commit time. Existing Git and blame tooling can’t express that distinction. This is an experiment to complement—not replace—existing contributor workflows.
PS: I asked for a resubmission and was encouraged to try again :)
- Local-first: all slicing and toolpath generation runs on your machine
- Works in any browser, even offline once loaded
YES!
I think a new type of open source is emerging centering around what is now possible in browsers. Browsers have a great track record when running legacy projects. Relying on a backend could be a liability for longevity.
I built opal editor myself, a local first open source free markdown editor with these same principles, https://github.com/rbbydotdev/opal
Plugins is a great idea. The ability to use existing obsidian plugins could be very powerful. Thank you for the idea!