The highest priority in U.S. government acquisitions is to respect the business "rights" of suppliers and potential suppliers. It's hard to understand how tightly this is wound into the very foundations of USG acquisition until you've seen the inside of the process. There are a lot of pragmatic things the government ought to be able to do to best represent the public's interests, but the corporate supplier base's business interests almost always trump the public's interests. The exceptions are when acquisition officials buck the system, lay out expectations for technical data up-front, negotiate hard, and are willing to risk the supplier walking away.
The deference to corporate interests is deeply entrenched in how the U.S. government works. In my opinion and experience, it is also why the U.S. government fails so badly at so many things it does.
Imagine you are the end-user of the thing being acquired (e.g., a military service). You know the acquisition is system is slow, ponderous, and subject to a lot of high-level interference. You care less about the public's long-term interests than about getting the thing, especially when there's a strong risk you may never get the thing due to acquisition system failures. When you feel that sense of desperation, you let the acquisition process give away a lot to the supplier if it substantially improves the likelihood you get the thing, or the (real or perceived) timelines to get the thing.
Feels like it is a “supply chain risk” using the same logic Anthropic was labeled such. (Note I do not think any should be a supply chain risk, but if they were being consistent)
A home network has neither of those, you're running a nerd network. You can set up an mDNS relay, and those devices can use other methods to register their addresses & get DNS updated (DHCPv6, DDNS, random cloud services, etc.).
What I don't understand is why a bot/scraper needs to load every page and image multiple times in the same hour or whatever session it's doing on my site. If I have say 10 pages and 100 images, surely 110 requests should be all it needs to load everything.
That's a weird take. There are plenty of professional use cases like quickly putting together a few short clips for social media shorts or whatever, that does not require anywhere near feature-parity with the big NLEs.
I had not used either before reading this thread, but omniclip has an odd interface, it's very unfamiliar to me compared to a standard NLE, and the loading time was quite long (maybe just HN load?).
reply