Users can now add an extra layer of security to their Orbit accounts with the ability to enable Two-Factor Authentication (2FA).
To enable 2FA, head to
Workspace Settings > Two-Factor Authenticationand follow the instructions.
You will be asked to scan a QR code, which you can do with an authenticator app such as Google Authenticator or Authy.
Once 2FA is enabled, when logging in to your Orbit account, you will be asked to enter the verification code from your authenticator app:
As a means of increasing the security of the Orbit app, we've implemented a change to Orbit URL paths in replacing the numerical IDs of Orbit Workspaces, Members, and various other elements with encoded IDs.
For Orbit users making API calls to access Workspaces or Members:
In order to avoid any of your active API calls, scripts, or integrations breaking, we kindly request that you use the
slug(instead of the ID) of your Workspace or the Members you’re referencing to avoid any lapses in Orbit data and activity.
To access a workspace:
To access a member:
We're changing the format of the Orbit API token that you use to authenticate requests with the Orbit API. The new format provides the following benefits:
- It makes the API token more secure and verifiable.
- It allows Orbit to participate in the GitHub Secret Scanning program that'll inform you when your Orbit API token is accidentally committed in a GitHub repository.
If you're interested in learning about the math behind our new API token format, take a look at this awesome blog post by the GitHub engineering team.
Is your old token still working?
Your old token will only continue working until November 30 2021.
Tokens that haven't been regenerated by this date will cease to work. Therefore, we strongly recommend you upgrade to the new token format ahead of that date to increase the security of your data and to avoid any potential disruption on your workspace.
Please, go to your account settings page and click Regenerate to get an API token in the new, more secure format.
Remember that you will need to update the API Token anywhere it was previously used.
On Aug. 2nd, the Orbit app received an unexpected error from the Twitter API which caused several Twitter integrations to be marked as invalid. As a result, we stopped importing new activities for these integrations.
The bug was fixed on Aug. 12 and activities are now being successfully imported.
If the Twitter integration in your workspace has been affected, you may see a big spike in new members on Aug. 12 due to the activities import adding new members from the past 10 days.
The Meetup Community Integration allows you to add RSVPs from your Meetup organization into your Orbit workspace.
A new version (v0.1.0) has been released that improves the overall experience of using the integration:
- Historical importing of older data is now possible within the instantiation of the client in the code and with the command-line interface (CLI) using the historical_importboolean parameter in the client instance or the--historical-importflag in the CLI
- Which Meetup RSVPs to send to Orbit are now dynamically determined based on the last activity for that type currently in your Orbit workspace
The GitHub Action template for Meetup has been updated with the latest instructions on how to leverage the
--historical-importoption. You can update your own action workflow using the latest instructions.
ruby_orbit_activitiesopen-source library provides developers with a tool to seamlessly work with the activities endpoint in the Orbit API in Ruby.
This helper library powers many of the Orbit Community Integrations, such as Meetup, LinkedIn, DEV, and Circle.
In the new release of the library, there is improved handling of rate-limiting in the Orbit API. The API restricts requests to no more than 120 requests per minute. The new version of the library now accounts for that limitation and will pause sending new requests when it encounters the rate limit error, and resume once the limitation has been released.
The Ruby gem can be found on GitHub with instructions on how to use it to build your own applications and services utilizing the Orbit API.
We’ve improved our bulk member editing feature, introduced last April, that now allows you to update any number of members at a time (it was previously capped to 25).
Using this feature, you can add and remove tags to several members in one go, as well as editing their attributes (location, company, etc…) and deleting them.
You can select members by picking them individually, selecting the whole current page, or all members with current filters.
As a reminder, here are the available shortcuts when bulk editing members:
- ↑/kand↓/jto navigate;
- Enterto visit the profile of the currently selected member;
- xto select or deselect the currently selected member;
- Eto edit the fields of the current selection;
- Cto delete the current selection;
- Tto add tags to the current selection;
- Rto remove tags from the current selection
On the Reports page, a new top navigation menu replaced the old sidebar to make it easy for you to explore all your community data and discover Orbit's reporting capabilities:
- The Overviewdropdown enables you to access thePulse,Totals, andLeaderboardreports.
- Explore Dimensionsto get stats aboutActivity types,Companies,Channels,Groups,LocationsandTagsyou have in your workspace.
- Custom Dashboardsallow you to create Dashboards that you can share with your team.
- The Builderenables you to create the figures you like and add them to your custom dashboards.
- Popular channelsallow you to quickly filter by the integrations (Twitter, GitHub, Slack...) added to your workspace.
Date rangepicker and the
Filterswidget offer you many more options to explore your community data and personalize your figures.
We have added support for
filtering new or returning membersfor a given time period:
In the example above, selecting “New (first active after Jun 9)” will select only members whose first activity happened after June 9, and vice-versa.
This filter is available on the Members, Activities, and Reports pages, and can be used to create Custom Dashboards.
The DEV Community Integration enables you to add DEV blog post comments and new DEV followers to your Orbit workspace.
The integration's new release, v0.5.0, now supports pagination for DEV followers and comments. This means that on each run the integration will fetch all the pages of responses from the DEV API, and not only the first page of results.
For very active DEV user accounts and blog posts, there was a chance that some activity would not be added to the Orbit workspace if there was more than a single page of results in between the times the integration was run. This has been addressed in this recent release.
Users of the DEV GitHub Actions template do not need to do anything to benefit from the new pagination support. If you are using the Rubygem package in your own code, make sure your installed version is upgraded to the latest release.