dang should change the title and/or merge this submission with the other one. [1] This is causing needless panic for a typosquatting-style "attack" unrelated to official Anthropic extensions.
329 karma · joined August 5, 2023
[1]: https://news.ycombinator.com/item?id=49322280
dang should change the title and/or merge this submission with the other one. [1] This is causing needless panic for a typosquatting-style "attack" unrelated to official Anthropic extensions.
.com wouldn't be covered by the proposal made in the post I replied to, because it isn't a ccTLD.
I also disagree with the post author's clarification in a sibling comment, saying that there should be a few major (US) CAs that can sign everything: As I originally understood it, the idea would really be to restrict signing of certs for ccTLD domains to CAs in the country in question, and only to those. There would not be a US CA that can sign certs for French domains and vice versa.
>most Rust projects (foo.rs) would probably not trust the Serbian CAs
Such domains are misuses of ccTLDs as originally envisioned anyway, and AFAIK the relevant standards bodies still see it that way, too.
>it seems possible that Chinese website owners might prefer to use non-Chinese CAs
For what reason? If it's a matter of resistance to government interference, it doesn't help, because ccTLD DNS records are ultimately under the control of that country's government anyway. It might make sense for very small countries in which operating a CA full-time isn't worth it for anyone; perhaps it should be possible for those to be grouped together, sure.
[1]: https://www.theinformation.com/newsletters/ai-agenda/anthrop...
Awfully optimistic. Why would they let you do that?
That's not what the GP said, they were referring to someone who "builds their own moat where they solely can profit and excludes others from the freedoms they themselves enjoyed".
I don't want to speak for them but I guess that LLM companies which release exclusively open weights models, or better yet, open weights plus training pipeline sources, would not fall into this category.
And these will be gone, too, a couple months later. Or possibly even at the same time.
Yes
>and do tools like Github and Confluence render them?
No
The preprint is interesting in that it predicts that on the way there, one can run into some kind of vicious cycle that leads to suboptimal outcomes even for the company owners. Navigating around this would certainly slow this process down, but I personally don't see it changing the ultimate outcome.
Where they went wrong, in my opinion, is in the implementation details.
It's mostly death by a thousand cuts: Requiring reputation to gain the ability to post comments, then having one's answers deleted as "this should've been a comment". Overeager marking of questions as duplicates, e.g. despite the equivalence between two situations being non-obvious (e.g. someone asks about data type A, and it turns out that it's a subtype of B for which an answer that applies to both exists; that should not be a duplicate, the fact that it's a subtype is the answer!). Endless other decisions like that, which wouldn't have taken any extra effort to implement correctly.
One feature they could've built that would have taken effort but also greatly helped against the common newbie complaint of "hostility" would've been a "newcomer track", which would've been more forum-like and guided them towards either formulating a good question or seeing that's it's already answered. In the latter case, some of the keywords that came up during this process should've been fed back into SEO so that future newbies would become more likely find the answer via a search engine despite using clumsy terms. I think they tried a simpler and worse version of this idea towards the end with "staging ground" but by then it was too late.
While this seems to be allowed because the current ToS don't seem to explicitly forbid it, I'd be surprised if this loophole stayed open for long... Why would they even distinguish between business and (much cheaper) individual plans if companies can work around it by telling employees to just pay for the latter themselves?
This one stood out to me:
>Machine-scale infrastructure. [...] Git itself wasn't designed for that load, and bolting AI onto platforms not built for agents is the biggest mistake of this era. [...] Git itself is being reengineered for machine scale.
Git itself is so far down the list of bottlenecks that do or could hamper LLM-driven development, even projecting years into the future...
On the other hand, LLMs seem perfect for triage and finding duplicates, so it's still surprising that they've let it get this bad.
Use Mypy in strict mode and run it in the post-turn hook of your LLM harness so the LLM has no choice but to obey it. And don't use overly general dictionary types when the keys are known at development time; use TypedDicts for annotations if you must use dicts at runtime.