6,687 karma · joined June 16, 2011
Personal site: https://michael.mior.ca
[ my public key: https://keybase.io/michaelmior; my proof: https://keybase.io/michaelmior/sigs/BpTU6skpVwr4X8MVODgsjjPXAPdaSLAjYbPl2EEDYeA ]
Verifying my Blockstack ID is secured with the address 19AvsK3Zo1cmFZg4D1c4pDaavHRZKvPEWm https://explorer.blockstack.org/address/19AvsK3Zo1cmFZg4D1c4pDaavHRZKvPEWm wonderfuldev_gceng9nu6y0g2kpciawxmwzc
I'd imagine someone more familiar with electronics possibly could have figured out what specific component was wrong and replaced only that for an even smaller fraction of the cost.
[0] https://useworkflow.dev/docs/deploying/world/postgres-world
There are a number of use cases for such a tool. One is for helping data analysts who are handed a pile of JSON documents to be able to more quickly and effectively craft analytics pipelines for heterogeneous data where just inspecting a few documents isn't sufficient. Another is to help automate API specification generation and regression testing. Definitely interested in any feedback.
[0] https://github.com/dataunitylab/jsonoid-discovery/ [1] https://michael.mior.ca/blog/llms-for-schema-augmentation/ [2] https://arxiv.org/abs/2407.03286
I don't see how either the HA instance or the Linux host can't be viewed as a hub. No hub required feels untrue to me. I assume this question is intended to clarify that some additional device is not necessary, but I think this could be reworded.
If Specific regenerates code from the spec each time (which I'm not sure it does), there's the potential for different code each time even for parts of the spec that haven't changed. This seems like a nightmare for maintainability and debugability.
(Caveat: Not an expert by any means, just someone who had a similar question and did some reading, so my answer may well be incomplete or not fully correct.)
I generally agree with you, but often the reason that these programs work economically is that those who don't choose to use them still contribute. There are (at least) three different categories: (1) caregivers who will care for their child themselves regardless of whether or not free care is available elsewhere, (2) caregivers who will find care elsewhere regardless of the cost, and (3) caregivers who will make use of free care if available, or otherwise, care for their child themselves.
I think the group (1) has a tendency to be higher income. It's certainly not true of everyone in that group, but I would wager that a significant number of people in that group do not need the financial assistance. Those people not using the free resource, but still contributing to funding it is what makes it economically viable.
Except it seems they only run on Mentra glasses. Not Meta Ray-Bans, Echo Frames, or any of the many other existing smart glasses platforms.
Humans can make mistakes too when compiling information and when mistakes are done unintentionally without the intent of causing harm, I believe liability is typically limited. I would expect the same would be true of LLM use. As long as the user of the LLM has taken reasonable precautions to ensure accuracy, I think liability probably should be limited in most cases. In the case of DeepWiki getting something wrong, I think the case for significant reputational damage is pretty weak.