Triberr Update: March 2017 – Sharing Frequencies / AWS

In January, we released a massive overhaul of our UI. Since then, we’ve been busy tinkering and just released several updates this week. Here’s a quick summary of what’s new inside Triberr:

Sharing Frequency

Until yesterday, Triberr only offered one (1) sharing frequency setting which applied to every social network connected. Given this constraint, most users only connected a Twitter account as it’s conducive to sharing more content. Suppose you wanted to share every 30 minutes to Twitter, it’s understandable that you will not want to apply the same sharing frequency to Facebook or LinkedIn accounts. Therefore, it’s no surprise that the majority of social connections and shares are Twitter accounts. We certainly don’t want you to solely depend on Twitter for sharing and traffic, so expect this functionality to evolve further:

• 2013 – 2017 – One sharing frequency for all social networks
• 2017 (March 15) – One sharing frequency per social network
• Next iteration – A sharing frequency per social connection

Some of you may be wondering why not just implement custom sharing frequencies per social connection immediately? Unfortunately, we have to work with what existed before (infrastructure, database, and cron constraints), and gradually iterate to our future vision. Though, rest assured that sharing frequencies per connection are in the near horizon. This update is one iteration closer to the end goal. Think of the process to get to the final iteration as outlined in the image below (we just went from a bicycle to a motorcycle – a convertible is next!).

• Save

How does the new update help you?

1. Add your Facebook or LinkedIn account and set it to share at any frequency. More or less sharing, more automation. Win!
2. Assign Tribes per social network. You decide which tribes content get shared to which social networks.
3. Better status indicators – since each social network handles authentication and token expirations differently, we’ve implemented better indicators to let you know when to reauthorize your connections.
4. # of Tribes Assigned – the new page shows how many tribes have been assigned to each social network

Here’s a screenshot outlining the subtle visual changes:

• Save

It may be easy to spot that this update is in preparation for the addition of more social networks coming soon. In the near future, you’ll be able to schedule content on Triberr similar to most well known SaaS applications. Why pay for additional services when Triberr can do it all? 😉

To AWS and Beyond

In a prior post, I had indicated the need for our platform to be prepared for greater scale. Therefore, this past weekend, we migrated the entire app infrastructure to Amazon Web Services (AWS). It sounds simple on the surface, but was quite an endeavor.

Luckily, our migration went smoothly without any disruption for end users.

Now that we’re on AWS, it will allow us to leverage services that can enhance Triberr’s functionality as well as take advantage of AWS services.

Other Minor Updates

There were a dozen other minor updates throughout Triberr. These include items such as:

• Allow ability to follow users by hovering over their profile image in-stream
• Within Queue, see the time posted for shared items
• Improved warnings when deleting blog posts to prevent abuse
• Bug fix for Twitter profile logic
• and several more; see the changelog for details

What’s Next?

For the next month, the team’s focus is on the following key areas:

1. Enhance the Promote Post (i.e. Sticky) functionality. Look for that update before the end of March.
2. Introduce Facebook Pages and Groups for premium members (Lite or Prime)
3. Continue development on achieving sharing frequencies per social connection
4. Move all payment processing to Stripe
5. Overhaul of Tribes section – better tribe management – how can we help you create active and relevant tribes?
6. Better on-boarding experience – Triberr’s is difficult to understand for newbies (we agree!)

If you have any suggestions, please send them to our Support team at – support [at] triberr.com – and we’ll be happy to evaluate your suggestions for inclusion on our development roadmap.