v0.17 files

help/help-releases.html

@@ -17,6 +17,7 @@
     <h1><a name="top">Release Information</a></h1>
     
     <p>
+        <a href="#0.17">0.17</a> |
         <a href="#0.16">0.16</a> |
         <a href="#0.15">0.15</a> |
         <a href="#0.14">0.14</a> |
@@ -65,7 +66,50 @@
     full list of changes.</p>
     
     <h2>
-        <a name="0.16">Version 0.16</a> <a name="latest">(This one!)</a> (2022-01-06)
+        <a name="0.17">Version 0.17</a> <a name="latest">(This one!)</a> (2022-01-31)
+        <a href="#top" class="top">[back to top]</a>
+    </h2>
+    <p>The Twitch v5 API is scheduled to be shutdown at the end of February 2022
+        and that old API still contains some emotes that aren't available in the
+        new API. This means that it's possible that more of your emotes won't
+        show up in the Emote Dialog, TAB Completion and your sent messages in
+        Chatty (Global, Subscriber and Follower Emotes should always be fine
+        though).</p>
+    <p>This update introduces the Local Emotes feature that allows you to
+        manually configure specific Twitch Emotes to be always available for you
+        locally in Chatty (how your messages appear to others won't be affected
+        by this). Read more about this in the <a href="help-settings.html#EmoticonsLocal">help</a>.</p>
+    
+    <pre>
+### Twitch Features
+- Switched Global Emotes to new API
+  - Some new Global Emotes that weren't in the old API should be available now
+  - Added separate Smilies (as in :) etc.) setting to select which set should be
+    displayed locally (since this isn't handled well in the new API), the
+    setting is automatically set based on the old API as long as it's available
+- Added Local Emotes setting
+  - Allows you to manually configure Emotes that should always be displayed
+    in your local client as usable by you, for Emotes that are not available
+    through the API
+  - As long as the old API is available, some Emotes available through that but
+    not through the new API can be marked as "endangered" in the Emotes Dialog
+- Added follower count to User Dialog again (previously removed due to being
+  slightly more difficult to implement with the new API)
+
+### Other
+- Tab Info Settings: Added custom color setting affecting color related options
+- Added setting to close tabs with middle mouse button
+- Added prefix `config:!blacklist` to circumvent the Highlight/Ignore blacklist
+- Some small Emote Dialog improvements
+- Updated Emoji (Twemoji set)
+- Updated help
+
+### Bugfixes
+- Added workaround for online/offline spam in followed channels doing a rerun
+    </pre>
+    
+    <h2>
+        <a name="0.16">Version 0.16</a> (2022-01-06)
         <a href="#top" class="top">[back to top]</a>
     </h2>
     <p>With the v5 Twitch API shutting down early 2022 more features have been

help/help-settings.html

@@ -429,7 +429,74 @@
     ignore emotes, because then the correct code will automatically be added to
     the list.</p>
     
+    <h3>
+        <a name="EmoticonsLocal">Local Emotes</a>
+        <a href="#top" class="top">[back to menu]</a>
+    </h3>
+    <p>This feature allows you to configure Twitch Emotes that will always show
+        up as usable in messages you send, the Emotes Dialog and TAB Completion,
+        disregarding if you actually have access to them or not. This only
+        affects your local client, others will only see emote images in your
+        messages when you actually have access to the emotes.</p>
     
+    <p>The use of Local Emotes is intended for Twitch Emotes that are not
+        available through the Twitch API and thus do not show up in messages you
+        send since Chatty doesn't know about them. This issue does not apply
+        when other people receive your messages or when you receive their
+        messages, since Twitch handles emotes parsing serverside for those.</p>
+    
+    <p>With the removal of the old Twitch v5 API in February 2022 this problem
+        can affect even more Emotes than before. The Emote Dialog provides the
+        "Highlight endangered emotes" function until the API is removed (see
+        below).</p>
+    
+    <p>Recommendations:</p>
+    <ul>
+        <li>Only add Twitch Emotes that you have permament access to.</li>
+        <li>Only add Emotes that would otherwise not show up in Chatty in your
+            sent messages or Emote Dialog.</li>
+        <li><strong>Do not add</strong> Global, Subscriber and Follower Emotes
+            as Local Emotes, since they should be available throught the API.</li>
+        <li>If you added a Local Emote by accident or lost access to one then
+            you should remove it again (e.g. through the Emote Context Menu or
+            Settings Dialog).</li>
+    </ul>
+    
+    <p>You can add/remove Local Emotes in different ways:</p>
+    <ul>
+        <li>The <strong>Emote Context Menu</strong> (e.g. right-click on an emote in chat)
+            using the <strong>"Add local emote"</strong> option.
+            For example if you have a favorite emote that you have permanent
+            access to but that isn't available through the API (meaning it
+            doesn't show up in the Emote Dialog or when you send a message), you
+            can send a message with it through Webchat to the same channel you
+            have joined in Chatty and then use the Context Menu option on it.
+        </li>
+        <li>In the <strong>Settings Dialog</strong> in the Emoticon settings you
+            can view and edit the list of Local Emotes.</li>
+        <li>The <strong>Emote Dialog "My Emotes" tab</strong> can highlight
+            Emotes that are only available through the old API, as long as the
+            old API hasn't been removed. Enable the <strong>"Highlight endangered emotes"</strong>
+            checkbox to see which Emotes might make sense to add.
+            <ul>
+                <li>Magenta border: Only available through old API</li>
+                <li>Gray border: Only available through old API, but already
+                    added to Local Emotes</li>
+            </ul>
+            To add Local Emotes you can use:
+            <ul>
+                <li>The Emote Context Menu to add a single Emote</li>
+                <li>The Section Title Context Menu to add all Emotes of a section</li>
+            </ul>
+            <em>Note:</em> You must have a channel joined and all API requests
+            must have finished for this to show up correctly. For example
+            Subscriber Emotes should not be highlighted. If the old API has
+            already been removed, adding Local Emotes through the Emote Dialog
+            doesn't really make sense, since all shown Emotes would be available
+            through the new API anyway.
+        </li>
+    </ul>
+
     <h2>
         <a name="Fonts">Fonts</a>
         <a href="#top" class="top">[back to menu]</a>
@@ -1004,6 +1071,9 @@
                     Example: <code>config:live|/"Grand Theft Auto"</code> would match
                     in any channel with a live stream where <code>Grand Theft Auto</code>
                     occurs in the currently streamed game/category</li>
+                <li><code>config:!blacklist</code> - Ignore the overall
+                    blacklist for this entry. The <code>blacklist:</code> prefix
+                    still applies though.</li>
             </ul>
         </li>
         <li><a name="Highlight_Prefix-blacklist"><code>blacklist:</code></a> to specify one or more text patterns

help/help.html

@@ -5,7 +5,7 @@
         <link rel="stylesheet" type="text/css" href="style.css" />
 </head>
 <body>
-    <h1><a name="top">Chatty (Version: 0.16)</a></h1>
+    <h1><a name="top">Chatty (Version: 0.17)</a></h1>
     <table>
         <tr>
             <td valign="top">

index.html

@@ -16,9 +16,9 @@ function loaded() {
 		      { ceiling: null,  text: "$years years ago" }
 		]
 	}
-	document.getElementById("ago").innerHTML = "Version 0.16 released "+humanized_time_span("2022/01/06", Date(), custom_date_formats)+"";
+	document.getElementById("ago").innerHTML = "Version 0.17 released "+humanized_time_span("2022/01/31", Date(), custom_date_formats)+"";
 
-	getDownloads("v0.16");
+	getDownloads("v0.17");
 
 	slideshow_init("slideshow");
 }
@@ -157,7 +157,7 @@ function getDownloads(tag) {
 
 
 	<h2 id="download">Download</h2>
-	<p>Choose one of the following downloads of <strong>Chatty Version 0.16</strong><span id="dlCount" style="margin-bottom:7px;"></span>. For older versions or betas go to the <a href="https://github.com/chatty/chatty/releases">GitHub Releases</a>. Checksums for  release files are available as <a href="https://tduva.com/chatty/checksums/v0.16/">SHA-256 hashes</a>.</p>
+	<p>Choose one of the following downloads of <strong>Chatty Version 0.17</strong><span id="dlCount" style="margin-bottom:7px;"></span>. For older versions or betas go to the <a href="https://github.com/chatty/chatty/releases">GitHub Releases</a>. Checksums for  release files are available as <a href="https://tduva.com/chatty/checksums/v0.17/">SHA-256 hashes</a>.</p>
 	<p>If this is your first time using Chatty check out the <a href="help/help-getting-started.html"><strong>Getting Started Guide</strong></a>.</p>
 
 	<h3>Windows</h3>
@@ -169,11 +169,11 @@ function getDownloads(tag) {
 		<tr>
 			<td>
 				<dl>
-					<dt><a href="https://github.com/chatty/chatty/releases/download/v0.16/Chatty_0.16_win_standalone_setup.exe"><strong>Download Windows Standalone (Installer)</strong></a> <span class="recommended"><sup>Recommended</sup></span></dt>
+					<dt><a href="https://github.com/chatty/chatty/releases/download/v0.17/Chatty_0.17_win_standalone_setup.exe"><strong>Download Windows Standalone (Installer)</strong></a> <span class="recommended"><sup>Recommended</sup></span></dt>
 					<dd>Install into a folder of your choice and start <code>Chatty.exe</code> (or optionally created shortcuts).</dd>
 				</dl>
 				<dl>
-					<dt><a href="https://github.com/chatty/chatty/releases/download/v0.16/Chatty_0.16_win_standalone.zip">Download Windows Standalone (.zip)</a></dt>
+					<dt><a href="https://github.com/chatty/chatty/releases/download/v0.17/Chatty_0.17_win_standalone.zip">Download Windows Standalone (.zip)</a></dt>
 					<dd>Extract the .zip into a folder of your choice and start <code>Chatty.exe</code>.</dd>
 				</dl>
 
@@ -181,11 +181,11 @@ function getDownloads(tag) {
 			</td>
 			<td>
 				<dl>
-					<dt><a href="https://github.com/chatty/chatty/releases/download/v0.16/Chatty_0.16_win_setup.exe">Download JAR-Version (Installer)</a></dt>
+					<dt><a href="https://github.com/chatty/chatty/releases/download/v0.17/Chatty_0.17_win_setup.exe">Download JAR-Version (Installer)</a></dt>
 					<dd>Install into a folder of your choice and start <code>Chatty.jar</code> (or optionally created shortcuts).</dd>
 				</dl>
 				<dl>
-					<dt><a href="https://github.com/chatty/chatty/releases/download/v0.16/Chatty_0.16.zip">Download JAR-Version (.zip)</a></dt>
+					<dt><a href="https://github.com/chatty/chatty/releases/download/v0.17/Chatty_0.17.zip">Download JAR-Version (.zip)</a></dt>
 					<dd>Extract the .zip into a folder of your choice and start <code>Chatty.jar</code>.</dd>
 				</dl>
 			</td>
@@ -193,7 +193,7 @@ function getDownloads(tag) {
 	</table>
 
 	<h3>Non-Windows</h3>
-	<p>For OS other than Windows (e.g. Linux or MacOS) you will need to download the <a href="https://github.com/chatty/chatty/releases/download/v0.16/Chatty_0.16.zip">JAR-Version (.zip)</a> and must have Java 8 or later installed on your system. Extract the .zip into a folder of your choice and start <code>Chatty.jar</code>.</p>
+	<p>For OS other than Windows (e.g. Linux or MacOS) you will need to download the <a href="https://github.com/chatty/chatty/releases/download/v0.17/Chatty_0.17.zip">JAR-Version (.zip)</a> and must have Java 8 or later installed on your system. Extract the .zip into a folder of your choice and start <code>Chatty.jar</code>.</p>
 
 	<h2 id="feedback">Contact</h2>
 	<p>If you have any feedback or questions feel free to contact me. You can <a href="https://discord.gg/WTuqGeJ">join the Chatty Discord</a> <sup>preferred</sup>, write me an <a href="mailto:chattyclient@gmail.com">E-Mail</a> or use <a href="https://twitter.com/chattyclient">Twitter</a>.</p>