Speedify LIVE Office Hours: Q&A With Our Developers

On the 169th episode of Speedify LIVE we hold our weekly Office Hours with the Speedify Devs to talk all things Speedify, Starlink, and have some fun with tech trivia!

We take viewer questions, take a look at our last IRL stream’s performance, give some Raspberry Pi suggestions, and talk about more upcoming improvements to Speedify on the Mac and to how we work with Starlink.

Here are our 5 takeaways from our Office Hours:

1. On the 168th episode of Speedify LIVE we went IRL at the Lunar New Year celebrations in Vietnam! Here’s what we learned: bonding two 3G connections in a crowded park, with Apple Airpods for microphones, is not enough for a good quality stream. Speedify did help make the stream happen, though! Without it, we wouldn’t have had the stream at all! 
2. When it comes to the Raspberry Pi, there’s some things we can and can’t make recommendations on. When it comes to specific Pi hats, we can’t make any official recommendations, as we generally just use USB ethernet adapters instead. As for other Pi compute modules, anything that can run a Raspberry Pi OS or Ubuntu will work with Speedify. 
3. The Speedify team is hard at work on Speedify 13, coming soon! Most of the improvements will be under the hood fixes for stability and speeds, while we mostly focus on Mac related things, like our long awaited M1 support! We’re also working on more improvements around how we work with Starlink. 
4. Speaking of Starlink, we’ve been running 24/7 livestreams, testing Starlink with Speedify, and getting a lot of data out of it! We’re making a collection of that data to present to our users in a public spreadsheet including Jitter, Latency, Loss and MOS score.
5. For those running into issues accessing certain sites and services, there’s a few things you can do: first, always try different servers as it’s possible only some are being blocked. Then, you can try the Bypass feature to direct the site’s traffic around Speedify, or if you’re on Windows, MacOS or Linux you can create a custom Bypass through the CLI.