Consolidated Thread Update Notifications

[SagaLore]

ATOT being the popular forum that it is, when I subscribe to a thread I am inundated with emails that the thread was updated.

Recently the Moderators have been removing my subscriptions, because they're getting bounce backs from my host, but my host is fine. I think it is this flood of emails that could be causing an occasional bounce back.

So first I get too many then my subscriptions are terminated.

My suggestion is to implement what some other forum softwares have - don't send another update notice until the thread has been revisited. Just imagine how much processing and bandwidth you would save by doing this.

Also, on topic with the notices - if you're not going to show the emoticons in the email, then just strip out the html reference for the image - or better yet, revert the emoticon to it's text representation, or just make the entire email plaintext.

Thanks :gift:

 

[ProviaFan]

The only-one-notification-per-thread thing would be a nice feature, though some time ago I think the excuse for not implementing it was that the architecture of Fusetalk didn't allow for such without a major rewrite (which is certainly a valid reason IMHO, but if they didn't plan for that and include the potential to implement it in the second-to-latest upgrade - the one where everything was FUBAR for a week...)

On the other topic, I used to have my subscriptions delivered by email, but it was a pain in the a... er, neck because if a mail bounced back, all my subscriptions would be cleared. This sucked especially if I was trying to follow an important thread that wasn't updated frequently. Since then, I just use PM subscription updates; though it's not as convenient as email, at least my subs don't get sent to /dev/null if my email provider has a temporary glitch. :roll:

 

[SagaLore]

Originally posted by: ProviaFan
The only-one-notification-per-thread thing would be a nice feature, though some time ago I think the excuse for not implementing it was that the architecture of Fusetalk didn't allow for such without a major rewrite (which is certainly a valid reason IMHO, but if they didn't plan for that and include the potential to implement it in the second-to-latest upgrade - the one where everything was FUBAR for a week...)

It seems to me it would be as simple as take the routine responsible for the subscribing (assuming the code is modular!), and referencing an additional routine that keeps track of this in a separate table in the database. The table would simply have a column with an import of all the users, a column that contained the catid&threadid, and a column that had a simple true/false flag. Email is sent, flag is true. Then find the other routine responsible for determining if the user is browsing the threads. Reference the routine, set the flag to false. Finally reference this routine in the routine responsible for emailing the notices - simple lookup in the table to see if the flag is true or not and email if it is false.