Re:Low Latency, Low Loss, and Scalable Throughput (L4S) Inte...
by Villodre on Monday December 11, 2023 @02:17AM
(#38598369)
An excellent answer - the very same kind of post I come here to read and not the very same machine-generated content that's everywhere in the Net ;-)
Re:Low Latency, Low Loss, and Scalable Throughput (L4S) Inte...
by MrBuddyCasino on Monday December 11, 2023 @02:26AM
(#38598406)
I think an AI summary, clearly marked as such, can be just as useful as the obligatory Archive link.
I understand the aversion against „AI spam“, but I find it weird that a supposed tech community rejects AI tech wholesale.
Re:Low Latency, Low Loss, and Scalable Throughput (L4S) Inte...
by valvar on Monday December 11, 2023 @02:32AM
(#38598425)
Nothing's stopping users who want an AI summary from feeding the content into their favourite GPT. But it's not contributing anything meaningful to a HN discussion.
Re:Low Latency, Low Loss, and Scalable Throughput (L4S) Inte...
by Closi on Monday December 11, 2023 @03:08AM
(#38598591)
Agree - possibly this is even an example of how to do it?
Clearly labelled as LLM generated and used to summarise a long RFC (where I personally didn’t find the abstract as clear as GPTs summary).
But everyone will have their own views on this. There is definitely a lot of anti-AI or anti-LLM scepticism or denial on HN.
Re:Low Latency, Low Loss, and Scalable Throughput (L4S) Inte...
by viraptor on Monday December 11, 2023 @02:50AM
(#38598510)
The archive link is useful, because it provides you a way to access the page itself. Nobody here has subscriptions to every single service, so if there's something paywalled, that link is useful to almost everyone person. (And I wish HN did it automatically) A lazy gpt summary is not that.
I personally agree with the downvotes - I don't want to see every HN post littered with "this is what GPT-4 has to say about this".