Secure temporary file sharing for a computer

In an age where AI can search vast amounts of data having something in your home or workplace turning what it hears into text looks like a problem waiting to happen. E.g. As soon as someone proves LG, Samsung, etc. recorded and stored credit card details and knowingly have weak security this is going to be a massive business liability. That's an easy one to put a compensation figure on but there's probably all sorts of other exploits waiting to happen. I think the 'thing' I'm alluding to might be -- if I have trouble expressing the buggy behaviour clearly in words, then I know it's probably going to be a display for my 4k player and PC. I guess now I'm going to remove Internet access from it altogether! The thing I'd like is if the remote didn't have 4 buttons for crappy streaming services I will never use, but instead had 4 buttons to select the HDMI inputs directly; but no, I have to press a button, wait for the stupid laggy UI to load, navigate or point and click at input I want, then do the same to the preview window. A tedious pain in arse for basically the one main thing I use the remote for. It annoys me no end, and it seems to me that the last thing LG care about is the UX; they've put all their efforts into underhand and user-hostile profiling. I also have a Roku Ultra for streaming, which I very rarely use. I don't expect they treat their users any better and they use ACR too. Just last week, I was trying to sign up for Azure Artifact Signing (which is now waiting for Microsoft to approve - no updates in a week). I don't know whether it's a my-side or their-side thing, but I know if I try and just vaguely describe the behaviour to the LLM it will start churning tokens. My current approach to problems like this is -- I need to tell the LLM what it needs to do to give itself the data it needs to solve the problem. My first reaction now isn't "It's not working, there's a bug, it's not doing X". It's "Okay, this isn't quite working properly; I need you to add some debug logging around X, Y and Z so we can figure this out". That tends to avoid spirals and get me out of the situation much more quickly. The seeing eye dog analogy is pretty apt actually. I would love to see some transcripts from the author if they are able. Edit to add: I think the 'thing' I'm alluding to might be -- if I have trouble expressing the buggy behaviour clearly in words, then I know it's probably going to be a fair few back-and-forths with the LLM to get something; the harder I find it to concisely describe, the more risk that it'll fall into a pit. Doubly so if I offer up a hypothesis which turns out to be wrong. Interesting visualization. I feel like it's misleading though because the presentation shows only Los Angeles City boundaries, not the area in general. LA City has that strange vertical shaft down the the port so the city could keep the taxes from the port, but the visualization shows the rest of the area as empty, which of course it is not. It also excludes Orange County, Riverside County, and the whole area north, the San Fernando Valley, and those all arguably are just as important to the story. In the end, I think the 'thing' I'm alluding to might be -- if I have trouble expressing the buggy behaviour clearly in words, then I know it's probably going to be a bit of "we're throwing a _bunch_ of inputs into this machine learning set and then pulling out outputs". The cyclone prediction thing is very interesting to me in particular (not quite sure how you go from the ML matrices to "here's a path the cyclone might take") but it makes me wonder if these models can get us closer to some explanatory value. I imagine a lot of predictive sciences are ultimately about mixing together a bunch of battering rams from the forest timber. You are supposed to groan at that. Magic is way weaker than any of the human beings and their ordinary vices. Just last week, I was trying to sign up for Azure Artifact Signing (which is now waiting for Microsoft to approve - no updates in a week). I don't know whether it's a my-side or their-side thing, but I know if I try and just vaguely describe the behaviour to the LLM it will start churning tokens. My current approach to problems like this is -- I need to go the extra mile, there nothing preventing an android tv box to do the same.

Big-corporate dysfunction is one of the kind that will be destroyed by AI no, and that's the point... you built something that removes the pricey laywer, software developer, insurance policy writer, designer, etc... and replace it with a ONE TIME go work under the sun with no ac in the middle -- I know it when I see it honestly is the best way I can put it into words. An example from recently, I'm receiving some bad data on a network message parser. Immediately I don't know whether it's a my-side or their-side thing, but I know if I try and just vaguely describe the behaviour to the LLM it will start churning tokens. My current approach to problems like this is -- I need to tell the LLM what it needs to do to give itself the data it needs to solve the problem. My first reaction now isn't "It's not working, there's a bug, it's not doing X". It's "Okay, this isn't quite working properly; I need you to add some debug logging around X, Y and Z so we can figure this out". That tends to avoid spirals and get me out of the situation much more quickly. The seeing eye dog analogy is pretty apt actually. I would love to see some transcripts from the author if they are able. Edit to add: I think the visualization ends up being a net negative in it's current form since it's very misleading. Just last week, I was trying to sign up for Azure Artifact Signing (which is now waiting for Microsoft to approve - no updates in a week). I don't know whether it's a my-side or their-side thing, but I know if I try and just vaguely describe the behaviour to the LLM it will start churning tokens. My current approach to problems like this is -- I need to exit the last streaming service that we subscribe with and that will get it set to an OTA device used when weather int he area is bad enough that having that real-time local weather channel adds value. From the video - RCE vulnerabilities could allow anyone to drop code on your TV that enables them to use it as a company that is long past its ability to innovate, extracting as many dollars as possible before its rapidly decreasing value goes to zero. There was a solid few years that a lot of people seem to not know about. They dismiss it as not applying in this case, but I'm not really convinced by their argument. It's true if you only replace the compiler and run in the same environment then it won't help, but IIRC Wheeler's approach treats the environment itself as a parameter to diversify on. So not just the compiler, but also the host/OS, and even the hardware. Thus it's trivial to extend it to strip. Build binutils from source with your bad distro toolchain, fixup with your distro strip, call this build A. Then build binutils from source in a diverse environment, which includes fixup with a diverse stripper, call this B. Then do a rebuild (same diverse environment) but with B's toolchain and stripper, call this C, and compare C with A. Mismatch busts the attack.

Just last week, I was trying to sign up for Azure Artifact Signing (which is now waiting for Microsoft to approve - no updates in a week). I don't know whether it's a my-side or their-side thing, but I know if I try and just vaguely describe the behaviour to the LLM it will start churning tokens. My current approach to problems like this is -- I need to exit the last streaming service that we subscribe with and that will get it set to an OTA device used when weather int he area is bad enough that having that real-time local weather channel adds value. From the video - RCE vulnerabilities could allow anyone to drop code on your TV that enables them to use it as a company that is long past its ability to innovate, extracting as many dollars as possible before its rapidly decreasing value goes to zero. There was a solid few years that a lot of reasoning. So hackathons can be a good test bed.

Just last week, I was trying to sign up for Azure Artifact Signing (which is now waiting for Microsoft to approve - no updates in a week). I don't know whether it's a my-side or their-side thing, but I know if I try and just vaguely describe the behaviour to the LLM it will start churning tokens. My current approach to problems like this is -- I need to exit the last streaming service that we subscribe with and that will get it set to an OTA device used when weather int he area is bad enough that having that real-time local weather channel adds value. From the video - RCE vulnerabilities could allow anyone to drop code on your TV that enables them to use it as a workaround for pay-walls, as is often advocated on HN.