My idea is for a new message that one can get.
If a Scratcher gives a project a love and a favorite, rather than giving two separate messages for both, it will give the creator one combined message.
For example:

Example_Scratcher loved and favorited your project example project 4:40 p.m.

I think this might be a good thing, as many a time, I've gotten two messages saying “x loved your project y” and “x favorited your project y”.
Just a suggestion, though.

I assume this is a duplicate. However, I can't find it.

LionHeart70 wrote:

I assume this is a duplicate. However, I can't find it.

Where have you seen it before?

-Multinia- wrote:

LionHeart70 wrote:

I assume this is a duplicate. However, I can't find it.

Where have you seen it before?

In the suggestions forum. I can't find it, though.

LionHeart70 wrote:

-Multinia- wrote:

LionHeart70 wrote:

I assume this is a duplicate. However, I can't find it.

Where have you seen it before?

In the suggestions forum. I can't find it, though.

Hmm…







so what do you think of my idea though

I think this is a great idea and would save the extra notifications. Support!

It's sort of a duplicate. I technically suggested this already, but I think the link's gonna be impossible to find. I'll keep searching.

Edit: Found it!

I couldn't find the duplicate specifically for this topic, so either isn't not a duplicate (congrats!) or it's lost in some collective “messages improvements” or “smarter messages” suggestion

Finally found my post. Although it's more of for the What's Happening section, so I don't know if this counts as a duplicate.

FancyFoxy wrote:

Finally found my post. Although it's more of for the What's Happening section, so I don't know if this counts as a duplicate.

No, the topic isn't suggesting that. Besides, if someone wants to suggest something that isn't the same thing as the topic but related, they should make a different topic.
I know it suggests the What's Happening, but I feel like being specific requires a separate thread.

But I like getting two messages. Besides what would happen if a user loves, comments, then favorites? What if a user loves one hour, and favorites next week?

muellly wrote:

But I like getting two messages. Besides what would happen if a user loves, comments, then favorites? What if a user loves one hour, and favorites next week?

I think it would check if you have unlooked at messages Loving and favoriting if you do it would combine them.

I don't think it would be too hard to add. Is it necessary? It's not going to make it that much shorter and there could be better ways.

muellly wrote:

But I like getting two messages. Besides what would happen if a user loves, comments, then favorites? What if a user loves one hour, and favorites next week?

Comments should be separate, since in the notifications it tells you what the user commented.

muellly wrote:

But I like getting two messages. Besides what would happen if a user loves, comments, then favorites? What if a user loves one hour, and favorites next week?

If one loves and then favorites a project, it will sense the love that is given and send a message, and then it will sense the favorite and replace the love message with a love-and-fave message.

-Multinia- wrote:

muellly wrote:

But I like getting two messages. Besides what would happen if a user loves, comments, then favorites? What if a user loves one hour, and favorites next week?

If one loves and then favorites a project, it will sense the love that is given and send a message, and then it will sense the favorite and replace the love message with a love-and-fave message.

Okay, however what if one week the person loves the project, one week latter the same person favorites the project. If it replaces the love message then the person will never see it because it if buried under other messages.

muellly wrote:

-Multinia- wrote:

muellly wrote:

But I like getting two messages. Besides what would happen if a user loves, comments, then favorites? What if a user loves one hour, and favorites next week?

If one loves and then favorites a project, it will sense the love that is given and send a message, and then it will sense the favorite and replace the love message with a love-and-fave message.

Okay, however what if one week the person loves the project, one week latter the same person favorites the project. If it replaces the love message then the person will never see it because it if buried under other messages.

That's why I say it should only be if both are unviewed.

I'm assuming the code would detect if the love and favorite were given in the same 30-60 seconds, and if they were, they would be sent as one message. I may be wrong, but I think messages are sent as soon as they are triggered. So the ST would have to delay the sending time by 30-60 seconds. That really wouldn't matter though, I don't think, so yeah. I support. I'm going on hiatus for a couple weeks starting Monday, and having this implemented would bring my message count down a lot, which would make the messages easier to scroll through.

EDIT: I saw what -Multinia- wrote, and I'm not really sure that's a good idea. Separate messages are probably better for far-apart loves and faves. A detector for when to send messages together and apart would most likely be easy to throw together, anyway.

Not a major issue, but I support.