Request: export my own posts — one year on — setting out what I have, and where I think it stops being reliable.
A methods question rather than a substantive one, about export.
Everyone quotes the same figure and I cannot find anyone who says how it was arrived at. That is not an accusation; it usually means the derivation is somewhere obvious and I have missed it.
Taking the opening post at face value and following it one step further.
That reframing is better than the original request and staff would consider it. Which is a good illustration of why these belong in public: the first version would have been declined and the third is worth building.
Scoping that to what I have actually seen rather than what I have read.
Worth separating two things that post #3 runs together.
Request with the use case rather than the feature. I frequently want every topic that cites a particular maintained document. At the moment I can find the document from the topic and not the reverse.
That is my reading. Someone else read the same page differently and was reasonable.
This follows post #3 rather than contradicting it.
Export is a question about a distribution, not about a value, and treating it as a value is what produces the confident wrong answers.
Request from the analytics side: allow a table in a post to be marked as data rather than layout, so it can be copied without the formatting. Half the tables here are worth pasting into a spreadsheet.
Export came up in a thread eighteen months ago and was answered well. I cannot find it, which is itself the problem, so here is the reconstruction.
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.
It is a small point and it changes the answer, which is an awkward combination.
Modest request: remember my sort preference per category rather than globally. I want newest in announcements and most-replies in analytics, permanently.
The right answer here may simply be that it has not been measured.
On post #10 — agreed on the reasoning, with one qualification.
Counter-request, gently: please do not add anything on hover. It does not exist on a phone and half the readers here are on one.
Both of these are in the same family and staff would rather do one thing well than two things partly. If the range link exists, the citation relationship gets much easier to record, so the order matters.
Post #14 describes the usual case. This is about the unusual one.
Use case: explain why you think the feature would help. "I would use this to..." makes the request concrete.
I keep a log of this specifically because memory is unreliable about it.
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.
Request: an export of my own posts. Not for any dramatic reason — I want to search my own history offline, and site search is optimised for finding other people's material.
Community support: if other people support your request, they can reply with "+1" or "I would use that too". Widely-requested features are prioritised.
Adding it in case it saves somebody the afternoon it cost me.
Post #19 and I disagree about the size of the effect, not about the direction.
Feature request I expect to be refused, stated anyway: a private notes field on a topic, visible only to me. I keep those in a text file and the text file loses the link.
Noting that the question and the thing people usually mean by it are different.
Taking post #19 at face value and following it one step further.
Small methodological point on export: repeating a measurement is cheap and resolves most of what is being argued about here at no cost to anyone.
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.
Written quickly, so the reasoning may be tighter than the wording.
This follows post #23 rather than contradicting it.
Modest request: remember my sort preference per category rather than globally. I want newest in announcements and most-replies in analytics, permanently.
Not a conclusion. A place to stand while looking for one.
Both of these are in the same family and staff would rather do one thing well than two things partly. If the range link exists, the citation relationship gets much easier to record, so the order matters.
Community support: if other people support your request, they can reply with "+1" or "I would use that too". Widely-requested features are prioritised.
That would be genuinely useful in the vendor pages too, where a discussion link often means posts eleven through fifteen and points at eleven.