Fossil SCM

Slight fileformat.wiki touchups regarding attachments/tags on forum posts.

stephan 2026-05-23 09:17 UTC forum-attachments
Commit 07bee50ac126855407e182a5f48b0a2e0f5ef437a5523fcd6e6173016647e5a6
1 file changed +9 -8
--- www/fileformat.wiki
+++ www/fileformat.wiki
@@ -608,18 +608,19 @@
608608
The <b>Z</b> card is the required checksum over the rest of the artifact.
609609
610610
<a name="forumpost-tag"></a>
611611
<strong>Forum posts and tags:</strong>
612612
613
-When adding [#ctrl|tags] to forum posts it is generally up to the
614
-application to tag only the first version of any given post. For
615
-example, if post X has two edits, a tag applied by the user to X+2
616
-should generally be applied to version X instead. Though this
617
-complicates the app logic for applying tags, it simplifies the app's
618
-location of tags. As of this writing (May 2026), no current Fossil
619
-use cases would be improved by tagging specific subsequent versions of
620
-posts, e.g. our hypothetical X+1.
613
+When adding [#ctrl|tags] or [#attachment|attachments] to forum posts
614
+it is generally up to the application to tag/attach to only the first
615
+version of any given post. For example, if post X has two edits, a tag
616
+or applied, or attachment added, by the user to post X+2 should
617
+generally be applied to version X instead. Though this complicates the
618
+app logic for applying tags, it simplifies the app's location of tags.
619
+As of this writing (May 2026), no current Fossil use cases would be
620
+improved by tagging specific subsequent versions of posts, e.g. our
621
+hypothetical X+1.
621622
622623
623624
<h2 id="summary">3.0 Card Summary</h2>
624625
625626
The following table summarizes the various kinds of cards that appear
626627
--- www/fileformat.wiki
+++ www/fileformat.wiki
@@ -608,18 +608,19 @@
608 The <b>Z</b> card is the required checksum over the rest of the artifact.
609
610 <a name="forumpost-tag"></a>
611 <strong>Forum posts and tags:</strong>
612
613 When adding [#ctrl|tags] to forum posts it is generally up to the
614 application to tag only the first version of any given post. For
615 example, if post X has two edits, a tag applied by the user to X+2
616 should generally be applied to version X instead. Though this
617 complicates the app logic for applying tags, it simplifies the app's
618 location of tags. As of this writing (May 2026), no current Fossil
619 use cases would be improved by tagging specific subsequent versions of
620 posts, e.g. our hypothetical X+1.
 
621
622
623 <h2 id="summary">3.0 Card Summary</h2>
624
625 The following table summarizes the various kinds of cards that appear
626
--- www/fileformat.wiki
+++ www/fileformat.wiki
@@ -608,18 +608,19 @@
608 The <b>Z</b> card is the required checksum over the rest of the artifact.
609
610 <a name="forumpost-tag"></a>
611 <strong>Forum posts and tags:</strong>
612
613 When adding [#ctrl|tags] or [#attachment|attachments] to forum posts
614 it is generally up to the application to tag/attach to only the first
615 version of any given post. For example, if post X has two edits, a tag
616 or applied, or attachment added, by the user to post X+2 should
617 generally be applied to version X instead. Though this complicates the
618 app logic for applying tags, it simplifies the app's location of tags.
619 As of this writing (May 2026), no current Fossil use cases would be
620 improved by tagging specific subsequent versions of posts, e.g. our
621 hypothetical X+1.
622
623
624 <h2 id="summary">3.0 Card Summary</h2>
625
626 The following table summarizes the various kinds of cards that appear
627

Keyboard Shortcuts

Open search /
Next entry (timeline) j
Previous entry (timeline) k
Open focused entry Enter
Show this help ?
Toggle theme Top nav button