Re^4: New Feature: Thread Watcher - Should we call it 'follow' instead?

Considering features prefer consistency, confusion reduction and short ways.

The page to check is called My *Watched* Nodes so newbies need to associate "watch" with "follow".

On another note:

It's also confusing me that

watches list the actual node prior to context
reply notifications list context prior to actual node

[ ] root says jdporter posted Re^3: New Feature: Thread Watcher - Shou
+ld we call it 'follow' instead? > New Feature: Thread Watcher

[ ] root says You've got a reply to Re: Why is Dumper returning "!!1" 
+for true file test? from XXX at Re^2: Why is Dumper returning "!!1" f
+or true file test?
[download]

Other features I'd like is an option to shorten the messages from redundancy

That is applying a regex to shorten the context node

[ ] root says You've got a reply to "Re: ..." from XXX at Re^2: Why is
+ Dumper returning "!!1" for true file test?
[download]

Cheers Rolf
_{(addicted to the Perl Programming Language :)

see Wikisyntax for the Monastery}

Comment on Re^4: New Feature: Thread Watcher - Should we call it 'follow' instead? Select or Download Code

Replies are listed 'Best First'.
Re^5: New Feature: Thread Watcher - Should we call it 'follow' instead? by jdporter (Paladin) on Apr 07, 2024 at 21:13 UTC
It's also confusing me that watches list the actual node prior to context reply notifications list context prior to actual node The problem is that the watcher code now — thanks to an earlier request to roll up multiple notifications — has to produce messages like the following: `$user posted $node` — this happens due to user follow. `$user posted $note somewhere under $parent` — this could be direct or any replies. `$user posted $note; this hits multiple watcher criteria.` I abbreviated "somewhere under" as ">". Can you suggest new wording for all of those so that they (a) convey the meaning intended by watcher and (b) have the desired consistency? Today's latest and greatest software contains tomorrow's zero day exploits.	[reply] [d/l] [select]
Re^5: New Feature: Thread Watcher - Should we call it 'follow' instead? by jdporter (Paladin) on Apr 08, 2024 at 12:42 UTC
Considering features prefer consistency, confusion reduction and short ways. The page to check is called My Watched Nodes so newbies need to associate "watch" with "follow". I'm inclined to replaced "watch" with "follow" globally. Do you have an opinion?	[reply]
Re^5: New Feature: Thread Watcher - Should we call it 'follow' instead? by jdporter (Paladin) on Apr 08, 2024 at 12:48 UTC
an option to shorten the messages from redundancy ... That is applying a regex to shorten the context node Well, I just patched it to shorten the parent's title unconditionally. It is not an option. Will people complain?	[reply]
Re^5: New Feature: Thread Watcher - Should we call it 'follow' instead? by Danny (Chaplain) on Apr 08, 2024 at 21:03 UTC
root says You've got a reply to "Re: ..." from XXX at Re^2: Why is Dumper returning "!!1" for true file test? Or just `reply: title_and_link_to_what_is_replied_to from: XXX` [download]	[reply] [d/l]