Forum Activity for @brian

Some questions (from a Social Engine user)

Design and Skin Customization

JR can do anything SE can pretty much, so that's not a problem. Jamroom can easily make "community" type pages, etc, listing anything from your profiles any way you want.

If you plan on having a small niche site, that's all good. I would highly recommend that if you plan on having a lot of users online at the same time interacting with your site, you avoid "community" style pages. Imagine that page you posted a screenshot of with 500 people posting at the same time - it would be unusable. This is why when you go to facebook or twitter there is no "community" section - all the interaction takes place on your profile or other users profiles.

Of course it's 100% up to you, but having been doing this for a very long time I've seen many sites really struggle with performance as many of the features that work great on a small, intimate site suddenly blow up once they get a surge in users.

Some questions (from a Social Engine user)

Design and Skin Customization

With JR this is totally doable - BUT - you would want to make sure you don't use Jamroom's power user and multi-user profile features, as in those instance it could break (if the user never visits their home profile after logging in then their active profile id would not be set).

Some questions (from a Social Engine user)

Design and Skin Customization

It sounds like you're actually looking for chat then?
updated by @brian: 07/10/16 01:00:12PM

Some questions (from a Social Engine user)

Design and Skin Customization

Sorry - don't do skype

JR can do this - that's no problem. But like Twitter, your users will be on their own profile when they make a post (for example - I cannot POST to my timeline from twitter.com - I have to go to twitter.com/jamroom). Users can leave comments on other user's profiles as well.

We do have some big updates coming in the next revision of our timeline that will make things a bit more interactive, but you can likely do most of what you want right now.

When it comes to configuring/customization JR can do most anything you want - if you feel JR doesn't do something, just post here and we can let you know.

Thanks!

not an action_text activity error

Design and Skin Customization

No - it's created at the same time as the item is created (using an event trigger).

not an action_text activity error

Design and Skin Customization


Because those actions are tied to other pending items (say a song) - doesn't make sense to show a "so and so just posted this song" timeline update if the song is not approved.

Some questions (from a Social Engine user)

Design and Skin Customization


Jamroom can show a feed of site activity if that is what you're looking for. If you can clarify (with details) what you are looking for we can let you know if it is doable.

Some questions (from a Social Engine user)

Design and Skin Customization

The profile tweaks module does custom profile backgrounds - i.e.:

https://www.jamroom.net/brian

https://www.jamroom.net/the-jamroom-network/networkmarket/2/profile-tweaks

not an action_text activity error

Design and Skin Customization

This isn't a very helpful error message - I'll get that fixed up. What this means is the timeline entry is NOT modifiable, since it's not an action entry where the user typed it in - it's a timeline entry that was added by a module (i.e. "so and so just posted a new song", etc.).

The default in pending is to link to the "update" view, and sine automatic timeline entries have no update view you see this error.

I think we'll need to add a custom pending items setup in for timeline entries, as well as update the error message so it's more helpful - we'll check that out.

Thanks!

Queue depth status

Using Jamroom


For each job you want to be able to adjust the priority on, just make it a unique worker.


It actually is numerical - the default priority for a queue worker is 5.

HIGH_PRIORITY_QUEUE = 1 and LOW_PRIORITY_QUEUE = 9. So if you need to you can use any value between 1 and 9. "HIGH_PRIORITY_QUEUE" is just a named constant, which makes it easier to understand what it means rather than "1".


Next version of the core - hopefully soon - it's in testing right now so I would anticipate sometime in the next week or so.

Let me know if that helps.