Everyone is forgetting the no delay is per application and not a system configuration. Yep, old things will still be old and that’s ok. That new fangled packet farter will need to set no delay which is a default in many scenarios. This article reminds us it is a thing and especially true for home grown applications.
Burn out is the second or third year of non-stop fires and you are the one to solve all of the problems. Meanwhile the company is busy creating more fires because they haven’t finished burning that sweet sweet engineer candle.
Oh I doubt it was his fault. I had something similar happen setting up a phone for a neighbor. Apple decided it was fraudulent after I added her address to the account. It was now dead with no recourse. At least I didn’t spend much on a used phone. Picked up an android and said it’s time to adapt.
Yes, when my org needed a very specific feature from an open source project the company reached out to the authors. I don’t know the terms, but they dropped a chunk of cash. No strings either on the new feature and everyone benefited in the end.
Well you can get closer with custom build tools and tools to gut features. Ms is acutely aware of these third party efforts and they are working diligently to stop them from working in each release. They are not interested in making a prosumer release, but harvesting the customer. One of you is the matrix and the other is the human battery. I leave it to the reader to determine where they fall in those categories.
It’s intentionally obfuscated because the product developers don’t want to share profits with brokers. They also do not want to compete on in the open because that too lowers odors Otherwise, we would have a system where it would be insanely easy to monitor and alert for price breaks. Hidden cities is probably the best example of how it could work and easily presents the price charts over time. Yet they too were cut off from some providers.
Not to derail but there are issues with kernel patching. If it does work you start building a very large matrix of various levels of hot patches and then sometimes it just doesn’t.
If my company was worth a trillion dollars and an entire multi-billion dollar industry (cybersecurity) had grown because of my security inadequacies I would figure it out.
In fact, they already figured out hotpatching and will sell it to you for server 2025.
I just run my own name server. DNS blocking is no longer an issue unless they get to the root name servers. With a little domain warming from the top 5000 domains it’s pretty snappy most of the time.
More realistically, DNS blocking is no longer an issue unless "they" get to the registries for the top-level/second-level domains. It's easy to make yourself immune to things injected by the root content DNS servers, with at least two mechanisms for combatting this (the better one being just running your own private root content DNS server) having existed for most of this century.
Comcast wonderfully intercepts port 53 traffic and shunts it to their own servers.
I was getting an A record for sending I knew didn't exist. Spent quite a bit of time investigating until I just tried opening the site up in a browser. Then I saw their lovely as page. Thanks guys...
reply