Upgrading open groups: Bringing back DMs from open groups
September 12, 2022 / Kee JefferysPrivate messaging
Update: PySOGS 0.3.5 is now available using the install instructions below
Open groups are an important part of Session. As more users flock to Session, it’s clear that open groups are one of the main ways for people to connect.
Our open groups on Session (covering things like Oxen, Session, and Lokinet) have grown into bustling communities with thousands of users. Of course, there are heaps of other open groups on Session that we don’t operate — open groups that are fully owned and operated by members of the community.
If you’re operating a Session Open Group Server (SOGS) — there are some changes coming your way!
ID Blinding: Making it easier to connect through open groups
A lot of people have been asking why they can’t pull Session IDs from open groups any more. The answer is simple: Spam.
Big open groups become big targets for people to try and scrape Session IDs to send spam messages or attempt impersonation. Because we run some large open groups ourselves, we noticed this issue a lot. We always planned to re-implement some way to directly contact other members of open groups, but we needed to build some anti-spam measures first.
The mechanism we have implemented is called ‘ID Blinding’: allowing you to send message requests to other people in an open group without needing their real Session ID. This feature will go a long way to preventing spam in Session, making it a safer, special-er place to hang out.
What does this mean for me?
At first, we are only going to enable ID Blinding for the official Open Groups which are operated by the Session Team. This way we can ensure that everything is working as-expected before rolling it out to all SOGS.
As of this article being published, we have enabled ID Blinding in the official SOGS, so you should be able to send message requests to other people in those groups. You’ll know that ID Blinding is enabled if the ID you are messaging begins with a ‘15’ instead of the ‘05’ of a real Session ID.
If your Session client is not up-to-date, it is likely that these open groups will not function as expected on your device. We recommend upgrading your Session client to the latest release to prevent your open groups from going silent!
After we’re confident that blinding is working well on our live open groups, we will release a new version of PySOGS (0.3.5) which contains ID Blinding functionality and enables the ability for users to send messages requests to each other through open groups.
Note: Though we recommend waiting until the 0.3.5 release, if you are adventurous and want to enable blinding earlier on your open group server, you can find the setting in the sogs.ini configuration file.
A new frontier: Deprecating legacy servers
Many operators are already running the updated PySOGS software. As the name suggests, PySOGS is a new codebase for open groups written in Python — a choice which has greatly hastened development timelines for open group servers. Although the date is not yet finalised, the Session client will stop supporting Legacy SOGS and older PySOGS releases at some point in the next few months. We recommend you upgrade to PySOGS 0.3.5 as soon as you can.
Checking your version and upgrading
If you are a SOGS operator but you are not sure what kind of Session Open Group Server you are currently running, checking is simple.
If you are on Legacy SOGS then this command will output a version:
root@freyr:~# session-open-group-server -V
Session Open Group Server 0.1.10
If you are on PySOGS you’ll get an error instead:
root@freyr:~# session-open-group-server -V
-bash: session-open-group-server: command not found
On PySOGS, the command to use is `
sogs`. For instance, `
sogs -L` will list your current open groups. If you are running PySOGS 0.3.0 or higher, `
sogs -V` will show the current version.
Upgrading your SOGS is also quick and easy, instructions on how to upgrade can be found on GitHub
Keep your community online
Make sure your community stays connected — watch out for the upcoming PySOGS release and upgrading to 0.3.5 as soon as you can!
In the meantime, stay tuned on our social channels, Session updates channel, and the Session open group for the most up-to-date information.
If you have any questions, feel free to reach out to us via those channels or our help centre.
Session Release Roundup #17: The long awaited syncing update
July 18, 2023 / Kee Jefferys
Protecting a Free and Secure Internet: World Press Freedom Day
May 03, 2023 / Alex Linton
Session Beta: Your all access pass.
April 19, 2023 / Wesley Sukh
Encrypted messaging apps urge for changes to the UK Online Safety Bill
April 17, 2023 / Alex Linton
Why Session is the Perfect Replacement for Wickr
January 24, 2023 / Alex Linton
Session Release Roundup #16: Trio of Changes
October 18, 2022 / Kee Jefferys