comment

diff --git a/doc/todo/trust_presence_info_for_specific_remotes_for_specified_time/comment_1_96e12b8ecba4bacfbfa5c58025bedaab._comment b/doc/todo/trust_presence_info_for_specific_remotes_for_specified_time/comment_1_96e12b8ecba4bacfbfa5c58025bedaab._comment
new file mode 100644 (file)
index 0000000..5bcb738
--- /dev/null
+++ b/doc/todo/trust_presence_info_for_specific_remotes_for_specified_time/comment_1_96e12b8ecba4bacfbfa5c58025bedaab._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2022-04-04T18:26:00Z"
+ content="""
+Using location tracking for this seems to trade off the time to contact the
+remote and check presence with bloat of the git repository. This does not
+strike me as a good tradeoff. If I were going to implement this, I suppose
+I'd store the information in sqlite instead.
+
+I'm not clear what the use case or benefit of this would be?
+"""]]