One of the reasons for the mysterious websocket close code=1006 reason="" error at the server end. Putting this here for search engines to find it in case anyone else hits it... Deployed a new service to a GCP compute node recently. Works perfectly in development, but the
Type any common business question, or even request to generate whole new original documents into ChatGPT and it will give you a linguistically plausible, well structured, and maybe even accurate and useful response. If you haven't played with it, you really should. Give it some questions from outside
Back when I made my first connection to the Internet, it was normal to ask for enough addresses to give a public IP to every computer in the organisation (and then some because they could only be allocated on classful octet boundaries). The organisation I worked for ended up with
Just about the only really good thing that came out of the pandemic for me was habitually going for walks with people to chat and exchange ideas rather than "going for a coffee" or "a beer" in crowded places. This works for me as I do
I hit an awkward problem that I've never hit before, last week. After a weekend at a hackathon with great Wifi, I checked back into my codebase to do a bit more work from the place I was staying and found all my cloud hosts were now rejecting