Welcome to week 12 of the Glimcap. This week we will be showing some of the progress we have been making towards the Alpha Phase 2 features, as well as going through our usual roundups of financials, metrics and wins from the previous week.
|This Week||Last Week||Diff|
Last week we covered 2 weeks metrics but this week sees a return to our usual 1 week reporting. Discord has declined again which is a continual pattern we are seeing week over week at the moment, and while this could just be natural attrition we still want to continue to monitor this.
As we said last week, that launch week hype on Twitter was starting to slow down and sure enough this week we have seen our first ever drop on Twitter. While we did have some new people follow us more unfollowed this week.
Reddit grew by 4 new users this week and Paco1342 is now starting to put the frameworks in place in terms of branding and moderation to start growing this and help it continue to grow. Growth was also seen across our Instagram and Facebook pages this week.
Users to the platform have again grown this week, up on the previous week by 367, but the MRR continues to drop. Normally we would have a graphic here to show the subscriptions in relation to MRR here however we have noticed the graph has not been accurately reflecting the churn so we are going to fix that before bringing it back to you.
One thing we have learned from monitoring these figures each week is that MRR and growth are not as directly attached as they seem, as while we have been losing active people to the platform we are not seeing the equivalent drop in revenue. However, as we have said previously MRR going down is not ideal. This is something we need to monitor and try to bring in new streamers and viewers to the platform to try and help that grow.
This is now becoming a trend of traffic going down week over week. Even page views this week are showing a significant decline from just a week ago, dropping from around 16,000 to 11,000. This decline isn’t great but we have a plan of action together and where we want to take our marketing to target that growth, we are now moving towards putting that together to get out there.
Again, we haven’t been tweeting as much so not getting the interactions of engagements. This is something which is entirely controlled by us and we know we need to continue to post and gain some momentum on events and marketing to take advantage of things. We have had some discussions in marketing around how this could look over in our discord. So although there is this continued descent it’s not cause for alarm, we are sharing it because we want to be open and transparent with you all and let you know we are creating concrete ideas now to make improvements here.
|Apr 1st-25th||Partial Glimesh Budget|
As we said earlier, MRR is down to $8160. This budget only tracks the servers at the moment as this is the only real cost we have at the moment. It also tracks both what the expenses would look like if we were paying for the server costs, and how it stands right now with our DigitalOcean credits. So far this month, 25 days in, we have earned $8480 and paid out $1800, so revenue thus far is around $6600.
Our total Digitalocean costs so far this month is $1800, this is down from last month where we had already hit this amount within the first 2 weeks, this shows that resizing our servers has really paid off. Bandwidth overages are small showing we have found a good size of servers for the website load. As we continue to grow we will scale these back up.
So as we were saying this chat reflects how things would look if we were paying for server costs, and if we were this month we would be currently $4000 in profit, but as we will have DigitalOcean credits left, we are $6600 in profit this month. This profit does not go into anyone’s pocket, no one is getting paid from that, it goes directly into the Glimesh bank account (or as it has become known, the Glimesh War Chest), so that we have money building for future processes such as marketing server upscale costs.
For those that missed our Alpha Phase 2 reveal last week (you can find more details in our dedicated blog post) we are making a push to be more accessible to viewers. When we contacted people to find out why they chose not to use glimesh, a lot of this was tied to not getting the features they wanted, lack of native viewership, technical issues and bugs. This is where the focus lies for us as we move towards Phase 2, making streams more accessible, improving video and bugs, a mobile app for accessibility and more marketing content to start to have a regular cadence on social media again.
This week we have a huge amount of wins coming from all aspects of Glimesh, so without further ado, let’s get started!
Barcxde, one of the members of our design team has been hard at work making designs for what our mobile app could look like, you can keep up to date with these in our #design channel in our Discord.
We are working on a mobile app which is focused on the video experience above all, with the ability to watch, follow, get live notifications and (once we work out how things work with Apple and Google taking their percentages) subscriptions.
We do currently have a semi functional prototype which has the ability to watch streams but the core functionality is not yet there to allow people to test this. Once it is though, and we have no idea yet when that will be, we will let people know so we can get some pre-alpha testers to report bugs so we can fix them before pushing it out.
You can also check out live streams of this app in development over on https://www.glimesh.tv/clone1018
- Packet Loss Smoothing Testing Starting Soon!
We’ve found some potential issues with the chrome browser not handling video correctly. While we are still in the early stages of investigation Dan has found that the chromium source may be handling some of the webRTC video packets incorrectly which are handling the buffer rates. Depending on what is dug up here we may be able to get some changes made, however this is still very early in the process but if you want to read up on it you can in our github.
Dan and Hayden are working on packloss smoothing for those having a minor packet loss of 2-4%. They have been working on code which can help fill missing packets and may be able to help make the video whole again, testing for this will start soon but we don’t want to make any promises until those tests have been carried out.
- New emotes are live!
Jerhenning has been the main person behind these creating these new Glimdrops so everyone should be able to use the static ones, and those who are platform subscribed should have access to the animated emotes.
Mature icon now shown on live stream and implemented in the API by Ember
Muted streams will now save the last set audio level on refresh
Standardized docker to compose workflow
One of our new developers Eein has helped implement a standardized docker to compose workflow which is easier for those wanting to work alongside us in #dev rather than having to have knowledge of elixir to get started. This will make it easier for those who want to contribute to Glimesh to jump into the code.
Overhauled the Support Site to make it more accessible for people to find information: https://www.support.glimesh.tv
New troubleshooting guide by Dan and Heiwa which is now on the support site for both OBS and SLOBS streaming issues: https://support.glimesh.tv/en-us/37-troubleshooting-guides
Article by Dan and Heiwa about how to set up recording clips locally via a replay
New Article by Chris how about to filter streams using tags when searching for content - part of our new ‘viewer help’ section: https://support.glimesh.tv/en-us/39-viewer-help
Article regarding changing your default payment method of subscriptions and platform subscriptions: https://support.glimesh.tv/en-us/5-subscriptions-payments/164-changing-default-payment-methods-channel-subscriptions
Video guides are now available for both streamers and users of the platform on the support site thanks to DigiZ and JustSimy
Don’t forget if you are having issues you can always reach out to us directly!
Check out our support site for resources, guides and FAQs
If all else fails, keep an eye on our Twitter account. We’ll post any major announcements or need to know updates there, too.