I guess it's just a matter of how your perception is towards the "last modified" item. The string of the stream item wouldn't really make much of a different but what I would interpret it is that "User B just liked a photo from User B that was uploaded 5 months ago"

Its not only my perception. Im doing UX for last 100 years (give or take)

The problem initially begins in step 2.
It is when user find the stream with bulk of photos, and then clicks on one and likes it.
At this point, user that carried the action have perception of liking the single image.
However, it is absolutely not what he see on the activity stream
He see that User A uploaded 5 images, five months ago, and he liked that action.

A total UX (and more importantly QA) disaster
Try to do some QA on this specific scenario http://qaonrequest.com
You can even get some friends that never used EasySocial before to try it.
You would be surprised how things that seems quite logical to you, are perceived completely differently by the users who are not that familiar with software.

So you are over 100 years old now? When you like a stream that is aggregated, you are actually liking the album and not the photo. If you clicked on the photo and liked the photo in the popup, it doesn't link to the stream.

Its just a saying... same would go for you doing joomla extension development for last hundred years

Anyway, i know how it works, and i'm more then convinced, it works bad.

Seriously, try do some Quality Assurance on this
Find 5 people that never used ES before, tell them what to do, and when they are done (without your influence) ask them what they see, and what they expected to see.
If after liking 1 photo, any of them say they expect to see how they liked an album, i will personally come to Kuala Lumpur and buy pizza's and beer for entire team

hey guys,
from a user and design perspective I think the best solution would be that "like" actions aren't affecting the stream sorting at all. here's why:
to get away from the 1photo vs 5photo stream discussion let's take a much simpler example: a basic story update.

say you wrote a story update 2 years ago and now someone likes it, then this would be bumped on top of the stream. for any regular users it's not obvious why it's there or better said most people would think it shouldn't be there at all. while technically correct (new like action triggered, something changed on the object) it's not identifiable by a user as they only see the 2 years old timestamp.

when you instead comment this old stream and it gets bumped up then it does make sense and is obvious for the user as the comment timestamp easily identifies the reason for the new stream position.

Alex wrote:

hey guys,
from a user and design perspective I think the best solution would be that "like" actions aren't affecting the stream sorting at all. here's why:
to get away from the 1photo vs 5photo stream discussion let's take a much simpler example: a basic story update.

say you wrote a story update 2 years ago and now someone likes it, then this would be bumped on top of the stream. for any regular users it's not obvious why it's there or better said most people would think it shouldn't be there at all. while technically correct (new like action triggered, something changed on the object) it's not identifiable by a user as they only see the 2 years old timestamp.

when you instead comment this old stream and it gets bumped up then it does make sense and is obvious for the user as the comment timestamp easily identifies the reason for the new stream position.

+1

i could live with that Alex

Thanks for the heads up on this. We'll see what we can do about this in the future but as it is right now, I think it makes perfect sense to bump up the stream when an "action" is made on the stream

Mark wrote:

Thanks for the heads up on this. We'll see what we can do about this in the future but as it is right now, I think it makes perfect sense to bump up the stream when an "action" is made on the stream

In that case, would it be possible to add a line for new like action for that feed something like "xyz likes this - abc minutes ago". This way users will know why that feed appears at the top all of a sudden. I noticed the same behaviour happens for k2 article feeds too which are liked after a few days and at first hard to figure out why it's there at the top again if you don't understand new likes also bumps them to the top. So a one liner on the action notice would solve this confusion.

If you introduce a string like this, it gets way more complicated It will be like inception because if you like the like activity stream, it will then generate another stream

No you have misunderstood I think. I didn't meant another new stream reporting the like. I meant when you bump the original stream to the top for new likes, maybe add a small line at the top or bottom of the same stream block with a message that xyz liked that stream. If this message was added as an independent stream then what you said was right.

I think both you and the rest here have valid arguments and both side makes sense too. It will be interesting to see if something comes out of this that can make everyone happy

Hm, I think it wouldn't make sense to display an additional text on the existing stream item. It's actually defeating the purpose of having the likes text that appears above the comment and I think that would be even more confusing.

Theres a lot of things to consider here. Lets get back to specific scenario im trying to advocate here.
I cant stress enough that i have liked only one photo and that fact is being ignored in the discussion.
I did found the photo on the stream, it is the picture from an album, but action is getting registered for completely different object (album)

In best case, when i like a single photo, no matter how i found that photo whether browsing an album, or finding it on the stream, when i click on it and like that specific photo, like should be registered for that photo, NOT the album. I didn't liked the album


Sorry for bolds and caps, but this discussion is going completely wrong way.
Bumped stream item is just a side effect.

Hi Darko,

I am sorry for the delay of this reply.

In best case, when i like a single photo, no matter how i found that photo whether browsing an album, or finding it on the stream, when i click on it and like that specific photo, like should be registered for that photo, NOT the album. I didn't liked the album

Regarding the above, the 'like' actually still registered under photo that you've liked, just that the modifed date of album stream get updated.
Anyway, we've fixed this issue so that, when someone liked / commented on a photo, if system detected this photo part of the aggregated stream, then the system will not update the stream modified date.

Attached the modified php files and please follow below instruction to patch at your EasySocial

1. Download and copy 'comments.php' to folder 'JOOMLA/components/com_easysocial/controllers/' and overwrite the existing comments.php.
2. Download and copy 'likes.php' to folder 'JOOMLA/components/com_easysocial/controllers/' and overwrite the existing likes.php.
3. Download and copy 'stream.php' to folder 'JOOMLA/administrator/components/com_easysocial/models/' and overwrite the existing stream.php

The above fixes will be added into next release of EasySocial
Hope this help and have a nice day