Minnit Chat – March 2020 Update

Hello everyone!

Today, we are pleased to announce a new update for Minnit Chat thanks to a ton of great feedback from Owners. While this update is a bit smaller than others due to us being hard at work on Organizations (which will support OAuth 2/SAML 2 and many other new stuff), we still wanted to work to make the service even better with some requested functionality and quality-of-life improvements.

First off: “Disable Functions” is a new suite of options to quickly disable various functions of the chat, depending on your payment plan. The options allow you to do the following:

Basic plan or higher can:

  • Disable user photos / avatars.
  • Disable Direct Messages
  • Disable nicknames

Community plan or higher can:

  • Disable the ability to add friends/view your Friends List
  • Disable the “View Profile” links
  • Disable the user list
  • Disable the display of @usernames

Pro plan or higher can:

  • Disable the ability to add users to “ignore”
  • Disable default Minnit emoji, such as (wink) or (dance). Since Pro chats can upload up to 100 JPGs/PNGs/GIFs as emoji, this is a great way to design your very own for use in the chat!
  • Disable any references to logging in/registering.

You can access these toggles here, assuming your chat is on a premium plan.

Next up, chatrooms on Pro plan are now able to change the texts of the chat directly. For instance, if you want to change the button that says “Direct Message” to “Instant Message”, you are able to do that. If you want to change the name of the Manager rank to “Supermod”, you can do that, too. Almost every single English string in the chat can be changed. You can see this by going to the “Custom Texts” section in the Chat Settings menu, assuming you’re on the Pro plan or Trial.

Finally, we’ve made a few smaller changes to other functions, such as clearing messages, so they are stored more efficiently and will result in much faster connections for chats that have lots of old messages. Other minor bug fixes and changes were made, as well.

That’s all for now! As mentioned, this is a relatively minor update, but we hope you enjoy it.

Happy chatting!

Minnit Chat – COVID19 / Coronavirus

Hello everyone.

We have seen an increase in churches, schools, and businesses sign up for Minnit Chat to stay in touch with one another, as they are unable to meet face-to-face in wake of the Coronavirus. Many remain on the Free tier as they simply do not have the means to pay anything during this concerning time.

Because of this, we wanted to lend a hand. Our standard Free tier, by default, allows up to 40 users to be in the chat at once for chats created since 2018 — but, starting now, we are more than doubling the limit. All free chats are now able to have 100 users online at once. This temporary increase will be in effect until September 15th, 2020 — after that point, the limit will decrease to 40 again.

We hope this decision to raise the limit will make it easier for you and your friends, colleagues, or other members of your community to choose to stay in touch virtually, and help prevent further spread of the virus.

Thank you.


Update: A previous version of this post stated that this would end August 1st. However, after learning that OVHcloud’s #Open_Solidarity initiative has been extended another month, and after seeing that the virus remains a global threat, it was an easy decision to make: The perks outlined above are now extended until September 15th, 2020. Thank you!

Handling “non-secure” radio streams

Hello everybody.

Earlier today, we put out this tweet mentioning that non-secure radio streams would not play in the latest version of Google Chrome when used within Minnit Chat. I wanted to take a moment to explain what exactly that means, as we’ve gotten quite a few tickets and inquiries.

First, what is a “non-secure” radio stream? A “non-secure” radio stream is one that is served over a standard HTTP connection. This protocol is incredibly unsecure, and it is very easy for others on your network, your ISP, or even a government (not necessarily your government) to view exactly what you’re doing. Secure content (HTTPS) fixes this by encrypting all data. If you are on a website that has a lock icon, like Minnit Chat, then you are on a secure and encrypted connection. If you are on a website that has the text “Not Secure”, you are on a standard HTTP connection.

What did Google do to break the radios, and why did they do it? The latest update to Google Chrome prevents secure content, like Minnit Chat, from loading non-secure content, like a vast majority of the owners’ radio streams.

The main reason they did that is simple: If you are on a website that says “Secure”, you should trust that everything you do on that page is secure. Having a “secure page” that loads a ton of scripts, assets, and other content from non-secure sources is misleading to the end-user, and, in an increasingly dangerous online world, it is important for users to know what they can trust, and what they can not trust. Google is moving in that direction by saying “If the page is secure, then it is entirely secure”. This is a good move for user privacy and security, but it does come with the sad caveat of non-secure radio streams being prevented from being streamed via the secure chat.

Now, what are the options to get the radio working again? If you own the radio station, you can put it on a server that supports the encrypted HTTPS protocol and link that in your chat settings. If you don’t know how to do that, contact your web master or hosting provider and ask about how to upgrade your service to HTTPS and to ensure that it won’t break your existing radio stream setup. Alternatively, if you embed Minnit onto your website, and your website is “Not Secure”, and you want to get the radio working again, you can embed the radio stream directly. Minnit Chat uses the standard HTML5 audio tag to broadcast content. You can put this onto your website yourself by pasting this code snippet:

<audio controls><source src="YOUR_STREAM_URL_HERE" type="audio/ogg"><source src="YOUR_STREAM_URL_HERE" type="audio/mpeg"></audio>

You can put this directly above, or below, your chat’s embed code, and a separate player will appear directly on your website. This, like our chat’s player, requires no plugins, and works great on every modern device.

Is there anything Minnit could do to fix this issue? As this is a policy that is in place by Google Chrome, and likely will be adopted by other browsers in the coming months, there is nothing we can do. The only possible option on the table is for Minnit to abandon the secure, encrypted HTTPS standard and revert back to the non-secure HTTP version, but we will never do that. That will put you, and your users, at risk of having your data viewed and your accounts at risk of being compromised. I have personally been interested in security exploits on websites since I was 11 years old, and so every single decision I make with Minnit is made with security in mind. I know that making Minnit Chat unsecure just for the radio to work is not a trade-off that owners want, and certainly not one I want.

Hopefully all of this is clear. If you have any more questions, feel free to contact Support and ask for me directly, and I will be more than happy to answer any questions you may have.

Have a great weekend, and happy chatting!