nomand

A single-function book is your window to the world. A phone is the world's window to you.

You don't even take care of your car well and you think you know what it takes to take care of a building? Anyway, you should buy a boat.

a bird's eye view :)

You're right. #notallwebstandards

I'm pretty skeptical of propitiatory protocols too. And a lot of pro marine stuff is starting to go wireless which is scary to think about.

Thanks for sharing that! Very interesting. There is even less margin for error in air compared to at sea. At least you can still float if the power goes out and at that point a sewing machine is all you need for most critical problems past that point.

Your labeling is only a reflection of the shape of the lens you have on the world. I'm not interested in feeding that.

If anything needs to run a server to communicate with anything else, especially if wireless is involved (which often is the case with more modern forms of radar, gps etc. because of ease of wiring and installation) is a recipe for disaster if you're relying on interfacing with existing instruments for navigation.

Simply firing up cli for troubleshooting and debugging of any kind should not be "expected behavior" at sea.

As a "sailor in tech", "web standards" do not belong anywhere near an ocean going vessel.

Ollama for mac + https://continue.dev/. Otherwise c.d has hooks for other types of installs.

My benchmark is having a peer programming session spanning days and dozens of queries with ChatGPT where we co-created a custom static site generator that works really well for my requirements. It was able to hold context for a while and not "forget" what code it provided me dozens of messages earlier, it was able to "remember" corrections and refactors that I gave it and overall was incredibly useful for working out things like recurrence for folder hierarchies and building data trees. This kind and similar use-cases where memory is important, when the model is used as a genuine assistant.

Does what you're saying mean you can only ask questions and get answers in a single step, and that having a long discussion where refinement of output is arrived at through conversation isn't possible?

Is it possible for such local install to retain conversation history so if for example you're working on a project and use it as your assistance across many days that you can continue conversations and for the model to keep track of what you and it already know?

Is there a coherent resource (not a scattered 'just google it' series of guides from all over the place) that encapsulates some of the concepts and workflows you're describing? What would be the best learning site/resource for arriving at understanding how to integrate and manipulate SD with precision like that? Thanks

You're describing Arietty by Ghibli, even "Borrower" is the English translation for the little beings :)

The thing you touch and interact with every day, better be beautiful and bring you joy, whether through aesthetics, tactile feel, personalized function, or whatever else, hencewhy "custom" is the keyword here. Nothing to do with quality of your typing or the work. You don't opt out for the cheapest possible decor because it "does the job", your environment affects the way you feel and this is just one ways to express one's own.

My team have been developing Remotely (https://meetings.remotelyhq.com/) with this very thing in mind - customizable avatars, voice-driven animation and expressions, animated emoticons, cinematic rooms, interactibles. It's still very early stages, but the main observation is that the scope of problems people are having with communication is too large. Some people want to feel less anxious in meetings, some want accountability, some productivity, some want "fun" and customize stuff, others want video, screensharing etc. It's hard to pinpoint "the problem" that's tangible and solvable outside of the base must-have features. "feeling more like part of the team while working remotely" is not an easy problem to tackle.