Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ubP5j-000OH1-Ee for pgsql-www@arkaria.postgresql.org; Mon, 14 Jul 2025 19:43:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1ubP5h-00ChBl-72 for pgsql-www@arkaria.postgresql.org; Mon, 14 Jul 2025 19:43:57 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ubP5g-00ChBd-OW for pgsql-www@lists.postgresql.org; Mon, 14 Jul 2025 19:43:57 +0000 Received: from mail-pf1-x432.google.com ([2607:f8b0:4864:20::432]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1ubP5e-007Hs3-35 for pgsql-www@postgresql.org; Mon, 14 Jul 2025 19:43:55 +0000 Received: by mail-pf1-x432.google.com with SMTP id d2e1a72fcca58-748fe69a7baso3840641b3a.3 for ; Mon, 14 Jul 2025 12:43:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; t=1752522233; x=1753127033; darn=postgresql.org; h=user-agent:content-disposition:mime-version:message-id:subject:to :from:date:from:to:cc:subject:date:message-id:reply-to; bh=URWlC3+7zRwE9zcjMlQKY9Rib9bNVQoGkRycVWMWmFk=; b=AvVqSQbcQVmO2BnkbXSUBJjICDRYcZEbBxBm9y3J/UFZh4n1F8FvMZNdwxMVi/AlER bOIuspm4gSSSHNDk+NxhNo7SUfFvG+SXW6P+IVfQDxYlyeCLAIoJtabLpzGBvA1boMGk 1gwXx+pQGiDOBp8AUdF1f/hZUjGVlGEjaeH+M= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1752522233; x=1753127033; h=user-agent:content-disposition:mime-version:message-id:subject:to :from:date:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=URWlC3+7zRwE9zcjMlQKY9Rib9bNVQoGkRycVWMWmFk=; b=OHo7lwC3F5e/TRpJrdaceBBSHbjG7wu0eCpX1aHxAlZFJnLfjIaIWM4OgpipD/5rHL /lF2fSxToulpC5jZr3p+sE94MeZupQF1UnDvsrqqtJtdBA0bF87A+Zyb/gIUIsiBEVA2 Eg+AkRiAayUhsw1EQ1Q1l3y6lgPz6MXph3lGDr40AkCBNu43vXDyDa5C045lQGbvqrID zqhufbzeK5bwAg4ST7+s44ZQ9jV7+90Fhg/0qSYmP9+552VdLXPlvM+hcnvOriQStCrh m6j85Z45arCsBHbHKvTavAXxUmYjViyPjmdwl3HRtYxGbrn8XOwP6MINKBq1mkEIfjXf aoJA== X-Gm-Message-State: AOJu0YwCioVLHI+6OH1sDfj2YzX7LvLZZlmtxd6Ht2knYpW3D8ucqjo0 shg95fyrviWDkzOCp46DfMz7/S8CHI+ikPOGB+/HJDiuhQ6dTNCvRdhh/9oVzWDaJ4uCrJzLMIR QByo= X-Gm-Gg: ASbGncu1NBJWBqHptrbo3fK6aGAPPoNj4mQt1E7dlMy0LrqynAwOoKWZFSMRaPZkwdr 0X/n+n2JmfbqJz+IQ8P5xmJSG5LhqJHAR4EJ6iZmboo9fY4jaozF2JF7mkH+eyXkHInfYdeKADi ViQ1ib5CxV30O8vlvlQIu/DNiQcYYW4eUoCAIMgxEffV7LEpB0IC4AaD3uLGEjUqqMwoviUwwkR BhsIe9aHRzq32SeV6A1XLjILLwPcyUQTMRYoqy5qiks0cGwTPmBMWhOa6+/F9q5/PLflCj4vMIm uMp7kqpFvHxRSmjUZ6GUXzojZTyaYd3PujX0aFXVETDGVQwrJFrxd56h2RW/KEb7WaXZ0hHvM2g 6PVSFAWm3vPW1pYfdwPd9ctAuH7CiKWLrDWhF1oqHsyMOk0MQsgs= X-Google-Smtp-Source: AGHT+IEfpQJW1S3y69eN+kN0NPlrfveC8njG9w8Ck0q1bnL+3vF9L85yESyzZLVKVLjGXrek14OA7A== X-Received: by 2002:a05:6a20:7491:b0:21f:7430:148a with SMTP id adf61e73a8af0-231201fa1f9mr22679350637.28.1752522233210; Mon, 14 Jul 2025 12:43:53 -0700 (PDT) Received: from google.com (c-73-15-160-255.hsd1.ca.comcast.net. [73.15.160.255]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-74eb9f2251bsm11420054b3a.100.2025.07.14.12.43.52 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 14 Jul 2025 12:43:52 -0700 (PDT) Date: Mon, 14 Jul 2025 12:43:51 -0700 From: Noah Misch To: pgsql-www@postgresql.org Subject: List archives "Next" button new behavior Message-ID: <20250714194351.e9.nmisch@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/2.2.12 (2023-09-09) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk A few weeks ago, the "Next" button on pages like https://www.postgresql.org/list/pgsql-www/since/202507100000 changed behavior: Old behavior: "Next" would use the timestamp of the newest message as of when you last loaded the page. "Next" would take you to a page containing that timestamp and all newer-timestamp messages. For example, as I'm writing this, the newest message has timestamp 2025-07-10T14:03. "Next" used to take me to https://www.postgresql.org/list/pgsql-www/since/202507101403 and I'd then see the 14:03 message and later messages, if any. New behavior: As long as the latest message is from 2025-07-10, "Next" takes one to https://www.postgresql.org/list/pgsql-www/since/202507100000. Also, visiting https://www.postgresql.org/list/pgsql-www/since/202507101403 redirects to 202507100000 (zeroing the HH:MM from the request). (I'm simplifying; there are more behavior nuances if one starts at a date far enough in the past for messages to fill the page.) Does anyone have background on this change? I found no discussion of it. I liked the old behavior better, since it made the "Next" button convenient to see everything since I last caught up. That said, I'll adapt if the change is intentional and/or favored. Thanks, nm