| |
| ▲ | seliopou 7 hours ago | parent | next [-] | | That link is broken for me but I assume you meant to link to [0]. I think if there is a “safeguard” in a system, that definitely fits the bill of a supply chain risk. The only vague term here is “adversary”. [0]: https://www.acquisition.gov/dfars/252.239-7018-supply-chain-.... | | |
| ▲ | bubblewand 7 hours ago | parent | next [-] | | Ugh, sorry for the broken link, I even pasted the same string into a new tab to make sure it worked because I thought the period at the end looked weird, and it was fine. Dunno how it got mangled. [EDIT] Oh man, yours is like that too? WTF. [EDIT2] If I follow your link, hit the 404 page, then add a period at the end of the URL, it does load. God that's strange. | | |
| ▲ | seliopou 7 hours ago | parent | next [-] | | Well, we ended up on the same page in any case, in at least one sense. | | |
| ▲ | bubblewand 7 hours ago | parent [-] | | Yes, we both accurately located and linked to the "page not found" page. That gave me a good, actual LOL, thanks for that one. |
| |
| ▲ | emmelaich 6 hours ago | parent | prev [-] | | Did you edit it to fix it? Is HN refusing to include the period as part of the URL? |
| |
| ▲ | layer8 6 hours ago | parent | prev [-] | | Working link: https://www.acquisition.gov/dfars/252.239-7018-supply-chain-... HN separates trailing dots from URLs, so that you can have working URLs at the end of a sentence. Hence you have to percent-encode trailing dots if they are a necessary part of the actual URL. (Same for some other punctuation characters, probably.) This behavior is common for auto-hyperlinking of URLs in running text, so it’s bad practice to have such URLs. |
| |
| ▲ | ASalazarMX 6 hours ago | parent | prev | next [-] | | Since the link is still broken, I tried encoding the final dot as %2E https://www.acquisition.gov/dfars/252.239-7018-supply-chain-... | |
| ▲ | 7 hours ago | parent | prev | next [-] | | [deleted] | |
| ▲ | x3n0ph3n3 7 hours ago | parent | prev [-] | | 404 |
|
