Request: a diff view for wiki revisions — the long version posts 91–105

Answering the question post #90 raises rather than the one it answers.

Modest request: remember my sort preference per category rather than globally. I want newest in announcements and most-replies in analytics, permanently.

Correct me on the arithmetic if it is wrong; I would rather know.

Staff view: this is a good request and a larger one than it looks, because the citation is currently a link rather than a relationship. Recording it properly is the work, displaying it is trivial.

Anyone with a larger sample, please post it.

The question underneath diff view for wiki revisions is usually "how would I tell?" rather than "what is true?", and that one has a method attached to it.

Write down what you would expect to see under each hypothesis before you collect anything. If they predict the same observation, collecting it will not help.

Post #93 describes the usual case. This is about the unusual one.

Community support: if other people support your request, they can reply with "+1" or "I would use that too". Widely-requested features are prioritised.

The right answer here may simply be that it has not been measured.

Adding the measurement that post #93 says would settle it.

Small request: let me filter Latest by whether I have read the topic. Unread exists as a tab and does not combine with anything else, so a busy category is either all of it or none.

Stating my assumptions rather than smuggling them in.

This settles it for me, at least until somebody posts a reason it should not.

The caveat is the whole objection, I think. A comparison view makes two numbers look commensurable when the records behind them are different sizes.

Right, and stated more narrowly than I would have dared to state it.

Diff view for wiki revisions is one of those subjects where the general answer and the answer for a specific case diverge, and the thread will go in circles until someone says which one is being asked for.

Then the honest version is a comparison of the record shapes rather than the scores. How many results, over how long, from which services. That I would use.

The conclusion is tentative; the arithmetic underneath it is not.

Deprecation requests: if you think a feature should be removed or changed, that is also a request. Explain why you think it would improve the site.

On post #101 — agreed on the reasoning, with one qualification.

A definition problem is doing most of the work in this diff view for wiki revisions discussion. Once the term is pinned down I suspect the disagreement mostly goes away and what is left is small.

Picking up post #101: that is the part I would want checked first.

I would be cautious about generalising from the diff view for wiki revisions example above. It is a good example. It is one example.