Comment History

 kalarro:

There has been a reply, they said this: "I can confirm that this is something we are adding in the next version. "

But that was on november 2024. So long ago...

I didn't know about the reply, however still.

6 years from the request  being made, 5 years later with one reply saying it will be added in the next version and a year later still nothing o.O

 Stuffed Cat:

Perhaps we should all make diary notes to come back and wish this request "Happy Birthday" every year? 

I hope we never have to. I truly do wonder why it has taken this long for us to get a reply, yet still nothing has happened.

I mean, if it took 6 months, that would be understandable.

But 6 YEARS and still nothing.....no. I don't understand that at all. 

If you have been in MDL long enough, you should know by now that a suggestion means nothing, Greater number of votes also has no effect. It is up to the MDL admins what they want to add on their websites next. You'll be surprised some less demanded feature (with low votes) all of sudden get added like "undecided list" for example ....lol There's no point to cry over it. Just use it for what it is.

I see no merit to an argument about operating costs if, by that, ongoing costs is meant. If it's 'Operating Costs' in the broader business terminology sense then, yes, there would be a small initial development cost.

You can see that each comment displays three bits of information: Who, When and What. There's a fourth - Where - so it can be tied to the entry the comment was made on. Every comment has a unique entry in this site's 'Comments' database table containing those four bits of info.

 Two ways come to mind to achieve what's been requested: (1) Search the 'Comments' table each time the list of comments made by a particular user is required and output a list of those comments. (2) Create a new field for each user holding the unique ref numbers of every comment they've made, then add each new comment ref to that as it's made.

(1) is extremely easy to implement and should require virtually no ongoing maintenance. Given the high number of comments on the site though, it would probably be relatively slow and resource heavy. 

(2) is a bit harder to implement but once the structure is set up it should, again, require virtually no ongoing maintenance. It would be much faster than (1) with minimal processing resource needs.

Nearly all costs would be 'one off', and mostly associated with making the result look acceptable visually.

 TimiZero:

Like I said in my comment above, a suggestion isn't an obligation. The decision is up to MDL. You don't have to think hard about it. If they want to add the feature they will one day :)

They already said they are doing it, but it's taking very long. But that's where the "I was wondering why it would take this long " is coming from.

Simple answer: Because it’s just 1 dev with 9,999 tasks to juggle. Every feature request goes into that mountain, and I have to climb it one bugfix at a time. 😅