1 +Ripcord version 0.4.23 (2020-2-17)
2 +----------------------------------
3 +
4 +### Discord
5 +
6 +* Removed usage of the ancient `GUILD_SYNC` Discord protocol feature.
7 +* Added initial population of channel user lists using the newer Discord server protocol features.
8 + * Initially, it will only show the 300 users at the top of the list for each channel.
9 + * Only the first 300 users will be initially loaded, regardless of how many members are in the server.
10 +* Added server-side name search to server member list and user list sidebar.
11 + * Ripcord now talks to the server when doing user searches and filtering.
12 + * You can use and this to load the information for users beyond the first 300.
13 + * If there are more than 300 members and you need to see a specific user in the list, use the search field to search for them.
14 + * If there's a match, they will appear in the sidebar, and will stay in the list you restart Ripcord.
15 +* Added server-side name search to @ completion.
16 + * Just like the user lists, you can also use "@username" to search for users, and the information for that user will be loaded on demand while you are typing.
17 + * This means you can now once again @-complete the names of users in servers of any size in Ripcord, just like back in the good 'ol days of 2016-2017.
18 + * This is probably still pretty buggy.
19 +* Fixed channel topic text not selectable in the channel details if your user doesn't have the permissions to edit it.
20 + * Finally, you can copy out the URLs in topics when you aren't a moderator.
21 +* Added ability to manage "Go Live"/stream permissions flag.
22 + * Just to manage the permissions. You can't stream or view streams with Ripcord.
23 +* Added some basic capabilities to display custom non-game Discord statuses.
24 + * Won't always work correctly -- this is just an initial test.
25 +* Decreased overall background CPU usage for many common back-end database/cache things.
26 + * Added some simple strategies to avoid wasting operations on the database files that better matches Discord's current data patterns.
27 + * Decreased CPU usage when Discord emoji reactions are rapidly being added and removed.
28 + * Decreased CPU usage when there are multiple private DM channels being modified in rapid succession.
29 + * Decreased CPU usage during initial sign-on with large friends lists.
30 + * Decreased CPU usage when fetching or processing lots of messages with embeds.
31 + * Decreased CPU usage when fetching lists of messages with many attachments/files.
32 + * Decreased CPU usage when in a server that's rapidly adding or removing members.
33 +* Removed the "Playing" prefix for custom statuses.
34 + * It was no longer always accurate, and Ripcord doesn't yet implement the newer custom status system that would give the full information for what kind of activity it is.
35 +* Added "BOT" next to bot authorship lines in chat log.
36 +* Fixed the username and emoji completion popups in the chat text input field for Discord channels jumping around between being above and below the input field as you type.
37 + * This was caused by the default popup window positioning logic trying to be too smart.
38 + * Ripcord just forces it above in all cases now, like it already did for Slack.
39 +* Fixed unmuting a Discord channel not taking effect in Ripcord's UI until restart.
40 + * The change should now be visible immediately.
41 +
42 +### Windows
43 +
44 +* Added a workaround for an incredible bug in Qt which could cause clicking the 'X' with the mouse in certain types of confirmation dialog boxes to confirm the action instead of canceling it.
45 + * Yes, this is a real bug in Qt.
46 + * It only happened if you clicked the 'X' window titlebar button with the mouse. It didn't happen if you clicked "Cancel" or if you pressed escape.
47 + * It only happened in some confirmation dialog boxes. It only happened on some versions of Windows and only some versions of Qt.
48 + * Shoutouts to user @Leafeon who discovered this Qt bug by taking a joke screenshot of the confirmation dialog box for deleting all of the channels in their server, and then having all of the channels in their server deleted.
49 +
50 +### Linux
51 +
52 +* Added a workaround for a FreeDesktop notifications clown fiesta.
53 + * Ripcord will sometimes issue notifications or tray messages like this example: "[CoolTeam] <Alice> hi Bob"
54 + * With Slack, the client is supposed to just display whatever the server gives it, like the example above.
55 + * Some Linux desktop environments (or rather, some components that constitute some desktop environments, I guess) will interpret "<Alice>" to be the opening tag of an HTML element that has no closing tag.
56 + * And then the desktop environment will helpfully display a popup with these contents: "[CoolTeam] "
57 + * Thanks.
58 + * If Ripcord just replaced '<' and '>' with the HTML entities as text (like `&lt;` ) then some *other* Linux DE components wouldn't display that correctly, either. (Since they aren't interpreting it as HTML, they would just display the HTML entities junk as text.)
59 + * There's no API or way to query to see what system or listener Qt ends up sending the notification messages to.
60 + * Even if there were, I don't want to maintain a list of specific FreeDesktop-ish dbus things in Ripcord with specific behaviors for each version that Ripcord should follow.
61 + * Solution: replace '< and '>' with 'ᐸ' and 'ᐳ' from the Unicode Canadian Aboriginal Syllabics block.
62 + * Computer.
63 +
1 64 Ripcord version 0.4.22 (2020-1-18)
2 65 ----------------------------------
3 66
4 67 Back from holiday. Back to work on Ripcord.
5 68
6 69 ### General
7 70