<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gabe Kangas</title><link>https://gabekangas.com/</link><description>Blog posts from Gabe</description><atom:link href="https://gabekangas.com/index.xml" rel="self" type="application/rss+xml"/><item><title>Blogs</title><link>https://gabekangas.com/blog/</link><pubDate>Wed, 16 Sep 2026 00:00:00 -0800</pubDate><guid>https://gabekangas.com/blog/</guid><description/></item><item><title>I miss Twitter</title><link>https://gabekangas.com/blog/2026/09/i-miss-twitter/</link><pubDate>Wed, 16 Sep 2026 00:00:00 -0800</pubDate><guid>https://gabekangas.com/blog/2026/09/i-miss-twitter/</guid><description>&lt;p>It&amp;rsquo;s not uncommon for people to feel generally nostalgic about Twitter &amp;ldquo;before it sucked&amp;rdquo;. But that&amp;rsquo;s not what I want to talk about. I want to talk about something more specific.&lt;/p>
&lt;p>I&amp;rsquo;m on The Fediverse. It&amp;rsquo;s decentralized, independent, flexible, and awesome. There are so many people from all kinds of backgrounds and interests and we&amp;rsquo;re all part of something that legitimately makes the internet a better place instead of worse. The assorted microblogging software of The Fediverse allows people to communicate using all kinds of different tools, platforms and software. It&amp;rsquo;s how the internet should work.&lt;/p>
&lt;p>But there&amp;rsquo;s something I just can&amp;rsquo;t shake.&lt;/p>
&lt;p>I think back to the time on Twitter (before it sucked) and I would announce something I was working on, or ask a question, or seek a connection. And people would jump at the opportunity to be involved, to contribute in some way, to make introductions to other people, and so much more. It was active in a real way. People engaged actively with you, people wanted to help, to discuss, to collaborate, and to connect. I was that way with others. It was exciting to be engaged with people and cool things.&lt;/p>
&lt;p>The Fediverse is &lt;em>completely different&lt;/em>. There&amp;rsquo;s no lack of support here. People are encouraging and immensely kind, but in a very passive way.&lt;/p>
&lt;p>There&amp;rsquo;s the notion of a &amp;ldquo;ratio&amp;rdquo; on Twitter, where if a tweet receives significantly more replies than likes or retweets, it indicates that the content is unpopular. On The Fediverse I&amp;rsquo;ve discovered a new kind of ratio. I like to call it the &amp;ldquo;engagement ratio&amp;rdquo;. I might post something and get 100 likes and 50 shares of the post, and not a &lt;em>single&lt;/em> response. It feels very strange. I think &amp;ldquo;Wow, look at all these people!&amp;rdquo;, but then I realize the shares are essentially a person saying &amp;ldquo;I don&amp;rsquo;t personally care about this, but maybe somebody else will&amp;rdquo;, or &amp;ldquo;That person needs help or advice, but I&amp;rsquo;m not interested in engaging, but I&amp;rsquo;m sure somebody else will if I share it&amp;rdquo;.&lt;/p>
&lt;p>Perhaps I was on Twitter at a very specific time when the community around me was particularly engaged in an active way. But I don&amp;rsquo;t think that&amp;rsquo;s it. Twitter always rewarded you for being loud, visible, interactive and having a &amp;ldquo;personal brand&amp;rdquo;. Everyone wanted to be seen, and a part of that visibility is being actively involved with others. While that may sound negative, and it kind of is, this ultimately ended up encouraging real networking, collaboration and connection. But on The Fediverse, none of that is the case. (Most) people don&amp;rsquo;t care if others know who they are. There&amp;rsquo;s (generally) no loudest person in the room. It&amp;rsquo;s not about being seen and having a personal brand. Most people don&amp;rsquo;t even use their real names or want to be publicly identifiable. In general it&amp;rsquo;s a culture that&amp;rsquo;s more private and less performative. I think that&amp;rsquo;s awesome. But I think theres a side-effect of that where things become far more passive.&lt;/p>
&lt;p>Or maybe I&amp;rsquo;m just not interesting enough or none what I do is of any interest to anyone. But I don&amp;rsquo;t think that&amp;rsquo;s the case. I &lt;em>know&lt;/em> people really support Owncast, for example. But If I post &amp;ldquo;Looking for somebody to test X&amp;rdquo; or &amp;ldquo;looking for design help, give me recommendations&amp;rdquo; or something similar I know people want me to succeed, people will click &amp;ldquo;like&amp;rdquo; to show their support, but they&amp;rsquo;ll never respond to your message. They&amp;rsquo;ll share it assuming that the people they share it with will engage. But everyone thinks that, so nobody does.&lt;/p>
&lt;p>This isn&amp;rsquo;t to try to change anything, I understand that The Fediverse is very different, and the personalities and interests and motivations are also very different. And maybe my experience is unique, and everyone else is having a completely different experience. But I wanted to jot my notes down and reflect on my thoughts and experiences anyway because it&amp;rsquo;s been on my mind. It&amp;rsquo;s also not to say that The Fediverse is generally unsupportive. It&amp;rsquo;s just a different kind of support, one that&amp;rsquo;s less visible and less interactive. It&amp;rsquo;s quiet support.&lt;/p>
&lt;p>All the active networking and loud personalities are probably on Linkedin these days. Please don&amp;rsquo;t make me do that.&lt;/p></description></item><item><title>Owncasts for iOS and tvOS get updates!</title><link>https://gabekangas.com/blog/2026/08/owncasts-for-ios-and-tvos-get-updates/</link><pubDate>Sun, 16 Aug 2026 00:00:00 -0800</pubDate><guid>https://gabekangas.com/blog/2026/08/owncasts-for-ios-and-tvos-get-updates/</guid><description>&lt;p>In 2024 &amp;ldquo;Owncasts&amp;rdquo; for iOS was released as a side project to give a native interface on the iPhone and AppleTV. I highly recommend you read the first post in this series: &lt;a href="https://gabekangas.com/blog/2024/01/owncasts-a-new-ios-and-tvos-application-for-viewing-owncast-powered-live-video-streams/" >Owncasts for iOS and tvOS&lt;/a>. It will detail what the goal with the application were, and how it came to life.&lt;/p>
&lt;p>It was something that wasn&amp;rsquo;t directly connected to or maintained by the Owncast project. And it hadn&amp;rsquo;t been touched much since then. But I did have a list of things I wished it could do. But I just never got to them.&lt;/p>
&lt;p>Until now! Today a new release is out, and it finally has most of the functionality originally wished for.&lt;/p>
&lt;h2 id="you-can-chat">
You can chat!
&lt;a class="heading-link" href="#you-can-chat">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>You can finally chat while mobile. On AppleTV you can just follow along, since typing with a remote really sucks. It doesn&amp;rsquo;t support chat auth, though. So if people find themselves using it, let me know.&lt;/p>
&lt;h2 id="mobile-live-streaming">
Mobile live streaming!
&lt;a class="heading-link" href="#mobile-live-streaming">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>If you&amp;rsquo;re an Owncast streamer, you can now stream live FROM the application. Put in your stream details into settings, and you can do live mobile live streaming. I think that&amp;rsquo;s neat. Let me know how it works for you. The real world network connectivity makes this kind of challenging, so I&amp;rsquo;m curious how it goes.&lt;/p>
&lt;h2 id="ipad-no-longer-sucks">
iPad no longer sucks!
&lt;a class="heading-link" href="#ipad-no-longer-sucks">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>It used to suck. Now (especially in landscape) it&amp;rsquo;s pretty nice.&lt;/p>
&lt;p>&lt;strong>So check it out&lt;/strong> and let know what you think. As previously stated, this is a side project with no promises of features or attention. But if people use it, I&amp;rsquo;ll keep at it.&lt;/p>
&lt;p>&lt;a href="https://apps.apple.com/us/app/owncasts/id6451178968" class="external-link" target="_blank" rel="noopener">https://apps.apple.com/us/app/owncasts/id6451178968&lt;/a>&lt;/p>
&lt;center>
&lt;img src="https://gabekangas.com/blog/images/iphone-01-home.webp" width="30%" alt="Owncasts iPhone home screen"/>
&lt;img src="https://gabekangas.com/blog/images/iphone-02-server.webp" width="30%" alt="Owncasts iPhone server screen"/>
&lt;img src="https://is1-ssl.mzstatic.com/image/thumb/PurpleSource221/v4/84/b1/61/84b1612e-5f49-8297-2c01-a715832734f3/iphone-03-server-chat.png/460x996bb.webp" width="30%" alt="Owncasts iPhone server chat screen"/>
&lt;/center>
&lt;center>
&lt;img src="https://gabekangas.com/blog/images/ipad-01-home-landscape.webp" width="70%" alt="Owncasts iPad home screen"/>
&lt;/center>
&lt;center>
&lt;img src="https://gabekangas.com/blog/images/appletv-01-home.webp" width="45%" alt="Owncasts Apple TV home screen"/>
&lt;img src="https://gabekangas.com/blog/images/appletv-03-server-chat.webp" width="45%" alt="Owncasts Apple TV server chat screen"/>
&lt;/center></description></item><item><title>Five Years of Owncast</title><link>https://gabekangas.com/blog/2025/05/five-years-of-owncast/</link><pubDate>Mon, 12 May 2025 00:00:00 +0000</pubDate><guid>https://gabekangas.com/blog/2025/05/five-years-of-owncast/</guid><description>&lt;center>
&lt;img src="https://gabekangas.com/blog/images/5-years-of-owncast-owncat.webp" alt="Five years of Owncast" width="40%"/>
&lt;/center>
&lt;p>It&amp;rsquo;s been a year since I&amp;rsquo;ve written a blog post. So that must mean it&amp;rsquo;s an Owncast anniversary! But this time, it&amp;rsquo;s a bigger one. Five years!&lt;/p>
&lt;h2 id="the-obligatory-past-5-years-section">
The Obligatory &amp;ldquo;Past 5 Years&amp;rdquo; Section
&lt;a class="heading-link" href="#the-obligatory-past-5-years-section">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>Five years is a long time, but it went by really fast. I&amp;rsquo;ve had a chance to work on a lot of cool things, travel to cool places, and meet a lot of cool people.&lt;/p>
&lt;p>I could write a bunch here about five years of building Owncast, but I &lt;a href="https://gabekangas.com/blog/2024/05/today-marks-four-years-of-owncast/" >wrote a lot last year&lt;/a>. And that all holds true, so I won&amp;rsquo;t repeat myself here. Instead I&amp;rsquo;m going to point you at the most recent edition of the &lt;a href="https://owncast.ghost.io/owncast-newsletter-may-2025/" class="external-link" target="_blank" rel="noopener">Owncast newsletter&lt;/a> where I shared a bunch of thoughts with Kit, the editor. Now is a great time for you to sign up for it if you haven&amp;rsquo;t. Kit does a great job with it, and it only comes out once a month, or every other month. So it&amp;rsquo;s low traffic, and it&amp;rsquo;s a great way to keep up with the project. And as a bonus, I don&amp;rsquo;t write it, so it&amp;rsquo;s a chance to not have to listen to me blab about Owncast for a change.&lt;/p>
&lt;h2 id="owncast-merch-store">
Owncast Merch Store
&lt;a class="heading-link" href="#owncast-merch-store">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>As long as Owncast has been a project people have asked for a way to get stickers or a t-shirt for themselves. And I never had a good answer for them. At conferences and events I would bring things to pass out, and contributors and supporters could get a t-shirt. But that was always easy because it didn&amp;rsquo;t require charging people, having a way to manage that money, shipping hassles, and there were no variety of products. Having an actual store would be a big change that I was never ready for.&lt;/p>
&lt;p>So I figured for our 5th anniversary, it was time to finally do it. Work for it began many months ago, and it required the work of multiple people to make happen. A special huge thank you to &lt;a href="https://donaberger.xyz/" class="external-link" target="_blank" rel="noopener">Mitch&lt;/a> and &lt;a href="https://gingervitis.net/" class="external-link" target="_blank" rel="noopener">Ginger&lt;/a> on the design side and Grace from &lt;a href="https://oscollective.org/" class="external-link" target="_blank" rel="noopener">Open Source Collective&lt;/a> on the finances side.&lt;/p>
&lt;p>But we did it, the &lt;a href="https://merch.owncast.online" class="external-link" target="_blank" rel="noopener">Owncast Merch Store&lt;/a> is live! You can get an assortment of Owncast branded items. Some of which I had to learn how to ship from my apartment. So now I have a shipping label printer and a stack of shipping materials.&lt;/p>
&lt;p>One of the t-shirts is a &lt;a href="https://merch.owncast.online/category/clothing" class="external-link" target="_blank" rel="noopener">limited time, 5-year anniversary shirt&lt;/a>, designed by &lt;a href="https://donaberger.xyz/" class="external-link" target="_blank" rel="noopener">Mitch&lt;/a>. I wanted something to commemorate the occasion, and it&amp;rsquo;s super fun. So that will be available as long as it&amp;rsquo;s available.&lt;/p>
&lt;p>I&amp;rsquo;ve been wearing the &lt;a href="https://merch.owncast.online/product/owncast-embroidered-logo-zip-up-hoodie" class="external-link" target="_blank" rel="noopener">embroidered Owncast hoodie&lt;/a> pretty much every day now for a while. It&amp;rsquo;s super comfortable. And when I was in Nashville in February I wore the &lt;a href="https://merch.owncast.online/product/ribbed-knit-beanie" class="external-link" target="_blank" rel="noopener">beanie&lt;/a> the entire time because it was freezing out.&lt;/p>
&lt;p>With each purchase a small portion of the price will be a donation to the Owncast project itself. Most of the price is to pay for the actual physical item, however. Previously there was no good way to manage that money, it would have had to go to me directly, and I would have had to then donate each purchase back to Owncast. But something came up that allowed us to do this. We are an early adopter of a new feature with &lt;a href="https://oscollective.org/" class="external-link" target="_blank" rel="noopener">Open Source Collective&lt;/a> where we have a virtual bank account. So when a purchase is made, that money goes into the account, and that gets deposited directly into our Open Source Collective balance without being funneled through me first. The only downside of the process is the other direction. I have to personally expense the cost of every item as its purchased, otherwise I&amp;rsquo;m paying for the manufacturing of every item. That will get tedious, but quite expensive if I don&amp;rsquo;t do it. Even just buying all the different versions of the test items the past few months got expensive.&lt;/p>
&lt;p>I encourage you to check it out. I hope you find something you like. And if you do, share a picture on the Fediverse, or wherever. I&amp;rsquo;d love to see it.&lt;/p>
&lt;h3 id="owncat">
Owncat
&lt;a class="heading-link" href="#owncat">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h3>
&lt;p>Did you see &lt;a href="https://owncast.bigcartel.com/product/owncat-unisex-hoodie" class="external-link" target="_blank" rel="noopener">Owncat&lt;/a>? He&amp;rsquo;s super chill. Owncat rules.&lt;/p>
&lt;h2 id="new-owncast-fediverse-account">
New Owncast Fediverse account
&lt;a class="heading-link" href="#new-owncast-fediverse-account">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>When Fosstodon was having it&amp;rsquo;s little piece of &lt;a href="https://hub.fosstodon.org/" class="external-link" target="_blank" rel="noopener">drama&lt;/a> I toyed with the idea of just pulling the Owncast Fediverse account completely. We don&amp;rsquo;t really post much. But people were vocal that they really didn&amp;rsquo;t want that to happen. And with the 5 year anniversary on the horizon, I figured it was good to be able to reach out. So instead, I thought I&amp;rsquo;d double down.&lt;/p>
&lt;p>I moved Owncast off of Fosstodon to a &lt;a href="https://social.owncast.online/@owncast" class="external-link" target="_blank" rel="noopener">new private server&lt;/a>, just like I had done with my personal account. Fosstodon hasn&amp;rsquo;t been great to me personally in the past and this was a good excuse to get off of it. Unfortunately, due to some issue with Mastodon, we lost our followers. So we went from over 5,000 to 800. So if you were following us before, you&amp;rsquo;ll need to re-follow it again now on the new account. Funny how it went from &amp;ldquo;should we shut down the account?&amp;rdquo; to &amp;ldquo;Please follow us again&amp;rdquo; in a matter of days.&lt;/p>
&lt;h2 id="onward-and-upward">
Onward and Upward
&lt;a class="heading-link" href="#onward-and-upward">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>I look forward to the next year, and the next five years. I want to thank everyone who&amp;rsquo;ve allowed me a chance to work on Owncast. It only exists because people have uses for it, and and they want it to exist. So thank you to everyone who has used Owncast, and especially those who&amp;rsquo;ve contributed in some way. Whether that be code, documentation, support, translations, or just sharing it with a friend. It all matters.&lt;/p>
&lt;p>I haven&amp;rsquo;t been perfect, but I appreciate all of the patience and grace I&amp;rsquo;ve been given in doing my best with Owncast. I hope you can all tell how much it matters to me, and the place that all of the support plays. I don&amp;rsquo;t take any of it for granted. I absolutely know that kind of thing can change in a second any given day. But as long as that doesn&amp;rsquo;t happen, I hope to continue to improve and grow the project, and I hope you&amp;rsquo;ll keep joining me for the ride.&lt;/p></description></item><item><title>Today marks four years of Owncast</title><link>https://gabekangas.com/blog/2024/05/today-marks-four-years-of-owncast/</link><pubDate>Thu, 23 May 2024 00:00:00 +0000</pubDate><guid>https://gabekangas.com/blog/2024/05/today-marks-four-years-of-owncast/</guid><description>&lt;p>May 23rd, 2024 marks the 4th anniversary of the first commit of Owncast, aptly titled: “WIP”.&lt;/p>
&lt;h2 id="wip">
WIP
&lt;a class="heading-link" href="#wip">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>It was a bit before exactly four years ago when I actually started working on it in earnest, but not that far before. I remember duct taping a proof of concept together, opening my laptop&amp;rsquo;s web port to the public internet, messaging somebody and asking “Could you open this URL in VLC or QuickTime or something?”. Since there was no web interface or player, I just wanted to see if video would play for somebody over the internet. When I was told it worked, I went from asking “I wonder if this is possible” to knowing it was possible.&lt;/p>
&lt;h2 id="what-specifically-was-happening-four-years-ago">
What specifically was happening four years ago?
&lt;a class="heading-link" href="#what-specifically-was-happening-four-years-ago">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>For fun, I took a look at what the first month of Owncast commits looked like, and I don&amp;rsquo;t remember things moving so fast. At that time, it already:&lt;/p>
&lt;ul>
&lt;li>Had native support for serving video via S3 compatible providers.&lt;/li>
&lt;li>There were two additional contributors apart from me.&lt;/li>
&lt;li>Chat had a fair bit of functionality.&lt;/li>
&lt;li>Video transcoding was completely customizable.&lt;/li>
&lt;li>It had persistent viewer statistics.&lt;/li>
&lt;li>Documentation existed, including a quickstart guide.&lt;/li>
&lt;li>A build script and Dockerfile allowed for relatively easy building.&lt;/li>
&lt;li>You could customize your page content with Markdown.&lt;/li>
&lt;/ul>
&lt;p>Here are some other things that were going on at that time that never made it to where we are now:&lt;/p>
&lt;ul>
&lt;li>It had native support for serving video via IPFS.&lt;/li>
&lt;li>The web interface was built with Vue + Tailwind.&lt;/li>
&lt;li>Your chat username color was determined by a color hash of your username itself.&lt;/li>
&lt;li>Chat had user avatars.&lt;/li>
&lt;li>Chat showed embeds when links were shared, including images.&lt;/li>
&lt;/ul>
&lt;h2 id="where-i-started-is-not-where-its-been">
Where I started is not where it&amp;rsquo;s been
&lt;a class="heading-link" href="#where-i-started-is-not-where-its-been">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>It&amp;rsquo;s remarkable how fast things move at first on any kind of project, and then as it starts to take shape it slows down and becomes a bit more methodical. Once the core functionality is built and it “works”, then you have to think about what&amp;rsquo;s next. I suppose Owncast could have stopped right there. But I wanted it to be even easier to use, and more customizable. The more people who started using it, the more feedback I&amp;rsquo;d get, I started to get a picture of the long-term direction of the project and its features. And that direction is still what we&amp;rsquo;re going from today. I wouldn&amp;rsquo;t blame you if you thought I didn&amp;rsquo;t listen to your suggestions, but I promise that&amp;rsquo;s not true. The specific thing you request might not happen, but the spirit of what you&amp;rsquo;re asking for heavily influences the trajectory of the project, and can turn into something that&amp;rsquo;s useful for a wider user base.&lt;/p>
&lt;p>Four years ago, Owncast to me, was a free and open source, self-hosted live video server. And since people who live stream also often enjoy having chat, it would be useful to bundle in a little optional minimal chat side feature as well. But the focus was always the video. It&amp;rsquo;s funny how much time and attention has gone into web interfaces (three entirely different implementations!) and chat over these years, when that has nothing to do with opening VLC and playing back a video stream. It&amp;rsquo;s still a balancing act to this day, since some people care very, very much about chat, social features, the public directory, and interactivity. Others aren&amp;rsquo;t concerned with those at all.&lt;/p>
&lt;h2 id="whats-up">
What&amp;rsquo;s up?
&lt;a class="heading-link" href="#whats-up">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>It&amp;rsquo;s never a good time, but I&amp;rsquo;m looking at the backend codebase that began four years ago. As with anything that was started very small, and you build on top of it long enough, there&amp;rsquo;s a point where at least some changes need to be made. Primarily because some of the things that are on our roadmap simply aren&amp;rsquo;t possible with how the backend is architected. So while it&amp;rsquo;s a messy undertaking, I think it&amp;rsquo;s a valuable one, and it&amp;rsquo;s happening now, so the really cool stuff can continue to get built after that.&lt;/p>
&lt;h2 id="thank-you">
Thank You
&lt;a class="heading-link" href="#thank-you">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>Thank you for the four-year journey. Your patience, your kindness, your contributions, your feedback, your encouragement, your donations, and for sharing your Owncast-powered live streams with me. Every so often I look at a screen full of those streams and I can&amp;rsquo;t believe I had some small part in helping you build them. It continues to mean the world to me that you let me be involved.&lt;/p>
&lt;p>I&amp;rsquo;m still excited about Owncast every day. I can&amp;rsquo;t say there hasn&amp;rsquo;t been periods of burnout, and doubt. And if I didn&amp;rsquo;t have an opportunity to see you out there using Owncast, maybe some of those periods would have been the end of it. But all of you keep it alive. At the end of the day, Owncast only exists because you use it. Everything else is an implementation detail.&lt;/p>
&lt;p>Here&amp;rsquo;s to another four, five, ten years when Owncast will still be a “WIP”.&lt;/p></description></item><item><title>Owncasts - A new iOS and tvOS application for viewing Owncast-powered live video streams</title><link>https://gabekangas.com/blog/2024/01/owncasts-a-new-ios-and-tvos-application-for-viewing-owncast-powered-live-video-streams/</link><pubDate>Sun, 14 Jan 2024 09:46:12 -0800</pubDate><guid>https://gabekangas.com/blog/2024/01/owncasts-a-new-ios-and-tvos-application-for-viewing-owncast-powered-live-video-streams/</guid><description>&lt;h2 id="owncast-is-server-software-thats-it">
Owncast is server software. That&amp;rsquo;s it
&lt;a class="heading-link" href="#owncast-is-server-software-thats-it">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>First off, I want to clarify: &lt;a href="https://owncast.online" class="external-link" target="_blank" rel="noopener">Owncast&lt;/a> is server software for anybody to run their own, independent, decentralized, completely standalone video streams. It provides some additional features that streamers and their viewers can use, but at its core it&amp;rsquo;s a piece of video server software. That&amp;rsquo;s what I, personally, care about, and that&amp;rsquo;s primarily the value I want the project to offer you. Everything else is secondary.&lt;/p>
&lt;center>
&lt;a href="https://apps.apple.com/us/app/owncasts/id6451178968?platform=iphone">
&lt;img src="https://gabekangas.com/blog/images/owncasts-logo.jpeg" width="70%" />
&lt;/a>
&lt;/center>
&lt;h2 id="the-owncast-directory">
The Owncast Directory
&lt;a class="heading-link" href="#the-owncast-directory">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>With that out of the way: Early on, mostly as an experiment, I built the &lt;a href="https://directory.owncast.online" class="external-link" target="_blank" rel="noopener">Owncast directory&lt;/a>. Not because Owncast should in any way be a centralized place to discover live video streams, but as a little side project to display examples of what Owncast is being used for by different people. I figured Owncast is a bit of a new concept, so being able to show how other people are using it might help clarify things. I never treated this as an “official” offering, or some kind of service to rival other services. I treated it like it could go away at any time and Owncast, at its core, wouldn&amp;rsquo;t change one bit. People would still be running their independent live streams without any impact. Because that&amp;rsquo;s how it&amp;rsquo;s supposed to work.&lt;/p>
&lt;p>Since then, I&amp;rsquo;ve been personally uneasy about having any centralized tools for Owncast streamers or viewers. But, I can&amp;rsquo;t argue that this directory does offer some nice to haves, and I do think people appreciate it. It fulfills a want, even if it&amp;rsquo;s not a need. I guess that&amp;rsquo;s ok. I do have some plans to expand how the directory works so it&amp;rsquo;s less centralized, is powered by ActivityPub, and enables anybody to do their own thing. But that&amp;rsquo;s a topic for another day.&lt;/p>
&lt;p>I never intended to expand the Owncast side projects further than that. But time went on, and I listened to viewers, and I saw a wider audience grow. More people who are used to YouTube and Twitch wanting to watch Owncast-powered streams, but wish they had similar tooling to do so.&lt;/p>
&lt;center>
&lt;img src="https://gabekangas.com/blog/images/owncasts-ios-browse-live.jpeg" width="30%"/>
&lt;img src="https://gabekangas.com/blog/images/owncasts-ios-browse-offline.jpeg" width="30%"/>
&lt;img src="https://gabekangas.com/blog/images/owncasts-ios-stream-portrait.jpeg" width="30%"/>
&lt;/center>
&lt;h2 id="i-want-for-you-something-i-cant-give-you">
I want for you something I can&amp;rsquo;t give you
&lt;a class="heading-link" href="#i-want-for-you-something-i-cant-give-you">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>The fact that Owncast, as a project, doesn&amp;rsquo;t have any control over people&amp;rsquo;s servers is essential to me. It&amp;rsquo;s built on standards, so people on any platform, using a multitude of common applications, can watch any Owncast-powered stream. You could even build your own application built specifically for your stream. You don&amp;rsquo;t need me. Likewise, you don&amp;rsquo;t need the directory. Everything already exists for you to do your thing.&lt;/p>
&lt;p>I&amp;rsquo;ve heard stories of non-technical people refusing to watch an Owncast-powered stream because they like watching on their TVs or phone, and there&amp;rsquo;s no Owncast application they can simply download like they&amp;rsquo;re used to. I&amp;rsquo;ve wished streamers could say &amp;ldquo;Just search the app store for X and press play&amp;rdquo;. But I&amp;rsquo;m aware nobody is going to go build their own mobile apps.&lt;/p>
&lt;p>But I&amp;rsquo;ve always wished they did. I&amp;rsquo;ve always hoped that every Owncast streamer could have their own native applications to make it super easy for their viewers to watch their streams. I know the open web is super important, but I find native apps to be a really great experience, especially when it comes to media. I want Owncast servers to directly notify their viewers when they go live, and I want a way for people to watch on the TV without having to &amp;ldquo;cast&amp;rdquo; (I hate that word so much, this isn&amp;rsquo;t fishing).&lt;/p>
&lt;p>I thought about offering templated source code for a native app. Owncast streamers could just fill in the config with their server URL and they&amp;rsquo;d have their own app. But no matter how much I wish that would happen, I know streamers would never go through the effort to submit their own native app to the app stores. Everyone having their native app experience wasn&amp;rsquo;t going to happen, regardless how much I want it to. And given this is all in the spirit of independence and decentralization, that&amp;rsquo;s about all I can offer in that respect. I can&amp;rsquo;t do it for you.&lt;/p>
&lt;h2 id="i-didnt-mean-to-build-this-for-you">
I didn&amp;rsquo;t mean to build this for you
&lt;a class="heading-link" href="#i-didnt-mean-to-build-this-for-you">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>Many months ago, due to a handful of personal reasons, I waned to do a little Apple development. I thought it&amp;rsquo;d be fun to build a little application for the AppleTV to make watching Owncast streams easier for me. And it doesn&amp;rsquo;t take a nuclear scientist in 1945 to know where this story goes from here. Within a couple of days I had built a pretty nice way to watch Owncast-powered streams on iOS and the AppleTV.&lt;/p>
&lt;p>I didn&amp;rsquo;t really know where I was going from there, but I found myself adding support for more of the Owncast APIs, many of the features that exist on the web, push notifications, and more.&lt;/p>
&lt;p>While the dream of every streamer having their own application wasn&amp;rsquo;t going to be possible, I could supply one application that is built for accessing people&amp;rsquo;s servers, even if they&amp;rsquo;re not publicly listed on the directory. But I&amp;rsquo;d have to be ok with being a gatekeeper of this single application. And honestly, I&amp;rsquo;m not really that ok with it. But I can try anyway.&lt;/p>
&lt;p>So here we are. A new experimental side project for Owncast viewers on iOS and tvOS. I call it &amp;ldquo;Owncasts&amp;rdquo;, because it&amp;rsquo;s just a place where you can watch Owncast-powered streams. It&amp;rsquo;s not &amp;ldquo;Owncast for iOS&amp;rdquo;. Owncast is server software.&lt;/p>
&lt;p>If you don&amp;rsquo;t like it, please pretend it doesn&amp;rsquo;t exist. If you don&amp;rsquo;t have Apple hardware, nothing changes for you. If you have an iPhone and don&amp;rsquo;t see the value in this, that&amp;rsquo;s absolutely fine. I&amp;rsquo;m not judging this by any success criteria, and I don&amp;rsquo;t know what, if anything, is next for it.&lt;/p>
&lt;center>
&lt;img src="https://gabekangas.com/blog/images/owncast-tvbrowse-profile.jpeg" width="70%"/>
&lt;/center>
&lt;h2 id="the-unfortunate-nature-of-apple-push-notifications">
The unfortunate nature of Apple Push Notifications
&lt;a class="heading-link" href="#the-unfortunate-nature-of-apple-push-notifications">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>Unfortunately, if your Owncast server is not listed on the directory, this application will not be able to receive push notifications on behalf of your live stream. In this case it&amp;rsquo;s the directory that sends out the notifications, and if the directory doesn&amp;rsquo;t know about your server, and doesn&amp;rsquo;t know when you go live, then it simply can&amp;rsquo;t be helpful in that regard.&lt;/p>
&lt;p>I hate that this is the case. I wish every individual Owncast server could send its own push notifications, but due to how they work that&amp;rsquo;s simply imposable. This is a case where some centralization is required for this feature, and you cannot be 100% private and still take advantage of it. I&amp;rsquo;m sorry. I feel bad about it.&lt;/p>
&lt;center>
&lt;img src="https://gabekangas.com/blog/images/owncasts-ios-apns.jpeg" width="30%"/>
&lt;img src="https://gabekangas.com/blog/images/owncasts-ios-stream-portrait-menu.jpeg" width="30%"/>
&lt;/center>
&lt;h2 id="decentralized-user-interfaces">
Decentralized user interfaces
&lt;a class="heading-link" href="#decentralized-user-interfaces">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>One thing I&amp;rsquo;d like to see more of is the idea of a single interface of true decentralized content. We&amp;rsquo;re so used to user interfaces of centralized content. Almost every interface displays an array of content that is controlled exclusively by the server who&amp;rsquo;s displaying it. Every stream you see listed on Twitch is controlled by Twitch, every movie you see on Netflix is controlled by Netflix, every image on Instagram is controlled by Instagram.&lt;/p>
&lt;p>There aren&amp;rsquo;t many real examples of decentralized interfaces left. An RSS reader is a good example of a single interface full of content pulled in from different places. Or a Podcast client that&amp;rsquo;s downloading Podcasts from different places. Search engines fit this definition on the web. There used to be web directories of content, that&amp;rsquo;s how Yahoo got its start. You click on a link and it brings you to somewhere completely disconnected from the place you came from. That&amp;rsquo;s how the internet is supposed to work! All linked together, but not controlled by any one entity.&lt;/p>
&lt;p>This is what the directory has always been, and this is what &amp;ldquo;Owncasts&amp;rdquo; is. It&amp;rsquo;s just an interface trying to give you another way to help you consume decentralized content. When you add your own, private, streams to the application, you can almost treat it like a purpose built web browser. You put in an Owncast-powered URL, you can consume that content.&lt;/p>
&lt;center>
&lt;img src="https://gabekangas.com/blog/images/owncast-tvbrowse-live.jpeg" width="70%"/>
&lt;/center>
&lt;h2 id="what-is-this-not">
What is this not?
&lt;a class="heading-link" href="#what-is-this-not">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>You might be thinking &amp;ldquo;Cool, lots of Fediverse adjacent projects have iOS apps now!&amp;rdquo; No.&lt;/p>
&lt;p>Mastodon, the company, has an iOS app for their product. Pixelfed, has an iOS app, PeerTube is starting work on an iOS app. &lt;strong>This is not like &lt;em>any&lt;/em> of those.&lt;/strong>&lt;/p>
&lt;p>Those are dedicated focuses, with dedicated developers. Those organizations have those applications on their roadmap and feel they are important to drive their vision forward. Those have Jira boards and meetings and budgets. Those have designers. Those are investments into the future of their products and are important to them.&lt;/p>
&lt;p>That&amp;rsquo;s not what this is for Owncast. I don&amp;rsquo;t feel that about this. I don&amp;rsquo;t feel that about the directory, or any of the side projects that are centralized by Owncast as a project, or me as an individual. The only thing that matters is that you have server software to stream with.&lt;/p>
&lt;center>
&lt;img src="https://gabekangas.com/blog/images/owncasts-ios-stream-landscape.jpeg" width="70%">
&lt;/center>
&lt;h2 id="the-long-long-road-of-rejections">
The long, long road of rejections
&lt;a class="heading-link" href="#the-long-long-road-of-rejections">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>&lt;a href="https://social.gabekangas.com/notice/AatxyxMNMccZlyuXJ2" class="external-link" target="_blank" rel="noopener">I posted a couple months ago how I had given up on this project&lt;/a> because Apple found every possible reason to reject it, and I was not making any progress. But I took some time away, and I swapped out my feeling of defeat for defiance and kept at it. One law firm, one conversation with Craig Hockenberry, a series of appeals, and a bunch of creative workarounds later, somehow I made it over the finish line.&lt;/p>
&lt;p>I don&amp;rsquo;t want this to be a negative post about how much Apple sucks, but you might be interested in a high level list of a couple of the crazier rejection reasons.&lt;/p>
&lt;ul>
&lt;li>Apple said I was illegally accessing the Owncast Directory. The same directory the Owncast project itself operates.&lt;/li>
&lt;li>Any Owncast server that had a &amp;ldquo;Donate&amp;rdquo; link caused this application to get rejected, because Apple said it was it &amp;ldquo;collecting money without using in-app purchases&amp;rdquo;.&lt;/li>
&lt;li>It&amp;rsquo;s Apple, so of course there has to be a way to &amp;ldquo;report&amp;rdquo; a server, even though that doesn&amp;rsquo;t make much sense in a decentralized world. But if somebody does report one, it&amp;rsquo;ll send me a message. And like usual, if somebody deserves to be removed from the directory they will.&lt;/li>
&lt;li>Apple said I had no rights to show any of the streams listed in the directory in the application. Note they don&amp;rsquo;t care about the &lt;em>content&lt;/em> in the streams, just the ownership of the streams themselves.&lt;/li>
&lt;li>Apple at one point rejected the app and said the application shouldn&amp;rsquo;t even exist, because people should use the web version instead. I&amp;rsquo;m not joking.&lt;/li>
&lt;/ul>
&lt;center>
&lt;img src="https://gabekangas.com/blog/images/owncast-tvbrowse-offline.jpeg" width="70%"/>
&lt;/center>
&lt;h2 id="nsfa">
NSFA
&lt;a class="heading-link" href="#nsfa">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>Any servers marked as NSFW on the directory get filtered out of the application completely. This should be no surprise. Apple doesn&amp;rsquo;t like bad words or naughty bits.&lt;/p>
&lt;p>So if you&amp;rsquo;ve set your server as NSFW for no reason, you might want to reevaluate that. Though, of course, you can manually add any Owncast-powered live stream to the app, regardless if it&amp;rsquo;s NSFW or not. So go nuts.&lt;/p>
&lt;h2 id="so-now-what">
So, now what?
&lt;a class="heading-link" href="#so-now-what">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>Like the directory, I don&amp;rsquo;t expect this application to have super active development. Bugs will be fixed, and as new features get added to Owncast they might show up natively in the application as well. We&amp;rsquo;ll have to see.&lt;/p>
&lt;p>It&amp;rsquo;s not the most beautiful application in the world, as UI design has never been something I&amp;rsquo;m terribly good at. But I hope it&amp;rsquo;s functional enough. Maybe that can improve if there are specific things that come up, but I don&amp;rsquo;t anticipate the design of a side project being a focus for anybody.&lt;/p>
&lt;p>I thought about adding native chat. But that one addition has so many requirements, and is a large amount of additional work, with the different forms of authentication, and moderation, and text formatting, and handling of custom emoji and all of that. I did experiment with embedding the web chat into the application as a shortcut, but that&amp;rsquo;s a pretty lousy experience. Nobody should be surprised that web in a mobile app sucks. But maybe, one day, I&amp;rsquo;ll put in the substantial work to put in real chat if people cared enough. I think people might like that, but I&amp;rsquo;m not sure if it&amp;rsquo;d be enough people. You can let me know, and we can all play it by ear.&lt;/p>
&lt;p>You might notice this application is not open source, in the same way the directory is not open source. Why? Because neither of these projects got the attention and the dedication that the Owncast server software gets, and it would be irresponsible for me to say they are an open source project. They are not. You would not be able to build them, and I would not be able to support you if you tried. No documentation, no tests, no support, no even the littlest amount of thinking about anybody building and running it other than me. That&amp;rsquo;s not open source. It&amp;rsquo;s a true side project that I didn&amp;rsquo;t know if I would get approved, or would ever ship.&lt;/p>
&lt;p>All this being said, while I don&amp;rsquo;t plan on it, don&amp;rsquo;t be surprised if I accidentally build the Android version some day. But again, this all depends if this kind of thing is useful to people. The Owncast project is not in the business of building mobile applications, but it is in the business of helping people get their live streams out to the world. So if this helps, great. If not, that&amp;rsquo;s ok too.&lt;/p>
&lt;p>At the very least this won&amp;rsquo;t be the last conversation around purpose-built applications for viewing Owncast-powered live video streams.&lt;/p>
&lt;p>Keep on streamin&amp;rsquo;. Or viewin&amp;rsquo;. Or whatever you do, as long as it&amp;rsquo;s cool, keep doing some more of that.&lt;/p>
&lt;p>&lt;a href="https://apps.apple.com/us/app/owncasts/id6451178968?platform=iphone" class="external-link" target="_blank" rel="noopener">Owncasts for iOS and tvOS&lt;/a>&lt;/p>
&lt;h2 id="thank-yous">
Thank yous
&lt;a class="heading-link" href="#thank-yous">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>&lt;a href="https://blog.iconfactory.com/author/craig/" class="external-link" target="_blank" rel="noopener">Craig Hockenberry&lt;/a> from &lt;a href="https://apps.iconfactory.com/" class="external-link" target="_blank" rel="noopener">Icon Factory&lt;/a> helped me work around one of the iOS guidelines I was having problems getting approvals with. This application would not have made it through app review without him.&lt;/p>
&lt;p>&lt;a href="https://yannicklung.com/" class="external-link" target="_blank" rel="noopener">Yannik Lung&lt;/a> did the icon design for the iOS and tvOS applications and I absolutely love how they came out.&lt;/p>
&lt;p>The &lt;a href="https://www.sheppardmullin.com/" class="external-link" target="_blank" rel="noopener">Sheppard Mullin Law Firm&lt;/a>. I wish I was joking.&lt;/p>
&lt;p>&lt;a href="https://danieldavis.app/" class="external-link" target="_blank" rel="noopener">Daniel Davis&lt;/a> for being my &amp;ldquo;Apple can suck it, but I&amp;rsquo;m still doing this anyway&amp;rdquo; sounding board for many years.&lt;/p></description></item><item><title>Thank you for making Owncast a success in 2023</title><link>https://gabekangas.com/blog/2024/01/thank-you-for-making-owncast-a-success-in-2023/</link><pubDate>Sat, 06 Jan 2024 00:00:00 +0000</pubDate><guid>https://gabekangas.com/blog/2024/01/thank-you-for-making-owncast-a-success-in-2023/</guid><description>&lt;p>I missed the first week of the year, but I still wanted to write a bit about Owncast and share my appreciation what this past year has brought for Owncast.&lt;/p>
&lt;p>As every year before it, Owncast has had the opportunity to be used to solve more people&amp;rsquo;s live streaming needs, be viewed by more people, and have more conversations around decentralization, Big Tech alternatives, The Fediverse, and all the wonderful things that come along with being a part of Owncast.&lt;/p>
&lt;h2 id="development">
Development
&lt;a class="heading-link" href="#development">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>From the development standpoint, by far, the biggest effort this year was the &lt;a href="https://gabekangas.com/blog/2023/02/owncast-v0.1.0-retrospective-frontend-web-rewrite/" class="external-link" target="_blank" rel="noopener">rewrite of the Owncast user interface&lt;/a>. This was also, by far, the largest effort by numbers of contributors. Switching to React and TypeScript was a huge win for the project. It opened the doors for frontend contributors for the first time, and I&amp;rsquo;m thankful every day I made that decision. I&amp;rsquo;m very proud of all all the work everyone had put into that effort, and it continues to pay off as we continue to more easily work on the frontend, fixing bugs and adding features.&lt;/p>
&lt;p>There&amp;rsquo;s a &lt;a href="https://owncast.online/roadmap" class="external-link" target="_blank" rel="noopener">roadmap&lt;/a> of upcoming plans that I&amp;rsquo;m really looking forward to getting to. There&amp;rsquo;s a lot of behind the scenes stuff taking place before the really fun and fancy user-facing features come to light, but I think it&amp;rsquo;ll all be worth it.&lt;/p>
&lt;h2 id="ubuntu-summit">
Ubuntu Summit
&lt;a class="heading-link" href="#ubuntu-summit">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>One of the highlights personally was being given the opportunity to travel to Riga, Latvia to &lt;a href="https://www.youtube.com/watch?t=515&amp;amp;v=sZMEuKI4Lpo&amp;amp;feature=youtu.be" class="external-link" target="_blank" rel="noopener">speak at Ubuntu Summit&lt;/a> about Owncast. It was a fantastic experience, and I&amp;rsquo;m very thankful to Cononical for the chance to share Owncast with more people. In general the attendees of the conference really seemed to be impressed with the direction of the project and the value it&amp;rsquo;s providing to users.&lt;/p>
&lt;h2 id="often-people-cant-find-a-way-to-talk-about-owncast">
Often people can&amp;rsquo;t find a way to talk about Owncast
&lt;a class="heading-link" href="#often-people-cant-find-a-way-to-talk-about-owncast">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>One problem that has continued to be difficult this year, and will continue to, is people&amp;rsquo;s expectations of Owncast, and how to interpret it.&lt;/p>
&lt;p>People, in general, are used to talking about multiuser &lt;em>services&lt;/em>. Like Facebook, or Instagram, or Twitch, or Mastodon, or Pixelfed, or Spotify. Things anybody can sign up to and use. These things are really easy to talk about. And Owncast will never be that. It&amp;rsquo;s not meant to be that. Owncast isn&amp;rsquo;t a public service. It&amp;rsquo;s &lt;em>software&lt;/em>. Like computing used to be. You wanted your computer to do something? You downloaded the software, you installed it, and now your computer does that thing. People don&amp;rsquo;t do that anymore, so people find it confusing. People want to go to a website and have somebody else run the software for them.&lt;/p>
&lt;p>They want unlimited users to be serviced, just like Facebook does. The concept of a person installing software that is just for that single person seems weird these days. So I get asked &amp;ldquo;How many channels can Owncast have?&amp;rdquo; Do you mean streams? One. Yours. It&amp;rsquo;s for you. I&amp;rsquo;m not sure how to make that more clear. It used to be the norm.&lt;/p>
&lt;p>I often get questions like &amp;ldquo;How many users does Owncast have?&amp;rdquo; And I don&amp;rsquo;t know what that question means. What&amp;rsquo;s a user? Do you mean how many downloads? Do you mean how many servers are online? I have no idea, servers are private. Do you mean how many viewers are watching streams? I have no idea. Streams are private.&lt;/p>
&lt;p>It also means most success stories are behind the scenes, and that sometimes leads to people comparing it to services like PeerTube and thinking Owncast is failing, or isn&amp;rsquo;t any good, or is useless, or whatever it is they think. That can&amp;rsquo;t be further from the truth.&lt;/p>
&lt;p>So you can see how people get frustrated and just blow off Owncast completely because they can&amp;rsquo;t get excited about something they can&amp;rsquo;t quantify. They can look at Pixelfed and say exactly &amp;ldquo;Look how many users they have!&amp;rdquo; or &amp;ldquo;Look how successful these accounts are!&amp;rdquo; and they&amp;rsquo;ll &lt;em>never&lt;/em> be able to do that with Owncast. And that&amp;rsquo;s okay. I just keep doing my own thing, and I try to explain when I can that it&amp;rsquo;s comparing Apples and Oranges.&lt;/p>
&lt;h2 id="thank-you-to-the-silent-successes">
Thank you to the silent successes
&lt;a class="heading-link" href="#thank-you-to-the-silent-successes">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>That being said, thank you to the many people and companies who are quietly relying on on Owncast to power their live video infrastructure. The churches, the porn sites, the conferences, the music venues, the wedding halls, and so many more that we&amp;rsquo;ll never hear spoken about. They&amp;rsquo;ll never be on the Fediverse or the directory. They&amp;rsquo;re not looking for viewers or attention. You&amp;rsquo;ll never know who they are. They&amp;rsquo;re just doing their thing successfully with Owncast. It is a complete honor to help them in some way, just like so many pieces of software have helped me over the years.&lt;/p>
&lt;h2 id="to-those-streaming-publicly-with-owncast">
To those streaming publicly with Owncast
&lt;a class="heading-link" href="#to-those-streaming-publicly-with-owncast">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>Thank you to those who keep running Owncast streams regardless if the majority of their viewers are there, or just a small minority. I&amp;rsquo;ve seen hundreds of Owncast-powered streams disappear after a week of waning enthusiasm because viewers didn&amp;rsquo;t magically show up. So when I see a live stream using Owncast publicly stream week after week, month after month, year after year, don&amp;rsquo;t think I don&amp;rsquo;t notice. It means everything. These are the people building the version of the internet I want to be a part of. They&amp;rsquo;re building their own thing, regardless what other people think. I don&amp;rsquo;t have the words to express how much that means to me.&lt;/p>
&lt;h2 id="thank-you-to-the-vocal-advocates">
Thank you to the vocal advocates
&lt;a class="heading-link" href="#thank-you-to-the-vocal-advocates">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>Those who care about the project, the vision, and the direction regardless if they&amp;rsquo;re actively streaming or not. I see all of you. It means the absolute world to me every time you say something nice about Owncast. It goes into a little bucket of motivation that I can pull from when I&amp;rsquo;m feeling down, frustrated, lonely, or that people don&amp;rsquo;t care. Thank you. I&amp;rsquo;ve been incredibly lucky to have people be so kind towards to me and the project, I can&amp;rsquo;t imagine others have it so good.&lt;/p>
&lt;h2 id="donors-have-really-helped-this-year">
Donors have really helped this year
&lt;a class="heading-link" href="#donors-have-really-helped-this-year">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>The financial support this year have been a lifesaver. At one point in the year I needed to acquire the services of a law firm to help with some paperwork. Mostly around clarification around the directory, what Owncast is, what it isn&amp;rsquo;t, what we provide, what we have control over, etc etc. The kind of thing I can provide next time I get a DMCA takedown (this is not uncommon). Without the donations I would have had to pay for that out of pocket, and it would have been a huge financial burden. So thank you to everyone who has donated, and continues to donate. It&amp;rsquo;s these kind of big expenses that come up that I&amp;rsquo;m able to handle because of your support, and I&amp;rsquo;m incredibly thankful for that.&lt;/p>
&lt;h2 id="community-outreach">
Community outreach
&lt;a class="heading-link" href="#community-outreach">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>Near the end of 2023 there began some really great initiatives around building more of a true community around Owncast. Since, in general, most Owncast-powered live streams are pretty isolated. People need to stream, so they install Owncast, and then they stream, they don&amp;rsquo;t exactly hang out and talk about Owncast with others. So it&amp;rsquo;s been a challenge to build a community around Owncast. But &lt;a href="https://owncast.mxks.dj/" class="external-link" target="_blank" rel="noopener">MXKS&lt;/a> offered to &lt;a href="https://owncast.online/newsletter/" class="external-link" target="_blank" rel="noopener">start a monthly Owncast newsletter&lt;/a> as a first step into reaching out to those who are interested in being a bit more connected into the world of Owncast and the streamers who use it. There has been an issue already, and people seem to like the idea. I&amp;rsquo;m looking forward to seeing where it goes. Please do sign up if you&amp;rsquo;re interested.&lt;/p>
&lt;p>Feel free to drop into the &lt;a href="https://owncast.rocket.chat/channel/owncast-community" class="external-link" target="_blank" rel="noopener">community chat&lt;/a> if you&amp;rsquo;d like to discuss the future of this initiative. Everything is on the table to make it easier for people to connect with each other, share their experiences, and help each other out. But it&amp;rsquo;s not up to me!&lt;/p>
&lt;h2 id="2024">
2024
&lt;a class="heading-link" href="#2024">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>I&amp;rsquo;m looking forward to 2024. There&amp;rsquo;s some really exciting things on the roadmap, and the behind he scenes stuff are equally going to improve working on the project. I hope to continue to balance features that improve the life of all streamers, regardless what their focus is, but also get to some specific things for the &amp;ldquo;interactive/twitch-style&amp;rdquo; streamer.&lt;/p>
&lt;p>I&amp;rsquo;m also looking forward to getting some ways out there to allow more people to easily view Owncast streams easier. Hopefully that&amp;rsquo;s on the horizon soon.&lt;/p>
&lt;p>Not everything goes fast with this project. I&amp;rsquo;m super appreciative that we get handfuls of contributions these days, but drive by contributions are usually not a good fit for working on really large, long-term feature work. But thankfully everyone has always been patient with me, and everyone is really thankful when they get released.&lt;/p>
&lt;p>That being said, if you&amp;rsquo;re interested in being a longer-term contributor to Owncast, and working on some of these exciting features that are coming up, I&amp;rsquo;d love to chat!&lt;/p>
&lt;p>Here&amp;rsquo;s to another year of creative, independent, decentralized live streaming. I hope I, and Owncast, can continue to play some part in it with you.&lt;/p></description></item><item><title>Upcoming Owncast features</title><link>https://gabekangas.com/blog/2023/04/upcoming-owncast-features/</link><pubDate>Mon, 24 Apr 2023 00:00:00 +0000</pubDate><guid>https://gabekangas.com/blog/2023/04/upcoming-owncast-features/</guid><description>&lt;p>While I try to keep a &lt;a href="https://owncast.online/roadmap" class="external-link" target="_blank" rel="noopener">public roadmap&lt;/a>, and keep a reasonable plan for Owncast, I rarely have an opportunity to gush to anybody (other than my therapist, and he doesn&amp;rsquo;t get it) about features I’m looking forward to building. So I thought I’d write a quick blog post to share some of my personal thoughts on my vision of future Owncast features from a high level.&lt;/p>
&lt;h2 id="the-frontend-rewrite">
The frontend rewrite
&lt;a class="heading-link" href="#the-frontend-rewrite">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>Owncast has been going through a &lt;a href="https://github.com/owncast/owncast/milestone/18" class="external-link" target="_blank" rel="noopener">large frontend rewrite&lt;/a> over the past year. And this wasn’t done lightly. It was done because I strongly felt if I wanted to build the features I had envisioned I wasn’t going to get there with the current frontend architecture, capabilities and tooling. So once this ships, I can get back to building features again! I’m really looking forward to that.&lt;/p>
&lt;p>Admittedly I have some backend infrastructure refactoring planned once the frontend ships, but I do expect that to be more straightforward since it doesn&amp;rsquo;t require UI.&lt;/p>
&lt;h2 id="powered-by-activitypub">
Powered by ActivityPub
&lt;a class="heading-link" href="#powered-by-activitypub">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>Practically every one of these features are backed by ActivityPub, and therefore supports federating with the Fediverse in some capacity. While some of these features may not have any available external interface to them yet, I hope some day for that to change. I&amp;rsquo;d love to work with more platform developers to make that happen. I&amp;rsquo;m super into the idea of robust Fediverse platform interoperability and I can&amp;rsquo;t wait to see what we can build together.&lt;/p>
&lt;h2 id="scheduled-streams">
Scheduled streams
&lt;a class="heading-link" href="#scheduled-streams">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>The first big one I’m looking forward to are scheduled streams. The ability to say “I stream at 7:30 every Tuesday” or “This Friday I have an event at 6pm”. It will be a really nice thing to feature on the Owncast stream page itself, so when you visit a stream that’s offline it tells you when you might want to come back. But that’s not the most interesting thing.&lt;/p>
&lt;p>People will be able to subscribe to a calendar so they have this schedule available to them wherever they are, so the real fans are always up to date. Additionally I can propagate this scheduled data to the Fediverse, updating the server’s profile info to include the next stream info, and inform followers that a stream is coming up soon. It’s all about informing people via different ways that something they might care about is coming up. I’m super excited about adding this functionality and I think it’ll benefit streamers and viewers alike.&lt;/p>
&lt;p>I&amp;rsquo;d also love for these events to be actionable on the Fediverse. I&amp;rsquo;ve looked into what it would take to &lt;a href="https://github.com/owncast/owncast/issues/2375" class="external-link" target="_blank" rel="noopener">federate with Mobilizon&lt;/a> but that doesn&amp;rsquo;t look possible. But if you know anybody over on that project, send them to me! Additionally, wouldn&amp;rsquo;t you like seeing an Owncast event come through your Mastodon timeline and there could be an explicit &amp;ldquo;see event&amp;rdquo; button or something built right in? Tell your friends who build your favorite microblogging Fediverse platform!&lt;/p>
&lt;h2 id="replays">
Replays
&lt;a class="heading-link" href="#replays">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>Next is a category of features I call “replays”. Some people want &amp;ldquo;archival&amp;rdquo;, meaning a bunch of video files they can download, but that&amp;rsquo;s not the goal here. I explicitly call these “replays” because that’s the point, for a viewer to be able to re-play part or whole of a stream.&lt;/p>
&lt;p>The plan is to start with clips. And while that’s technically more challenging, with more UI and requirements from my side, I believe it has the most value. I think being able to share highlights of a stream will help grow people’s viewership more than entire streams.&lt;/p>
&lt;p>I would also love for these clips to be Federated with PeerTube, but my expectations of that is going to stay low for now unless I can get some help from them to open things up and allow federating with non-PeerTube ActivityPub instances. Anybody know anybody at PeerTube? I’d love to chat.&lt;/p>
&lt;p>The entire replay project will be large, with a lot of design and UI requirements that admittedly I’m worried about. As I’ve &lt;a href="https://gabekangas.com/blog/2023/02/owncast-v0.1.0-retrospective-redesign/" >blogged about in the past&lt;/a> I’ve had a near impossible time getting design help, and it’s by far the skill set I have the hardest time with. So it’s going to be a long journey to get to where I’m trying to get to. But I’ll cross that bridge when I get to it.&lt;/p>
&lt;h2 id="mini-directories">
Mini Directories
&lt;a class="heading-link" href="#mini-directories">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>Something that people have asked for is to be able to run their own Owncast directories. The thought is that some communities and groups would like to be able to run multiple Owncast instances and have a way to link them all together. And while I’ve always thought that would be interesting, I’ve never been able to justify starting yet another rather large standalone software project that needs to be built, documented, supported, updated, etc for just a couple of people. It’s not as simple as open sourcing the current &lt;a href="https://directory.owncast.online" class="external-link" target="_blank" rel="noopener">Owncast directory&lt;/a> site for a number of reasons.&lt;/p>
&lt;p>So the solution I’m looking at is essentially making every Owncast server to be a mini directory. Via ActivityPub (the standardized protocol that powers the Fediverse), each Owncast server will “Follow” other servers, and then the servers would federate between each other things like stream status (live/offline), schedule, and more. They could even list non-Owncast instances in their directory, as long as they are on the Fediverse. This means you could add PeerTube channels in your Owncast mini directory if you wanted to. But of course they wouldn’t have all the additional federated info unless the remote server sent the required ActivityPub data. But there&amp;rsquo;s nothing stopping that from happening.&lt;/p>
&lt;p>And because things like stream state will be federated between Owncast instances, you could essentially mimic a Twitch-style “raid” because once your stream ends it’ll know what other streams are currently live, and can recommend your viewers to check them out.&lt;/p>
&lt;p>Cool, right?&lt;/p>
&lt;h3 id="powered-by-standards">
Powered by standards
&lt;a class="heading-link" href="#powered-by-standards">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h3>
&lt;p>In theory any Fediverse service could send the correct activities to Owncast and share state to show up in this directory (as long as the Owncast instance has explicitly followed the remote account, of course). I hope this will expand some of the things we do with decentralized, federated data. I have a &lt;a href="https://github.com/gabek/fedidocs/pull/10" class="external-link" target="_blank" rel="noopener">PR up&lt;/a> in the FediDevs repo to discuss Federated presence standardization that would be behind this feature.&lt;/p>
&lt;p>Can’t wait to build this stuff. &lt;a href="https://owncast.online/help" class="external-link" target="_blank" rel="noopener">I hope some of you join me!&lt;/a>&lt;/p></description></item><item><title>Owncast v0.1.0 Retrospective - Frontend Web Rewrite</title><link>https://gabekangas.com/blog/2023/02/owncast-v0.1.0-retrospective-frontend-web-rewrite/</link><pubDate>Fri, 17 Feb 2023 00:00:00 +0000</pubDate><guid>https://gabekangas.com/blog/2023/02/owncast-v0.1.0-retrospective-frontend-web-rewrite/</guid><description>&lt;p>This post is a continuation of posts leading up to Owncast v0.1.0 that discusses some of the high level goals for the release. Read the first post about a &lt;a href="https://gabekangas.com/blog/2023/02/owncast-v0.1.0-retrospective-redesign/" >Owncast redesign&lt;/a> for part 1.&lt;/p>
&lt;h2 id="hack-the-planet">
Hack the planet!
&lt;a class="heading-link" href="#hack-the-planet">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>One of the high level goals for Owncast since day one was hackibility. I wanted what was shipped to be a starting point for people looking to run their own custom live streams, not a locked in experience.&lt;/p>
&lt;p>I was determined to write the web frontend in a way that required no pre-processing, no bundling, no JavaScript compilers. Raw JavaScript, HTML and CSS would be shipped so making changes to these files would be as straightforward as opening the files in a text editor and making your changes.&lt;/p>
&lt;p>To pull this off it meant making a lot of very specific web technology choices, or maybe more specifically, a lack thereof. There could be no modern web development tooling, no bundling of source files, no TypeScript, no SASS, no CSS modules, no UI component libraries, no Webpack, no Babel. Just a bunch of raw web source.&lt;/p>
&lt;p>And it worked. My goal of giving people a bunch of plain text files they could edit was successful and I thought it was kind of cool. It traded a good developer experience for a better customization experience, but I felt that was a fair trade off.&lt;/p>
&lt;p>I thought all this would be a positive for contributors, too. There would be no development environment. You just download Owncast and you start making changes to the frontend files. That’s as minimal as you can get, and I thought people would enjoy that when looking to help the project.&lt;/p>
&lt;p>A nice middle ground was using &lt;a href="https://preactjs.com/" class="external-link" target="_blank" rel="noopener">Preact&lt;/a> + &lt;a href="https://preactjs.com/guide/v10/getting-started/#alternatives-to-jsx" class="external-link" target="_blank" rel="noopener">HTM&lt;/a>. It allowed building frontend components in &lt;em>almost&lt;/em> the exact same syntax as React, but without all the overhead of React or JSX transpiling requirements. I thought it was a pretty sweet solution that allowed people with familiarity with React to still jump right in and feel at home.&lt;/p>
&lt;h2 id="serious-downsides">
Serious downsides
&lt;a class="heading-link" href="#serious-downsides">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>Even though all the pieces of the puzzle worked, it became clear of the downsides.&lt;/p>
&lt;h3 id="frontend-contributors-were-scared-off">
Frontend contributors were scared off
&lt;a class="heading-link" href="#frontend-contributors-were-scared-off">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h3>
&lt;p>&lt;em>Almost&lt;/em> React is not React, and people were scared away from contributing on the frontend for pretty much the entirety of the project because Preact can look slightly different than React. People know what they know and like what they like, and me saying “anybody will be able to pick it up” didn’t make people feel comfortable enough to actually contribute.&lt;/p>
&lt;h3 id="everything-was-built-from-scratch">
Everything was built from scratch
&lt;a class="heading-link" href="#everything-was-built-from-scratch">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h3>
&lt;p>Because I was unable to take advantage of 3rd party UI components everything needed to be built from scratch. And as somebody who’s favorite part of software development isn’t deciding what a button’s hover state should look like, this really started to bother me. I wanted to build features, but every addition had a huge UI lift.&lt;/p>
&lt;p>An additional, substantial, downside, was the accessibility of all these home grown components wasn’t great and I was always being told how awful of a person I was because of it.&lt;/p>
&lt;h3 id="nobody-actually-took-advantage-of-it">
Nobody actually took advantage of it
&lt;a class="heading-link" href="#nobody-actually-took-advantage-of-it">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h3>
&lt;p>While people would tweak a color or font here and there, my goals of allowing people to completely control their page never really appealed to people like I thought it would. It was infinitely hackable, but nobody cared to hack it.&lt;/p>
&lt;h2 id="a-change-in-direction">
A change in direction
&lt;a class="heading-link" href="#a-change-in-direction">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>I started looking at all the features I wanted to build going into the future. Things like schedules, localization and recordings. But all I could think about was how I’d have to build, from scratch, calendars and scheduling components and reinvent the wheel to support translations. At this rate I’d never complete anything because I’d be spending all my time on UI and never complete features. There was nobody to help me, so I needed to figure out how to help myself make progress with the frontend. Changes had to be made.&lt;/p>
&lt;p>I figured if people weren’t taking advantage of the raw source, and I had to give up so much in order to continue to ship it, I would make the call to completely change this approach.&lt;/p>
&lt;p>I made sure to, multiple times, &lt;a href="https://owncast.online/news/20230201-preparing-for-v010/" class="external-link" target="_blank" rel="noopener">warn people of this change&lt;/a>, and then I’d take a rather large step backwards. By completely rewriting the UI using a new tech stack it would allow a better development experience in exchange for no longer shipping those raw web source files that nobody cared about anyway.&lt;/p>
&lt;h3 id="a-new-stack">
A new stack
&lt;a class="heading-link" href="#a-new-stack">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h3>
&lt;p>&lt;a href="https://nextjs.org/" class="external-link" target="_blank" rel="noopener">Nextjs&lt;/a>, &lt;a href="https://reactjs.org/" class="external-link" target="_blank" rel="noopener">React&lt;/a>, &lt;a href="https://www.typescriptlang.org/" class="external-link" target="_blank" rel="noopener">Typescript&lt;/a>, &lt;a href="https://github.com/css-modules/css-modules" class="external-link" target="_blank" rel="noopener">CSS Modules&lt;/a>, &lt;a href="https://sass-lang.com/" class="external-link" target="_blank" rel="noopener">Sass&lt;/a>, &lt;a href="https://storybook.js.org/" class="external-link" target="_blank" rel="noopener">Storybook&lt;/a>. I almost immediately started enjoying the process of web development more when I had tooling that made it more tolerable. I was moving faster, I was taking advantage of other tools, and in every direction there were positives (except the part where the entire thing had to be rebuilt).&lt;/p>
&lt;h3 id="contributors-came">
Contributors came
&lt;a class="heading-link" href="#contributors-came">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h3>
&lt;p>And it was almost overnight once Owncast stopped saying “Any web developer would feel at home with our stack” to explicitly saying “We use &lt;strong>React&lt;/strong>”, the contributors started showing up and successfully contributing.&lt;/p>
&lt;p>Really great people with insight, experience, and energy wanted to jump into the project and say “Hey, I know React. I know Typescript. I know Sass, let me help”. I can’t tell you how great that made me feel to finally get some help on the frontend after so long being frustrated with the situation.&lt;/p>
&lt;p>A &lt;strong>huge&lt;/strong> thank you to everyone who&amp;rsquo;s been involved with the work going into this release. There was so much to do and each person who jumped in to help made a world of difference.&lt;/p>
&lt;h3 id="progress">
Progress
&lt;a class="heading-link" href="#progress">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h3>
&lt;p>All of a sudden this huge goal that I created of rebuilding the entire Owncast interface started getting chipped away. I’d look at the issues that were in progress and there were more than just my name attached to them.&lt;/p>
&lt;p>I started to see things paying off. Now the page loads faster because I was able to tree shake unused code, and code split things into specific bundles. I was able to experiment faster by using 3rd party components. The accessibility support was better because people who build UI components for a living are better at it than I am and I wasn’t reinventing the wheel at every turn.&lt;/p>
&lt;p>The project is able to use Storybook to build and test components now, allowing contributors to help the project without even running a test instance of Owncast. They can load up Storybook and make changes. These changes can be validated by build tooling and UI snapshot tests can highlight the changes that are made.&lt;/p>
&lt;p>And I can get a level of structure and strictness that JavaScript alone doesn’t afford by using Typescript. I like types. Writing JavaScript alone feels like I’m wiring up a bomb with no instructions on where the wires go.&lt;/p>
&lt;p>None of this was possible before. At least not in a straightforward way.&lt;/p>
&lt;h2 id="what-did-i-learn">
What did I learn?
&lt;a class="heading-link" href="#what-did-i-learn">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>I guess you could call the initial goals of infinite hackibility to be a sort of a premature optimization. I wanted people to have the ability to do something that I didn’t know if they wanted or not. And sometimes that’s ok when you don’t have to invest a lot, or give up so much to accomplish it, but in this case it wasn’t a fair trade off.&lt;/p>
&lt;p>And while many people don’t agree, this is a concrete example of technology choices mattering. React is the biggest game in town, so using React appeals to more people. And even though a software developer can probably successfully work with any tech stack they try, not all of them want to try. No amount of me saying “It’ll be fine, just jump in” will convince them otherwise.&lt;/p>
&lt;h2 id="in-conclusion">
In conclusion
&lt;a class="heading-link" href="#in-conclusion">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>Do I think the React+TypeScript stack is so wonderful? Not really. In fact, it has a &lt;strong>ton&lt;/strong> of downsides. But did changing to it have significant upsides? &lt;strong>Absolutely&lt;/strong>.&lt;/p>
&lt;p>The old saying is pick the technology that can stay out of the way and lets you focus on only the parts that make you distinct. Moving to a React stack has really done this for me, the project, and the contributors.&lt;/p>
&lt;p>I now have an entire ecosystem of tooling that I can plug right in to make my life easier. Issues get caught at build time with TypeScript. UI issues get caught in visual snapshot tests. Things are more accessible because I can bring in components that were improved over years. I could go on and on.&lt;/p>
&lt;h2 id="oh-yeah-and-the-project-is-open-for-contributions">
Oh yeah, and the project is open for contributions
&lt;a class="heading-link" href="#oh-yeah-and-the-project-is-open-for-contributions">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>And lastly, I&amp;rsquo;d be missing an opportunity if I didn&amp;rsquo;t call out that we&amp;rsquo;re always looking for contributors to help with the project both on our new frontend, and the Go backend. Take a look at the &lt;a href="https://owncast.online/help" class="external-link" target="_blank" rel="noopener">Contributing Guide&lt;/a> and jump in!&lt;/p></description></item><item><title>Owncast v0.1.0 Retrospective - Redesign</title><link>https://gabekangas.com/blog/2023/02/owncast-v0.1.0-retrospective-redesign/</link><pubDate>Wed, 08 Feb 2023 00:00:00 +0000</pubDate><guid>https://gabekangas.com/blog/2023/02/owncast-v0.1.0-retrospective-redesign/</guid><description>&lt;p>With Owncast v0.1.0 starting a bug fixing and a super early testing phase now, I thought I’d write some blog posts about what it’s been like to get this far in this rather large release. A lot of projects don’t go into depth about how the sausage is made, and Owncast is no exception. I’m generally an open book if you ask or are involved with contributing to the project, but I usually don’t go out of my way to share every little thing with people who aren’t involved.&lt;/p>
&lt;p>For this first post I thought I’d start with a goal that I was very passionate about for this release, a redesign. And while I&amp;rsquo;m trying to be both respectful and honest it might seem like I&amp;rsquo;m being too much of one or another. Keep in mind that I appreciate every person who has been involved with Owncast in any capacity, and I respect their thoughts and any amount of energy they&amp;rsquo;ve put into the project.&lt;/p>
&lt;p>Going forward I promise other topics will be more positive, and I&amp;rsquo;ll be writing about the other goals for this release in future posts.&lt;/p>
&lt;h2 id="history-of-a-redesign">
History of a redesign
&lt;a class="heading-link" href="#history-of-a-redesign">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>I heard from so many people for such a long time that they liked Owncast but it &lt;em>&amp;ldquo;needed polish&amp;rdquo;&lt;/em> or &lt;em>&amp;ldquo;it looked bad&amp;rdquo;&lt;/em> or &lt;em>&amp;ldquo;the design needs help&amp;rdquo;&lt;/em>. And while there were never constructive action items, suggestions, or offers to help, I knew they were right and I looked forward to the opportunity to improve it.&lt;/p>
&lt;p>Like a lot of open source projects Owncast originally started small, with few features. As the project grew more things got added and the UI requirements became more complex. Few of the components or design elements shared styles, type, or colors because they were just slapped on as needs arose. &lt;strong>I felt now was the time to take a step back and start fresh with the Owncast web application frontend.&lt;/strong> I wanted to design from scratch and then build the UI from scratch. After that we can get back to building new features, hopefully with a design and architecture that serves the project well for years to come.&lt;/p>
&lt;p>&lt;strong>I took this redesign seriously and I wanted to do it right.&lt;/strong> Since visual design isn&amp;rsquo;t one of my core strengths I decided to find somebody who could work with the project.&lt;/p>
&lt;h2 id="finding-design-help">
Finding design help
&lt;a class="heading-link" href="#finding-design-help">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>I&amp;rsquo;ve never been able to catch the attention of designers to help with Owncast. And given my lack of design skills I feel quite vulnerable that there’s a skill I don&amp;rsquo;t have, and not sure how to acquire, leading to being completely dependent on somebody other than myself. When it comes to Owncast I generally haven’t had success when relying on others, but without a designer in-house I knew to accomplish this big project I&amp;rsquo;d have to find a design agency.&lt;/p>
&lt;p>It started as you’d expect, with me sharing everything I could about Owncast with the agency. It’s important that at this “product” level that they are 100% informed about what it is you’re building, why you’re building it, and who you’re building it for. I wrote documents about use cases and the different types of users. I provided lists of requirements and lists of things I didn’t want. I gave examples of work that I enjoyed and examples of things I didn’t like.&lt;/p>
&lt;p>The reaction from an outsider to Owncast wasn&amp;rsquo;t unexpected. &lt;em>“Owncast is kind of like Twitch? &lt;strong>Let’s make it look like Twitch!&lt;/strong>”&lt;/em> And that’s a valid starting point, it’s not uncommon to use existing products as a way to start. But unfortunately &lt;strong>I was unable to force progress from there&lt;/strong>. The more I pushed to not look like Twitch the more they straight up copied Twitch’s colors, layout, iconography and more. I’d say &lt;em>“This wouldn’t work for a church”&lt;/em> or &lt;em>“A school would never want a 100% black page with swords”&lt;/em>. Months of back and forth took place without much progress, and with other large topics such as mobile layouts, modals and user flows still up in the air &lt;strong>I realized I knew this project wouldn&amp;rsquo;t be completed with this particular partnership&lt;/strong>.&lt;/p>
&lt;p>I was disappointed, but I wasn’t ready to give up. This is when I, again, started hitting the Fediverse, forums, Linkedin, and other social platforms looking for somebody who could help with a new design of Owncast. I told everyone to share this request with their friends and colleagues. I needed help.&lt;/p>
&lt;p>Lucky for me some people responded, and each time they did I was immensely excited. A person who wants to help, it always makes me &lt;strong>so happy&lt;/strong>.&lt;/p>
&lt;h2 id="trying-to-accomplish-a-long-term-project-with-short-term-contributions">
Trying to accomplish a long-term project with short-term contributions
&lt;a class="heading-link" href="#trying-to-accomplish-a-long-term-project-with-short-term-contributions">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>I&amp;rsquo;m thankful for each person who has ever showed up with hopes to help with Owncast, so I don&amp;rsquo;t want to come off as harsh or ungreatful. But I was unprepared for the challenges of trying to manage a long-term project such as the entire look and feel of the web application when people were unable to commit to seeing it through.&lt;/p>
&lt;p>A project such as a redesign requires a long term commitment. It’s not like code contributions where you can jump in quick, fix a typo, and then never show up again. So what would happen is somebody would show interest, I&amp;rsquo;d get them up to speed on our requirements, they&amp;rsquo;d spend time working out what tools they wanted to use, start working on something, and then no longer be able to contribute for one reason or another. So I’d ask around again, and somebody new would graciously jump in but with the caveat that they &lt;strong>start the design over from scratch&lt;/strong> because they didn’t like what the previous person did. A couple times I agreed out of desperation for help, but each time they’d disappear and the cycle would restart. New person, new tools, new design, no progress. &lt;strong>New person, new tools, new design, no progress&lt;/strong>.&lt;/p>
&lt;p>It&amp;rsquo;s not uncommon to want to work on the sexy stuff, I totally get that. While I had a list of &lt;em>&amp;ldquo;Needs Design&amp;rdquo;&lt;/em> tasks like authentication modals and error states it was primarily things like chat that people wanted to start over on each time, leading to a long list of things that couldn&amp;rsquo;t get any attention.&lt;/p>
&lt;p>Eventually I had to make the call that there would be &lt;strong>no more complete restarts&lt;/strong> of design work because at some point I needed progress to be made. So going forward each person would &lt;strong>build upon the work of the person before them&lt;/strong>. And as expected people had no interest in working on error states and menus so &lt;strong>all design interest from anybody completely went away&lt;/strong>.&lt;/p>
&lt;p>With over half of a year passed, with nothing more than little bits and pieces of incomplete or unusable design scattered here and there we simply took the old layout of Owncast and started rebuilding it. No new colors, no new layout. People will see this rebuild and think &amp;ldquo;What took so long? It looks the same.&amp;rdquo;&lt;/p>
&lt;p>After all of this time, effort, and money, the redesign was a failure.&lt;/p>
&lt;h2 id="what-could-have-been-done-differently">
What could have been done differently?
&lt;a class="heading-link" href="#what-could-have-been-done-differently">
&lt;i class="fa fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
&lt;span class="sr-only">Link to heading&lt;/span>
&lt;/a>
&lt;/h2>
&lt;p>As the project maintainer this failure was completely my fault. I was operating purely on ambition, hoping the complimentary design skill set could be found one way or another and we&amp;rsquo;d end up building something that everyone was super proud of.&lt;/p>
&lt;p>Maybe it was foolish to take upon a project where I didn’t have that skill set required to accomplish it myself. Maybe I need to double down on the approach that if I can’t do it myself, then Owncast shouldn’t try it. But that would be so sad. &lt;strong>I want to believe that I can work with others to accomplish a goal that’s bigger than something I could do on my own.&lt;/strong>&lt;/p>
&lt;p>I think design and visually creative efforts will always be a challenge with Owncast and it&amp;rsquo;s not something I&amp;rsquo;ll be able to fix overnight. But I do hope that if I keep pushing hard enough I can appeal to people who care about visual design and want to see their efforts and vision reflected in the project.&lt;/p>
&lt;p>But just in case I did buy a couple books on design that I&amp;rsquo;m making my way through.&lt;/p></description></item></channel></rss>