Hi,

Ah that's a typo on our part.

We decided on time instead of items due to system limitation. Polling on time would gives better performance compared to polling based on the number of items.

I figured, but just had to make sure.

I'm still confused as to what exactly polling on time does. Does it limit the new posts by the time that is set in that option?

Hi,

It is just the cycle load. It is similar to "load 10 items per cycle", but in this case, load all items in 1 hour, and the next hour, and so on.

I suggest fixing the word choice of it for future versions of EasySocial. Thanks for the explanation.

Thanks for updating Josh.

After thinking about this for some time I've come up with a proposal. Right now when I open up my dashboard it loads one item due to the time constraint. Here's what it looks like:



Ideally it should load multiple items in the stream regardless of how much time has gone by. This is how social networks operate because they want their users to see activity data even if it's a little bit old. Why not allow the admin to determine how many items should load per "pagination load"? Here's what it could look like:



Having it setup this way would not only help make the dashboard upon first glance more engaging but would also help the "load more" appropriately display content based on the server speed and such. With a fast server the user could be fed a nice amount of content as they scroll down. This will in turn make it easier for the user to see what their friends are up to.

Hello Josh,

Setting "number of items to load" is going to be extremely heavy for your site. Believe me, we know as we've ran some tests on this We also need to take into consideration stream items that may or may be visible to some users and may not be visible to other users too. It's going to be extremely complex.

I admit I'm not quite sure how setting the number of items to load is extremely heavy for my site? Loading 3-5 items per pagination load is heavy? Or are you saying having the ability to set it somehow is taxing? Just curious about that.

Take this scenario for example, there is 2 users on your site viewing the site now and pagination is set to display 10 items per page. All these 10 stream items are posted by User C and his privacy for these stream items are only for his friends. Considering that user A is a friend of user C, he can see all the 10 items posted by User C without any issues. User B on the other hand, can't see anything on the stream because these 10 items are not visible to him unless we go into a loop cycle that keeps cycling through all 10 items.

We can't use a single SQL query to fetch different results for different users as they are all dependent on the person's privacy.

I see the problem. Feel free to use that example through out this discussion.

I know a decent amount of SQL, so you are free to use techie language on me. So rather than having the stream "attempt to load 10 items" that the user does not have permission to view, would it be possible for the stream to only attempt to load/count in content that the user has permission to view via the WHERE clause?

Also how does the time method escape this issue?

Hello Josh,

The problem is there are too many "privacy" possibilities on each different stream. We can try to join everything into a single query but it's going to be heavy and people will eventually complain that it's slow

We wouldn't want that. Not quite sure if in the future of ES there might be the possibility for the admin to "disable" privacy?

Hi,

We will come back to this in the future as there will be a lot of concerns regarding this.

Sounds good.

Thanks Josh

I have a question about this... I can only get two items to appear on my dashboard for public viewing. With only two items showing it appears there isn't any activity on the site. Do I have something set wrong (I have the number of items to load at 7 days). Is there any way to display more than just that last to (most recent items)?

Hi,

Sorry but currently we only have the settings to load based on period rather than number of items.

Hey Jason, I don't suppose a additional time could be added, perhaps 1 month? Currently the highest that can be selected is a week. It's fine for active members, but for those who don't have as much going on it will seem "dry". So a 1 month option for the time limit might do the trick. In the settings pagination it has a limit feature called "Frontend Limit", does this limit the number of items that initially load when viewing the stream for the first time? (first time for that page load) Would 1 month combined with a 5 item limit cause more strain on the database than the current setup?

Hello Josh,

Thanks for the heads up on this. We'll consider this in the future But setting it to a month could be a little heavy for busy sites though.

Thanks Josh, we'll consider this because setting it to 1 month for a busy site could be pretty heavy.

Jason Rey wrote:

Hi,

Sorry but currently we only have the settings to load based on period rather than number of items.

Thanks for the reply ... I think I posted this in the wrong place since I am talking about the dashboard in the new frost template. And as far as the time period, that doesn't matter, If I add 10 new items it still will only show the last two even though all ten of them were added within a few minutes of each other.

Thanks .. I'll move my comment over to the 1.2 beta.

Regards!

Hello Barkley,

That's probably because of the privacy of each of the stream item If it's not visible to you, it will not be available

I don't believe it is that either. If the same person updates their stream five times I can only see the last two ... that's my point... it only shows the last (most recent) two posts... permissions are set to "everyone"... Thanks!

Hm okay then that is odd. Can you submit this issue at http://stackideas.com/issues since it is on 1.2. Also, can you download and try beta 4 first?