<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>The Impact of Positional Encoding on Length Generalization in Transformers · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2305.19466/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2305.19466/feed.xml" rel="self" type="application/rss+xml" /><item><title>The Impact of Positional Encoding on Length Generalization in Transformers — mentioned by krackers</title><link>https://news.ycombinator.com/item?id=50083225</link><guid isPermaLink="false">urn:hackerpapers:mention:2305.19466:50083225</guid><pubDate>Wed, 14 Oct 2026 06:28:14 GMT</pubDate><description>&lt;p&gt;&amp;gt;drops the positional encodings after pretraining, I thought with NoPE schemes you don&amp;#x27;t even need it during pretraining https://arxiv.org/abs/2305.19466 https://sebastianraschka.com/llm-architecture-gallery/nope/ Given the causal mask and the way attention works LLMs can implicitly propagate a signal for ordering&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2305.19466/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>The Impact of Positional Encoding on Length Generalization in Transformers — mentioned by krackers</title><link>https://news.ycombinator.com/item?id=44730063</link><guid isPermaLink="false">urn:hackerpapers:mention:2305.19466:44730063</guid><pubDate>Wed, 30 Jul 2025 01:12:29 GMT</pubDate><description>&lt;p&gt;The paper showing that dropping positional encoding entirely is feasible is https://arxiv.org/pdf/2305.19466 . But I was misremembering as to its long context performance, Llama 4 does use NoPE but it&amp;#x27;s still interleaved with RoPE layers. Just an armchair commenter though, so I may well be wrong. My intuition for NoPE was that the presence of the causal mask provides enough of a signal to implicitly distinguish token position. If you imagine the flow of information in the transformer network, tokens later on in the sequence &amp;quot;absorb&amp;quot; information from the hidden states of previous tokens, so in…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2305.19466/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>The Impact of Positional Encoding on Length Generalization in Transformers — mentioned by spmurrayzzz</title><link>https://news.ycombinator.com/item?id=43598551</link><guid isPermaLink="false">urn:hackerpapers:mention:2305.19466:43598551</guid><pubDate>Sun, 06 Apr 2025 02:46:21 GMT</pubDate><description>&lt;p&gt;Not sure what you mean by summary paper, its a pretty dense topic that assumes a fair amount of prior knowledge of the fundamentals. But maybe the Meta blog post may suffice for that? Otherwise yes there are lots of papers on this and related topics, a few dozen in fact. But here are some notable ones, a couple of them are linked in their blog post. RoFormer: Enhanced Transformer with Rotary Position Embedding - https://arxiv.org/abs/2104.09864 Scaling Laws of RoPE-based Extrapolation - https://arxiv.org/abs/2310.05209 The Impact of Positional Encoding on Length Generalization in Transformers…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2305.19466/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>The Impact of Positional Encoding on Length Generalization in Transformers — mentioned by miven</title><link>https://news.ycombinator.com/item?id=43596239</link><guid isPermaLink="false">urn:hackerpapers:mention:2305.19466:43596239</guid><pubDate>Sat, 05 Apr 2025 19:38:52 GMT</pubDate><description>&lt;p&gt;According to [0] it&amp;#x27;s partly due to a key change they introduced in interleaving layers that use standard RoPE positional encodings and layers using what&amp;#x27;s called NoPE [1], not encoding positions at all and letting the model to figure those out on its own (this exclusively works because the LLMs are autoregressive, so the model can recognize an input token as being the very first by there not yet being any other tokens to attend to, and recursively deriving the position of the subsequent ones from that base case) [0] https://ai.meta.com/blog/llama-4-multimodal-intelligence/ [1]…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2305.19466/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>The Impact of Positional Encoding on Length Generalization in Transformers — HN submission</title><link>https://news.ycombinator.com/item?id=41283966</link><guid isPermaLink="false">urn:hackerpapers:submission:2305.19466:41283966</guid><pubDate>Sun, 18 Aug 2024 17:55:20 GMT</pubDate><description>&lt;p&gt;The Impact of Positional Encoding on Length Generalization in Transformers&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;2 points; 1 discussion reply on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2305.19466/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>The Impact of Positional Encoding on Length Generalization in Transformers — HN submission</title><link>https://news.ycombinator.com/item?id=36174120</link><guid isPermaLink="false">urn:hackerpapers:submission:2305.19466:36174120</guid><pubDate>Sat, 03 Jun 2023 05:58:48 GMT</pubDate><description>&lt;p&gt;The Impact of Positional Encoding on Length Generalization in Transformers&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;5 points; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2305.19466/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item></channel></rss>
