Add: Handle telnet links with Mudlet #7117

guhitb · 2024-01-30T18:06:27Z

Brief overview of PR changes/additions

Updated command line arguments to accept any URI or file path (first positional argument)
Made MudletInstanceHandler packages generic so any URI can be passed to another Mudlet Instance.
Updated mudlet.desktop, registry keys, and Plist (see Associate Mudlet with telnet links installers#115) to handle opening telnet links on each operating system.
Reused telnet ui components and profile selection logic from Add telnet:// links support #3131

Motivation for adding to Mudlet

fixes #689
/claim #689

Other info (issues closed, discussion etc)

I'm having trouble testing the linux telnet file association on my machine. I think I have something misconfigured that's not part of the Mudlet repo. I placed MimeType=x-scheme-handler/telnet;application/zip; in mudlet.desktop and ran xdg-mime default mudlet.desktop x-scheme-handler/telnet to set default.

Testing: open http://www.durismud.com and click on on the Play now link.

Mudlet#7107)  - Replaced `Mudlet::registerInstanceCoordinator` with `Mudlet::takeOwnershipOfInstanceCoordinator`. - Used unique_ptr and std::move() to transfer ownership rather than passing a raw pointer of `MudletInstanceCoordinator`. CodeQL warning ![image](https://github.com/Mudlet/Mudlet/assets/147658676/3344899f-d24c-4cd7-8cf7-dfac8d180d53) Mudlet#7065 (comment)

…t#7108) #### Brief overview of PR changes/additions :crown: An automated PR to update the built-in `3rdparty/kdtoolbox/singleshot_connect/singleshot_connect.h` to its latest version in upstream. We don't include it as a submodule as we're using tools from the KDToolBox as we need them. #### Motivation for adding to Mudlet Latest version of the Qt utility feature that allows singleshot connections. #### Other info (issues closed, discussion etc) _update triggered by refs/heads/development 1899c427a3a08462d3d29a5d842b669f211ba60b_ Co-authored-by: mudlet-machine-account <mudlet-machine-account@users.noreply.github.com>

…Mudlet#7110) Bumps [ZedThree/clang-tidy-review](https://github.com/zedthree/clang-tidy-review) from 0.17.0 to 0.17.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/zedthree/clang-tidy-review/releases">ZedThree/clang-tidy-review's releases</a>.</em></p> <blockquote> <h2>v0.17.1</h2> <h2>What's Changed</h2> <ul> <li>auth: Allow private key for apps to be base64 by <a href="https://github.com/bwrsandman"><code>@bwrsandman</code></a> in <a href="https://redirect.github.com/ZedThree/clang-tidy-review/pull/112">ZedThree/clang-tidy-review#112</a></li> <li>Use PyGithub to reuse auth headers to do requests by <a href="https://github.com/bwrsandman"><code>@bwrsandman</code></a> in <a href="https://redirect.github.com/ZedThree/clang-tidy-review/pull/113">ZedThree/clang-tidy-review#113</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/ZedThree/clang-tidy-review/compare/v0.17.0...v0.17.1">https://github.com/ZedThree/clang-tidy-review/compare/v0.17.0...v0.17.1</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/ZedThree/clang-tidy-review/commit/4923dc7cbb13a291cecc8507a89f70ed25ac9ce9"><code>4923dc7</code></a> Merge pull request <a href="https://redirect.github.com/zedthree/clang-tidy-review/issues/113">#113</a> from bwrsandman/authenticated-requests</li> <li><a href="https://github.com/ZedThree/clang-tidy-review/commit/baadf424d2af3b418e4c7de25989570fded55e34"><code>baadf42</code></a> Use set difference to cull comments</li> <li><a href="https://github.com/ZedThree/clang-tidy-review/commit/40e754e569e9aad0183712b96b3da37de04a961f"><code>40e754e</code></a> Reuse auth headers to do requests</li> <li><a href="https://github.com/ZedThree/clang-tidy-review/commit/f5273417752b89feb2903b47a72352b5d2ac4b41"><code>f527341</code></a> Merge pull request <a href="https://redirect.github.com/zedthree/clang-tidy-review/issues/112">#112</a> from bwrsandman/base64-private-key</li> <li><a href="https://github.com/ZedThree/clang-tidy-review/commit/d51789bde871d26e75c895ef69b3c3b11e39b38e"><code>d51789b</code></a> auth: Allow private key for apps to be base64</li> <li>See full diff in <a href="https://github.com/zedthree/clang-tidy-review/compare/v0.17.0...v0.17.1">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=ZedThree/clang-tidy-review&package-manager=github_actions&previous-version=0.17.0&new-version=0.17.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

#### Brief overview of PR changes/additions Add flatpak support #### Motivation for adding to Mudlet AppImage alternative and possibly better Steam Deck support #### Other info (issues closed, discussion etc) Sound works! --------- Co-authored-by: Vadim Peretokin <vadim.peretokin@carasent.com>

add-deployment-links · 2024-01-30T18:06:29Z

Hey there! Thanks for helping Mudlet improve. 🌟

Test versions

You can directly test the changes here:

No need to install anything - just unzip and run.
Let us know if it works well, and if it doesn't, please give details.

vadi2

The link handling didn't work for me on macOS, but that might be because the other PR registering URI's isn't merged yet.

vadi2 · 2024-02-03T17:19:13Z

src/FileOpenHandler.cpp

+
+        if (openEvent->url().isValid()) {
+            QUrl url = openEvent->url();
+            if (url.scheme() == "telnet") {


Could you add qsl() around string literals here and in other places please?

vadi2 · 2024-02-03T17:23:26Z

src/MudletInstanceCoordinator.cpp

-        } else {
-            mudletApp->slot_showConnectionDialog();
+
+        QStringList skippedUris;


What does this do?

It's unused, I'll will remove it

vadi2 · 2024-02-03T17:24:45Z

src/MudletInstanceCoordinator.cpp

+        QStringList skippedUris;
+
+        // Process queued URIs until we have to wait for a profile to be selected or loaded
+        while (!mQueuedUris.isEmpty()) {


Do you think this could be a ranged for instead? Better to avoid while loops if possible.

I can change it to something like for (int i = mQueuedUris.length() - 1; i >= 0; i--) to avoid while, but I don't think a ranged for will work since the loop needs to remove items from the list during the loop.

src/dlgConnectionProfiles.cpp

src/dlgTriggerEditor.cpp

vadi2 · 2024-02-03T17:30:52Z

src/main.cpp

@@ -657,7 +653,14 @@ int main(int argc, char* argv[])
    }
    mudlet::self()->show();

-    mudlet::self()->startAutoLogin(cliProfiles);
+    // Do auto login if a no URIs that open profiles are supplied


Hmm, grammar?

vadi2 · 2024-02-03T17:38:01Z

src/mudlet.cpp

+    if (process.exitStatus() != QProcess::NormalExit || process.exitCode() != 0) {
+        qWarning() << "Failed to set mudlet.desktop as the default handler for telnet links.";
+    }
+#endif


Try lregister for macOS: https://chat.openai.com/share/ca778a07-0203-4535-88ac-2c85e85cf384

vadi2 · 2024-02-03T18:00:37Z

src/mudlet.cpp

+#endif
+
+#if defined(Q_OS_MACOS)
+    return true;


Could macOS get a check too?

ironcross32 · 2024-02-03T19:04:54Z

I'm having trouble with this on Windows. The very first time I did the following:

Downloaded the PR
Extracted the ZIP file
Ran Mudlet.exe, waited for it to load fully, then closed it
Went to [https://www.durismud.com/](this page) and clicked the telnet link
Accepted opening the shortcut DLL
Mudlet opened, but to a blank screen as if no profile were selected
Closed Mudlet and attempted several times
After the first attempt, which did open Mudlet, successive attempts did not. I chose, upon clicking the link the secont time, to always allow the shortcut to open. It's worth noting that I had another instance (An earlier PR) of Mudlet open and connected to a MUD during this testing session.

guhitb · 2024-02-03T20:14:35Z

@ironcross32 Thanks for testing this.

From your report, it sounds like the association between Mudlet and telnet is successful, but the wrong version of Mudlet was opened to handle the link. I have the registry keys configured to open the installed version of Mudlet, not the version that was used to set the association.

I can change the file association to use the path of the running executable instead of the installed executable. This should allow the portable .exe to handle telnet links.

I'm not sure why subsequent attempts wouldn't open anything, but could be related to the other version of Mudlet being open. Can you provide a link to the earlier PR?

ironcross32 · 2024-02-03T21:53:58Z

@ironcross32 Thanks for testing this.

From your report, it sounds like the association between Mudlet and telnet is successful, but the wrong version of Mudlet was opened to handle the link. I have the registry keys configured to open the installed version of Mudlet, not the version that was used to set the association.

I can change the file association to use the path of the running executable instead of the installed executable. This should allow the portable .exe to handle telnet links.

I'm not sure why subsequent attempts wouldn't open anything, but could be related to the other version of Mudlet being open. Can you provide a link to the earlier PR?

Mudlet 4.17.235144c49 My mistake in my earlier post; I meant that I had the PTB running, not another PR.

Kebap · 2024-02-03T22:21:40Z

A person often runs both Mudlet release version, and Mudlet PTB on the same machine.

Now during testing, also a Mudlet DEV version is used next to those other two as well.

Which Mudlet version is expected to open the telnet:// links going forward now?

Let's take as example a few days in Mudlet lifecycle, and assume PTB gets updates daily.

Currently.

Mudlet 4.17.2 release - does not know telnet links.
Mudlet PTB from today - does not know telnet links.
Mudlet DEV from here - only this knows how to open telnet links, so it should be used.

Tomorrow, let's say this PR gets merged, all are happy.

The day after tomorrow,

Mudlet 4.17.2 release - does not know telnet links.
Mudlet PTB from that day - now this also knows how to open telnet links.
Mudlet DEV from here - this probably won't be in use anymore
Mudlet DEV from another random PR - this also knows how to open telnet links.

When I run this Mudlet release - I don't expect it to open telnet links
When I run this Mudlet PTB - I expect it to open telnet links
When I download the random DEV - ? Should it open telnet links instead?
When I close the random DEV - ? Should PTB open telnet links again? Would be good, as DEV will probably not be used much longer.

The day after the day after tomorrow,

Mudlet 4.17.2 release - does not know telnet links.
Mudlet PTB from that day - now this received another update, still knows telnet links
Mudlet DEV from here - this probably won't be in use anymore
Mudlet DEV from another random PR - I was only using yesterday, not today

When I run this Mudlet PTB - I assume this would grab the torch back from previous DEV version, and start to open telnet links again?

The day of 4.18 release

Mudlet 4.18 release - update installs, and now it knows how to open telnet links
Mudlet PTB from that day - still knows telnet links
Mudlet DEV - let's ignore these for now, should probably behave same as before

Which Mudlet would I expect to open telnet links now?
From a technical point, probably Mudlet 4.18 has taken the torch from PTB during update?
Generally speaking, should Mudlet release always open telnet links, and PTB should not?
A person often runs both Mudlet release version, and Mudlet PTB on the same machine.
From a usage point, would they expect PTB to open each telnet link, maybe?

The day after 4.18 release;

Mudlet 4.18 release - still knows how to open telnet links
Mudlet PTB from that day - still knows telnet links
Mudlet DEV - let's ignore these for now, should probably behave same as before

From the same technical point, then PTB has again taken the torch from release again?
Because it was installed the latest, after the latest PTB update?
So then when a person installs a PTB, they can never open telnet links with Mudlet release?
I am not so sure, which is the desired result.

guhitb · 2024-02-04T05:20:49Z

How about:

Mudlet should always use the path of the current executable when setting associations.
Any existing association set by another Mudlet version should be overwritten.
The "Do you want to associate Mudlet with telnet" popup should be shown if a different version has been associated.
For PTB and dev versions, version and executable path should be shown in the association popup.

Using this method:

There is no way to associate telnet with versions of Mudlet that do not support it.
The user can associate the desired version of Mudlet by running it and clicking yes.
If the user has disabled check at launch for the version of Mudlet they want to associate, they would need to reenable it first.

vadi2 · 2024-02-04T09:50:55Z

I think that would be great to try.

vadi2 · 2024-02-04T09:53:20Z

Updating with latest development to trigger a rebuild and see if the Mac changes come through.

wrapped string literals with qsl() removed unused variable bugfix replaced `while` with `for` fixed comment typo added lsregister for mac and mudlet scheme handling for windows

SlySven

Sorry if this seems a bit nit-picky - I'm just trying to polish it up a bit.

Thanks for working on this as it has been something that we wanted doing for a long time. 😌

One further suggestion would have though is that: can you ensure you have left a blank line between successive methods /functions in the source code.

HTH

SlySven · 2024-02-05T18:37:37Z

src/FileOpenHandler.h

 #include <QFileOpenEvent>
+#include <QObject>


QObject is a bit of a special case I think as it is the base class for many, if not all other Qt classes - so it does make sense to have it before the other class headers (though they probably #include it them selves anyhow)... thoughts @vadi2 ? 🤷‍♂️

SlySven · 2024-02-05T18:45:48Z

src/MudletInstanceCoordinator.cpp

+    }
+
+    QString file = uriOrFile;
+    if (file.startsWith("~")) {


That is a bit of a dodgy "bash"-ism (I think) - ~ as the WHOLE of the first directory specifier does indeed mean the "user's" home directory in the bash (and some other) shells - however ~someotherUser/ means the home directory of someOtherUser which is not how the code afterwards will handle it - I think you have to be more discerning than just using file.startsWith("~") here - you may have to check for a directory separator immediately afterwards to be sure...

SlySven · 2024-02-05T18:59:19Z

src/MudletInstanceCoordinator.cpp

        }
+        mMutex.unlock();


Careful - I do not think you want to hit this line if you have already unlocked it before by carrying out one of the blocks of code inside the ifs otherwise you could get nasal daemons - the Qt documentation for this method notes that it:

Unlocks the mutex. Attempting to unlock a mutex in a different thread to the one that locked it results in an error. Unlocking a mutex that is not locked results in undefined behavior.

Thanks for noticing this! I placed it outside the loop to avoid checking if(i==0) inside the loop, but it seems like that's the correct way to do it.

src/dlgProfilePreferences.cpp

src/dlgTriggerEditor.cpp

SlySven · 2024-02-05T19:39:55Z

src/mudlet.cpp

+
+    QStringList hostList = QDir(getMudletPath(profilesPath)).entryList(QDir::Dirs | QDir::NoDotAndDotDot, QDir::Name);
+
+    int profilesFound{};


🤮 - for complex classes I suppose the default/empty initialisation with {} does look attractive but for plain old data types like this I honestly think this is better:

Suggested change

int profilesFound{};

int profilesFound = 0;

SlySven · 2024-02-05T19:41:00Z

src/mudlet.cpp

+
+    int profilesFound{};
+    QString lastHostFound;
+    for (auto& host : hostList) {


Maybe?

Suggested change

for (auto& host : hostList) {

for (const auto& host : hostList) {

SlySven · 2024-02-05T19:48:32Z

src/mudlet.cpp

+            mpConnectionDialog->showInformationMessage(tr("%n matching profiles found for %1, which would you like to open?",
+                                                          "this message is shown when Mudlet is opened from a telnet:// link on a webpage, and more than one profile matches the game server/port - so "
+                                                          "the user needs to pick which of the available profiles they'd like to play with",
+                                                          profilesFound)
+                                                               .arg(url.host()));


We are not using that form of providing information to the translation team (see #5522) - instead try:

Suggested change

mpConnectionDialog->showInformationMessage(tr("%n matching profiles found for %1, which would you like to open?",

"this message is shown when Mudlet is opened from a telnet:// link on a webpage, and more than one profile matches the game server/port - so "

"the user needs to pick which of the available profiles they'd like to play with",

profilesFound)

.arg(url.host()));

/*: This message is shown when Mudlet is opened from a telnet:// link on a webpage, and more than one profile matches the game server/port - so

the user needs to pick which of the available profiles they'd like to play with.*/

mpConnectionDialog->showInformationMessage(tr("%n matching profiles found for %1, which would you like to open?",

"",

profilesFound)

.arg(url.host()));

SlySven · 2024-02-05T19:52:07Z

src/mudlet.qrc

@@ -217,5 +217,6 @@
        <file>ui/package_manager.ui</file>
        <file>ui/package_manager_unpack.ui</file>
        <file>ui/set_room_area.ui</file>
+        <file>ui/check_default_client.ui</file>


Please move it up a bit so that it is in the correct alphabetical sort position (after line 210)...

SlySven · 2024-02-05T19:57:06Z

src/ui/check_default_client.ui

+      </size>
+     </property>
+     <property name="text">
+      <string>Mudlet is not currently set as your default client. Would you like to make it your default client?</string>


A suggestion to try and avoid repeating the exact "your default client" phrase. Also to explain what it would be the default for! 😀

Suggested change

<string>Mudlet is not currently set as your default client. Would you like to make it your default client?</string>

<string>Mudlet is not currently set as the default client for handling <tt>telnet://</tt> URLs. Would you like to make it your default?</string>

You might need to tweak the <tt>...</tt> - I am trying to get it displayed (almost) like: telnet: appears here (but without any shading).

guhitb · 2024-02-07T02:51:43Z

Okay, those changes have been made 😄

bugfix for macos compile

vadi2 · 2024-02-07T07:11:54Z

/refresh links

vadi2

Testing has revealed a problem on Linux 😅 the temporary location the AppImage gets extracted and run from will always change. Do you think this is solvable? We're looking at migrating to flatpak at the same time, so it's not worth too much effort to make it work for AppImages.

vadi2

macOS testing always says "checking default: false". Have you got access to a mac? If no I can do some testing for you.

guhitb · 2024-02-07T09:45:20Z

I think so. We can check if there's an APPIMAGE env var set and use that instead of the executable path.

I don't have access to a mac, testing would be appreciated. I'm using a swift script to check which executable handles telent, but sounds like it's not working as expected.

Unfortunately it has to be a compiled binary that is linked to Cocoa to work.

demonnic · 2024-02-10T13:59:33Z

Hmm, when I open the test version it does ask to register itself as the handler for telnet links, but then when I click the telnet link to 'play now' it doesn't actually open anything up.
Windows 10

vadi2 · 2024-02-10T14:06:22Z

I've fixed checking which application is responsible for the telnet:// uri, but registration doesn't yet work. One reason might be that lsregister expects a .app path, not the binary path @guhitb.

mpconley · 2024-02-10T14:27:55Z

Mac with snapshot 746c2092 and after a Chrome restart

guhitb and others added 26 commits January 25, 2024 16:33

changed 'open with' to accept telnet links

afb547c

Merge branch 'Mudlet:development' into telnet

0de6965

added telnet opening logic and ui from previous attempt

321b650

bug fixes

e595047

fixed file path to uri conversion and removed some logs

c675db9

moved checkbox into container

d4811f6

added row and column to checkbox

ee9e834

added telnet opening logic and ui from previous attempt

134d699

removed duplicate functions

24a5682

fixed duplicate/old code from rebase

8fc9c5c

Merge branch 'development' into telnet

a1f9e7e

bugfix

b9b098f

applied clang-format

cd56b84

ran clang format

53cd7d0

ran clang-format

8c98294

ran clang-format

b40d425

ran clang-format

b4362c5

ran clang-format

a3dc7d6

ran clang-format

a15b6c4

ran clang-format

3f223b9

updated comments and help

fb39d16

guhitb requested review from a team as code owners January 30, 2024 18:06

Merge branch 'development' into telnet

e00e7f3

vadi2 reviewed Feb 3, 2024

View reviewed changes

vadi2 and others added 2 commits February 4, 2024 10:53

Merge branch 'development' into telnet

a9c4262

added support for mudlet uri scheme on mac

6eb495b

wrapped string literals with qsl() removed unused variable bugfix replaced `while` with `for` fixed comment typo added lsregister for mac and mudlet scheme handling for windows

SlySven reviewed Feb 5, 2024

View reviewed changes

guhitb added 3 commits February 6, 2024 21:31

impemented code review suggestions

871eccd

clang-format

b647ec0

added copyright header

c45adb9

bugfix for macos compilation

3025a30

bugfix for macos compile

guhitb force-pushed the telnet branch from c5c4826 to 3025a30 Compare February 7, 2024 05:45

vadi2 reviewed Feb 7, 2024

View reviewed changes

use appimage path

24ba7d1

vadi2 added 2 commits February 10, 2024 14:50

Fix telnet URI retrieval on macOS

746c209

Unfortunately it has to be a compiled binary that is linked to Cocoa to work.

Improve variable names

31e064d

Added explanatory comment

cbca988

vadi2 assigned guhitb Feb 16, 2024


		QStringList hostList = QDir(getMudletPath(profilesPath)).entryList(QDir::Dirs \| QDir::NoDotAndDotDot, QDir::Name);

		int profilesFound{};

	for (auto& host : hostList) {
	for (const auto& host : hostList) {

	<string>Mudlet is not currently set as your default client. Would you like to make it your default client?</string>
	<string>Mudlet is not currently set as the default client for handling <tt>telnet://</tt> URLs. Would you like to make it your default?</string>

Add: Handle telnet links with Mudlet #7117

Are you sure you want to change the base?

Add: Handle telnet links with Mudlet #7117

Conversation

guhitb commented Jan 30, 2024 • edited by vadi2

Brief overview of PR changes/additions

Motivation for adding to Mudlet

Other info (issues closed, discussion etc)

add-deployment-links bot commented Jan 30, 2024 • edited

Test versions

vadi2 left a comment • edited

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

ironcross32 commented Feb 3, 2024

guhitb commented Feb 3, 2024

ironcross32 commented Feb 3, 2024

Kebap commented Feb 3, 2024

guhitb commented Feb 4, 2024

vadi2 commented Feb 4, 2024

vadi2 commented Feb 4, 2024

SlySven left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

guhitb commented Feb 7, 2024

vadi2 commented Feb 7, 2024

vadi2 left a comment

Choose a reason for hiding this comment

vadi2 left a comment

Choose a reason for hiding this comment

guhitb commented Feb 7, 2024

demonnic commented Feb 10, 2024 • edited

vadi2 commented Feb 10, 2024 • edited

mpconley commented Feb 10, 2024

guhitb commented Jan 30, 2024 •

edited by vadi2

add-deployment-links bot commented Jan 30, 2024 •

edited

vadi2 left a comment •

edited

demonnic commented Feb 10, 2024 •

edited

vadi2 commented Feb 10, 2024 •

edited