Commit

Author:

Hash:

Timestamp:

+10 -8 +/-1 browse

Kevin Schoon [me@kevinschoon.com]

d30e53659d2c8fdf64a7b1af6b6f5c3d91a4de1f

Thu, 05 Jun 2025 19:41:19 +0000 (2 days ago)

fixup meta tag
1diff --git a/README.md b/README.md
2index 2c178eb..22ac7f1 100644
3--- a/README.md
4+++ b/README.md
5 @@ -295,7 +295,7 @@ element such as below at the root domain of your forge. For example,
6 type="application/rss+xml"
7 title="Recent Forge Activity"
8 href="https://code.example.org/firehose.xml" />
9- <meta name="forge-feed:index" content="enabled"/>
10+ <meta name="forge-feed:index" content="https://code.example.org/firehose.xml"/>
11 </head>
12 <body>
13 ...
14 @@ -303,16 +303,18 @@ element such as below at the root domain of your forge. For example,
15 </html>
16 ```
17
18- The link SHOULD have a title of "Recent Forge Activity" such that it uniquely
19- identifies this feed as being related to forge updates. A server SHOULD also
20- provide a meta tag with the name `forge-feed:index` which may be toggled
21- with `content="enbabled"` or `content="disabled"`. If this tag is present and
22- enabled then global index servers will periodically crawl the content here for
23- discovery, if it is disabled then servers will remove it from their schedule.
24+ The link MAY have a title of "Recent Forge Activity" such that it uniquely
25+ identifies this feed as being related to forge updates. A server MUST provide a
26+ meta tag with the name forge-feed:index where the content of the tag matches
27+ the href of an RSS link listed on this page which should be used for indexing
28+ by external crawlers. Applications which rely on the forge-feed:index meta
29+ tag MUST stop crawling the serving website if this tag is no longer present
30+ in the pages HTML.
31
32 ### An example Feed
33
34- Below is an example RSS feed with an optional repository section (described below).
35+ Below is an example RSS feed with an optional repository section (described
36+ below).
37
38 ```xml
39 <?xml version="1.0" encoding="utf-8"?>