1
0
Fork 0
mirror of https://git.sr.ht/~ashkeel/strimertul-website synced 2024-10-31 21:33:09 +00:00

push beta build
All checks were successful
Deploy to Artifacts / deploy (push) Successful in 7s

This commit is contained in:
Ash Keel 2024-10-12 22:53:03 +02:00
parent b977f9ff17
commit 4acd54dd97
No known key found for this signature in database
GPG key ID: 53A9E9A6035DD109
2 changed files with 115 additions and 26 deletions

View file

@ -0,0 +1,87 @@
---
tag: v4.0.0-beta.1
title: v4.0.0-beta.1
date: 2024-10-12T20:49:36.112Z
prerelease: true
downloads:
- target: Windows 64bit
url: https://downloads.strimertul.stream/v4.0.0-beta.1/strimertul.exe
- target: Linux amd64
url: https://downloads.strimertul.stream/v4.0.0-beta.1/strimertul-amd64
- target: Linux arm64
url: https://downloads.strimertul.stream/v4.0.0-beta.1/strimertul-arm64
---
## Release notes
It's been a while since the alpha, things have been changing in my life and honestly the alpha worked so well I didn't really feel like needing to go back and change things, but also the 3.x.x has been giving people (those few who actually use this damn thing) issues, so I better start bringing 4.x to the stable field.
I'm cutting down on new features and will just add them later, the IRC bot *needs* to be dead ASAP, so this is now a beta (it's not just the same as the alpha, some stuff has been updated all around).
Below is the rest of the changelog exactly as-is from the Alpha. Don't expect new features between this and stable release, it's only bug fixes.
----
If you built any software using the kilovolt API: Woops, you gotta re-do a lot of that. Most of the keys have changed in naming and some in format as well.
Two important things: back up your `data` folder and re-authenticate your user (it should tell you to, more on that below).
### The IRC bot is dead
With Twitch finally pushing out the latest EventSub APIs for chat interaction I could finally kiss the IRC bot goodbye. All the existing chat functionality works as before but you'll notice it be way more stable.
Setting a secondary user as the chatting user is now done through the API (with a similar flow)
![The new chat user configuration showing up a secondary user as authenticated](../media/v4-chat-account.png)
### New permissions required warning
v4.0.0 sets up the foundation for a "problem detection system" aimed at finding configuration problems. I will be adding checks as I find them but for now the only one will be to check if a user is authorized to the Twitch app and if the scope of that authorization is valid. As Twitch adds new features and strimertül adopts them the scope of authorization will change and this warning will tell you to re-authenticate when needed.
![The window shows a yellow warning telling the user to re-authenticate](../media/v4-permission.png)
### Compact sidebar with narrow window
To accomodate people with not that much screen estate the strimertül window can now make better use of narrow spaces by compressing the sidebar to only show icons. You can still hover over the icons to check which page they link to.
![The main window with only icons in the sidebar to better accomodate content in a small window](../media/v4-small.png)
### Internal API overhaul
As v4.0.0 was going to be a big breaking change I took the opportunity to rename a lot of the kilovolt keys. You can check the changelog for a key-by-key breakdown or just take a look at the new API reference (since this is a pre-release, you'll need to check [indev](/api/v40/)). If you have built integrations such as overlays or extensions it's very much likely that you'll need to at least change the keys. If you wrote any chat integrations you'll definitely have to update the formats as well.
### Overall stability improvements
While developing v4.0.0 I found a lot of random crashes and I could fix most of the causes. There's still work to do on a lot of tickets that are still open but this should be much more stable than v3 even as an alpha. You can check the list of tickets still open [here](https://todo.sr.ht/~ashkeel/strimertul). Not all of them will be addressed in this release but all the bugs should be!
## Changelog
### Added
- The UI sidebar has been modified to better adapt to small window sizes
- A new part of the dashboard will now inform the user if any configuration problems have been detected.
### Changed
- The required set of permissions has changed. Existing users must re-authenticate their users to the app connected to strimertül.
- The `twitch/ev/eventsub-event` and `twitch/eventsub-history` keys have been replaced by a set of keys in the format `twitch/ev/eventsub-event/<event-id>` and `twitch/eventsub-history/<event-id>`. Users of the old system will have to adjust their logic. A simple trick is to change from get/subscribing from a single key to the entire prefix. The data structure is the same.
- The `twitch/bot/@send-message` key has been renamed to `twitch/chat/@send-message`. The data structure is the same.
- A lot of keys for internal use have been changed, make sure to check the new reference for fixing up any integrations you might have. A migration process will convert v3 keys to v4 keys.
- The log format has changed significantly as the internal logging library has been replaced.
- The Twitch chat integration has been rewritten from the ground up to not use an IRC bot and rely on EventSub. This means that you will need to reconfigure your twitch account, especially if you used a different account as the "bot" account. Because of this rewrite, the terminology around chat functionalities have been renamed from "Bot" to "Chat" (e.g. "Bot commands" are now "Chat commands").
- The (i) icon next to "Recent events" in the dashboard now uses a custom tooltip that shows up more consistently.
- The "strimertul is already running" message now pops up from the currently running instance.
- Setting up a secondary user for chat interactions is now much simpler through an auth flow much like the one for setting up the main user.
### Fixed
- Updated Kilovolt to a version that fixes an annoying crash when managing subscriptions.
- A new cleanup routine will remove old eventsub subscriptions that are no longer used. This should remove most of the errors when trying to set new API keys about "too many subscriptions".
### Removed
- `twitch/@send-chat-message` has been removed. Use `twitch/chat/@send-message` instead.
- The `twitch/ev/chat-message` and `twitch/chat-history` keys have been removed. Use the EventSub keys `twitch/ev/eventsub-event/channel.chat.message` and `twitch/eventsub-history/channel.chat.message` instead. The data structure will be different!
## Downloads
{{< release-dl >}}

View file

@ -1,20 +1,21 @@
{{ define "main" }} {{ define "main" }}
<main class="release-list"> <main class="release-list">
<div class="doc"> <div class="doc">
<header><h1>{{ .Title }}</h1></header> <header>
<h1>{{ .Title }}</h1>
</header>
<section class="copy">{{ .Content }}</section> <section class="copy">{{ .Content }}</section>
{{ range .Pages }} {{ range .Pages }}
<article class="release-item"> <article class="release-item">
<h2> <h2>
<time datetime="{{ .Date | time.Format "2006-01-02" }}" <time datetime="{{ .Date | time.Format " 2006-01-02" }}">{{ .Date | time.Format "2006-01-02" }}</time>
>{{ .Date | time.Format "2006-01-02" }}</time
>
<a href="{{ .RelPermalink }}">{{ .Title }}</a> <a href="{{ .RelPermalink }}">{{ .Title }}</a>
{{ if .Params.prerelease }} {{ if .Params.prerelease }}
<span class="prerelease">prerelease</span> <span class="prerelease">prerelease</span>
{{ end }} {{ end }}
</h2> </h2>
{{ if not .Params.prerelease }}
{{ if .Fragments.Identifiers.Contains "release-notes" }} {{ if .Fragments.Identifiers.Contains "release-notes" }}
<ul class="recap"> <ul class="recap">
{{ range (index .Fragments.HeadingsMap "release-notes").Headings }} {{ range (index .Fragments.HeadingsMap "release-notes").Headings }}
@ -22,8 +23,9 @@
{{ end }} {{ end }}
</ul> </ul>
{{ end }} {{ end }}
{{ end }}
</article> </article>
{{ end }} {{ end }}
</div> </div>
</main> </main>
{{ end }} {{ end }}