Added a comment
authoryarikoptic <yarikoptic@web>
Mon, 9 Jan 2023 22:04:11 +0000 (22:04 +0000)
committeradmin <admin@branchable.com>
Mon, 9 Jan 2023 22:04:11 +0000 (22:04 +0000)
doc/todo/Allow_for_URLs_prioritization_WITHIN___40__web__41___remote/comment_5_4d8e8abe8b31174ccc536387a96b0228._comment [new file with mode: 0644]

diff --git a/doc/todo/Allow_for_URLs_prioritization_WITHIN___40__web__41___remote/comment_5_4d8e8abe8b31174ccc536387a96b0228._comment b/doc/todo/Allow_for_URLs_prioritization_WITHIN___40__web__41___remote/comment_5_4d8e8abe8b31174ccc536387a96b0228._comment
new file mode 100644 (file)
index 0000000..babcd48
--- /dev/null
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="yarikoptic"
+ avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
+ subject="comment 5"
+ date="2023-01-09T22:04:11Z"
+ content="""
+> Because when getting a file, the main web special remote is tried before this high-cost slowhost one, and will use any url, including slowhost.com urls.
+
+can't I just give the entire `web` remote the highest cost so it is then considered last by default and all the prior \"*web\" remotes with custom costs for fast/slow would be considered in their \"weighted\" fashion?
+"""]]