Re^3: Message Inbox: Retain Deleted messages longer (more)

++jdporter for the sarcasm. And thanks for the prod that quite a while has passed but nothing else has happened on this thread.

I quickly gave the one answer that I had handy at the time. After posting, it eventually occurred to me what some of the other answers likely were. But I wasn't where I could post when any of these potential answers finally came to me.

And, of course, I'm not the only person who has knowledge of or access to the code in question. It was my hope that somebody else (maybe even jdporter) might find the motivation to find (or reveal) some of the answers. And I expected I'd have to not completely answer for quite a while if there was going to be a chance of somebody jumping in.

But, as often happens, me volunteering to do some small thing leads to little credit for what I did and more blame for what I didn't volunteer to do. I doubt jdporter sent a personal message to Corion or demerphq or even chromatic "thank"ing them for not answering any of his question.

Part of the reason I do so relatively little at PerlMonks now is, in part, due to trying to avoid that much more blame for what I don't manage to do (and other reasons). But I actually manage to still hang out here and rarely do some tiny bit of maintenance or administration, and I still get the lion's share of the blame (it seems to me). I don't mind getting blamed for doing something badly. But getting blamed for not doing enough simply because almost nobody else has stuck around as long or nobody else did anything on that topic... is discouraging. Oh well.

There are people who do more maintenance/administration at PerlMonks than I do. I'll let them step forward if/when they decide they'd like to start getting blamed more. ;)

One of the nightly cron jobs runs a query like:

update message set folder = folder-1 where -3 < folder and folder < 0;
[download]

and then deletes rows where folder has reached -3 (roughly).

So I think it is actually between 2 and 3 days before a "deleted" message is irretrievable, depending on the time of day when it is "deleted".

You can find -3 hard-coded quite a few places in the other bits of code that deal with "message folders". So we could lengthen the grace period by updating all of those (as well as, I think, just the one instance of "-3" in one cron job).

- tye

Comment on Re^3: Message Inbox: Retain Deleted messages longer (more) Download Code

Replies are listed 'Best First'.
Re^4: Message Inbox: Retain Deleted messages longer (more) by Anonymous Monk on Feb 11, 2014 at 22:47 UTC
Part of the reason I do so relatively little at PerlMonks now is, in part, due to trying to avoid that much more blame for what I don't manage to do Ever wonder if your bedside manner could share in the blame? You regularly come across as gruff with shortness in your answers, maybe a simple rephrasing would head off much of that blame? "It is already several days. About 3, as I recall. I don't have the rest of your answers at my fingertips, but poke me a in a few days if no one has expanded on this to see what I can pull up." That extra 30 seconds is all that's required. And if you are doing so little here, are you at least willing to cede a growing amount of power to others, especially those who may view the monastery differently than you do, to continue maintenance and perhaps growth in new directions? Because you do a lot here, but we don't want the site to die just because you run out of tuits. And no, I don't have any suggestions of who. I have some thoughts as to who not, but that's even less productive, so I will hold them to myself.	[reply]
Re^5: Message Inbox: Retain Deleted messages longer (power) by tye (Sage) on Feb 12, 2014 at 03:01 UTC
are you at least willing to cede a growing amount of power to others I've actively worked to do that for years. Even more important to me is working to address aspects of contributing that greatly contribute to volunteer churn here. Appointments to positions of power have been increasingly designed to promote sustainable delegation rather than continuing the parade of churn and replacement (to varying degrees of success). I keep hoping to get to trying to address much of that directly myself, but I'm still climbing out of 1.5 years of issues that have significantly impacted my effectiveness on volunteer projects (and more time before that which restricted the complexity of projects I could volunteer for). That extra 30 seconds is all that's required. There are sure a lot of people who have very low estimates for me about how long it should take me to come up with a sufficient level of eloquence. It indeed would only take 30 seconds of typing. But that isn't the time-consuming (nor tiring) part of the process. Having actually many times added verbiage with a particular goal while only taking a very short time to do it, I find that it very often is beyond not-helpful and can have quite the opposite of the desired effect. So, thanks for the suggestion (sincerely), but I believe that it is neither as easy nor as effective as you believe (in my case). "I don't have the rest of your answers at my fingertips, but poke me a in a few days if no one has expanded on this to see what I can pull up." Somehow I don't find it likely that adding "If nobody contributes, don't worry, I'm sure I'll come up with the answers" would actually encourage somebody else to go looking for them. (: - tye	[reply]


go ahead... be a heretic
	PerlMonks