[1] http://www.textfiles.com/bbs/BBSLISTS/internetinfo.txt

It worked out so well that I decided to get some more. Needless to say, it went from unavailable to being available for double the price. Now, I guess it won't be available at all in the future. :(

[1] https://www.worldradiohistory.com/Archive-Catalogs/Radio-Sha...

https://www.microsoft.com/en-us/p/windows-11-pro/dg7gmgf0d8h...

I learned that there are two ways of buying a Windows 11 license. One way results in getting a traditional license key that can be reliably transferred, and the other way (tying the license to your Microsoft account) risks losing your license. :( I'm very careful to only buy licenses the former way, now.

I don't think it would exactly be "create a fork of this repo", but if a developer invests significant time and effort solving hard problems where the solutions are implemented in the released source, once an LLM model is trained on it, then someone else could quickly and easily have the LLM generate a new program that implements the novel solutions. Whether this is a problem or not may depend on the motivations of the developer, but this potential for IP laundering may very well begin influencing the licenses and methods of distribution that people choose.

(Of course, I suppose at some point AI will be able to analyze and learn from binary executables or obfuscated source...)

I clearly had the wrong book for that computer. ;)

[1] https://www.retroprogrammez.fr/listings/aventure/cia/

Good luck!

You mention Netware, but as I recall the Netware function you describe was just "SEND" and "NET SEND" was a Microsoft networking thing. (But maybe there was some integration between the two after my experience with Netware, who knows.)

I mainly wanted to say, as someone who used/abused a Netware network in high school, I disassembled the SEND program and discovered that the username included in the message is not authenticated at all -- the IPX (or NETX, I forget which) software interrupt just took a string, and the SEND executable formatted the username into this string. So by crafting your own SEND program that used the software interrupt directly, you could easily forge any username you wanted. So you could very easily send a message from "ADMIN". :)

This should not be construed as a confession of any network shenanigans that may or may not have occurred at my high school. ;) :D :)

But since you asked what I optimize for... I'm cheap, and tend to opt for inexpensive, no-frills, but reliable 4K monitors. I have several Philips 278E 27-inch 4K monitors. I don't see these on Amazon any more, so maybe this model has been discontinued, but they ran about $250 USD or so. I use a couple on my main workstation for coding, my wife has a couple (that are secondary to an Apple Studio Display), and I have a floating one for the workbench. I find this model to be a sweet spot for my needs. They aren't as beautiful as an Apple display, but they're sufficient.

Potential cons include no camera (I have a separate camera on top, although it sometimes obscures some of the display due to narrow bezels), lousy speakers (I use headsets), and they seem oddly sensitive to electrical fields in the environment (for example, they'll turn off momentarily if I static shock myself on something nearby).

For example, my developer profile is slated for removal in a few weeks because I haven't provided a verified phone number and email address that can be publicly available for the world to see. (And I don't care to, since I haven't used this developer account in years, and I'm not actively doing Android development.) Does this mean I'll be barred for life?

I don't think all or most of these companies on the list are intentionally selling my address to spammers. I suspect most of these leaks are due to poor handling of the data or server compromises. (Surely Adobe, for example, isn't so desperate that they would sell my address to spammers.) But whether by malice or incompetence, I can easily block them.

It would be nice if my Docker image builds, which may include apt-get steps, could benefit from the cache. I know Docker build will cache layers itself, but this doesn't check the upstream for fresher packages in the same way that could be done with HTTP caching. I know I could simply set the Acquire::http::Proxy in the Dockerfile, but then I've mixed local infrastructure concerns into a Dockerfile that should be generically usable by anyone, anywhere. It would be great if there were some way to inject these site-specific configurations into the image without tampering with the Dockerfile. This could be tricky, since the base image of any random Docker image isn't even guaranteed to be Debian. (Although I could imagine a very generic Bourne shell script that consumes /etc/os-release, if present, and performs any distro-specific customization.) This would also solve the similar problem of needing to inject site-specific trusted enterprise CA certificates into images.

Another pain point is the lack of HTTPS caching, which the author mentions. I'm not sure that dropping down to plain HTTP is the solution. I sometimes wonder if there could be a MitM proxy approach, where the cache presents a certificate for the remote hostname that is trusted by a CA certificate installed on the client. (In other words, something similar to what a Zscaler does to intercept HTTPS.)

I think a part-time coding job would be fantastic, but such jobs don't seem to be abundant or stable. It's my experience that very few people need just a little software engineering. If someone needs software engineering at all, they usually need a lot of it. Also, the structure and management of most teams don't seem to be compatible with part-time work. Many companies aren't sure how to deal with someone who can't attend all the meetings.

That said, if you managed to do this for a decade, you likely have more experience with how to pull this off than the rest of us here. I'm not sure what may have changed since mid-2021, other than the general tech slump.