In the last months we’ve been working on a few things we know you’ll love. This is the first of many summaries in which we will share the shiniest new features, improvements and general updates.
Read receipts show up under your message and indicate whether your message has been read by the other party. They are visible in one-to-one conversations when both users have activated read receipts. Group conversations have their own settings in which read receipts can be activated. Read our separate blog on read receipts for more information and default settings.
Really quite simple. The wire desktop apps are now available in a soothing dark theme. See our dark mode blog entry for more.
Externals can now be invited to the team without granting them too much access. This is helpful when working with freelancers, or any other form of partners. For those, we have introduced a new user role in Wire Pro: Partners. These have less rights than team members but can easily find all team members and start 1:1 conversations with them. They can be added to group conversations by other team members but cannot create one or change its settings. More on our blog.
Markdown Links support
Markdown links allow users to format their own links. Share for instance a lengthy URL to an online document but simply show it as “Document”.
Example: Just like we can use markdown to create this (invalid) link on this blog: I am a long link in disguise, we can create the same on Wire.
SSO users can now see internal information of their team members in the conversation details. This may include information such as Job-title, department, entity or further contact information. To access this information a single-sign-on integration is required.
New naming convention for downloaded images
Images downloaded via Wire are now easier to locate on your device and have a new naming convention that is easier on the eye. Images will always have the naming format of “Wire Date at Time”.
Electron, used by the desktop apps, was updated to version 4.08 in order to circumnavigate the Chromium FileReader vulnerability. More information on the vulnerability can be found on Electrons blog.