Re: [Tools-discuss] another case of links not updating

Paul Wouters <paul@nohats.ca> Thu, 07 May 2020 03:36 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B31EA3A076C for <tools-discuss@ietfa.amsl.com>; Wed, 6 May 2020 20:36:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ctwVO-rD8cTN for <tools-discuss@ietfa.amsl.com>; Wed, 6 May 2020 20:36:24 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7AB203A0763 for <tools-discuss@ietf.org>; Wed, 6 May 2020 20:36:24 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 49HfJQ4fGLz3Bh; Thu, 7 May 2020 05:36:22 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1588822582; bh=GN4Q04g+MlIfQFgXJB8/vljdZfoMGxnacCCWHwwczng=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=W7A2TJaDO16mCPppidvCEsf9VDxd1MbwKcmty5EpWxt/5U3D++WvF4iKmlDY/otIr XaO+FKA/dSdHSQjprtzOIa3mHU6JSNNlKHNuvlqMiUEGEHTftQTLqizuDEUWHpwXBB O1njM7l5qNCUd3wZBiXUOvt/zC52PPKIQVHn6smM=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id FFDtZnbyE4ag; Thu, 7 May 2020 05:36:21 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Thu, 7 May 2020 05:36:21 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id A6BAE6020D9F; Wed, 6 May 2020 23:36:20 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id A591F66B7C; Wed, 6 May 2020 23:36:20 -0400 (EDT)
Date: Wed, 6 May 2020 23:36:20 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: Robert Sparks <rjsparks@nostrum.com>
cc: Henrik Levkowetz <henrik@levkowetz.com>, tools-discuss@ietf.org
In-Reply-To: <ae0875b4-13b6-387a-df7a-f157e39c1992@nostrum.com>
Message-ID: <alpine.LRH.2.21.2005062331440.536@bofh.nohats.ca>
References: <alpine.LRH.2.21.2005061024040.16512@bofh.nohats.ca> <d538a7da-8e90-cf26-3c39-b0dd5b2241b9@levkowetz.com> <alpine.LRH.2.21.2005061352200.20509@bofh.nohats.ca> <ae0875b4-13b6-387a-df7a-f157e39c1992@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/ZODByxP3TkHjGDibxCznS1xp9po>
Subject: Re: [Tools-discuss] another case of links not updating
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 May 2020 03:36:27 -0000

On Wed, 6 May 2020, Robert Sparks wrote:

>>  references on my own drafts. It is really unclear how many references I
>>  miss on other people's drafts when I don't know they exist because the
>>  tracker might not show me.

> Again, just to be very clear, I think what you mean by that last sentence is 
> that when you think there's a new draft, you go to tools.ietf.org and are 
> frustrated occasionally because the redirect handler for the name without a 
> draft there doesn't redirect to what should be the current version. That is, 
> by 'tracker' you mean the pages on tools.ietf.org.

Yes. What really happens is I go to google, type in
"draft-pwouters-powerbind", which gets me the tools.ietf.org page. I
click it, then I might be on 02 where it also says 03 because of google
caching or more links having been made to -02 to get better page
ranking, then when I am on -03, which appears as the latest, I manually
change the url to +1 and see if i get file not found. then I know -03
is really the latest.

> The datatracker doesn't have this problem.

I don't like the datatracker page as much, because it's kind of awkward
to click on the tiny html button to get the html version, which is the
tools page. Also, sometimes when googling for the draft gives me too
many wrong hits, I add the word "tools" to the search to get me the
tools.ietf.org version.

Paul