DOCS-2046: Update install and agent docs #3243

npentrel · 2024-08-13T12:44:07Z

installation: ready for review
- the change from micro-RDK to viam-micro-server will happen separately to limit complexity
agent: ready for review
provisioning: ready for review

Currently missing and I am leaning towards doing that in a separate PR:

Offline/pre-installation
Test CLI Utility

docs/configure/agent.md

sguequierre · 2024-08-14T18:38:33Z

docs/configure/agent.md

+Currently, `viam-agent` is only supported on Linux, for amd64 (x86_64) and arm64 (aarch64) CPUs.
+{{< /alert >}}
+
+To see how to provision machines using `viam-agent`, see


Suggested change

To see how to provision machines using `viam-agent`, see

To provision machines using `viam-agent`, see

sguequierre · 2024-08-14T18:46:45Z

docs/configure/agent.md

+
+1. Create a configuration file with the desired configuration for your machine. You can:
+
+   - [create a new machine in the Viam app](/cloud/machines/#add-a-new-machine) and configure it as desired or use an existing deployed machine, then switch to **Raw JSON** mode and copy the configuration shown into a new file on your machine.


Suggested change

- [create a new machine in the Viam app](/cloud/machines/#add-a-new-machine) and configure it as desired or use an existing deployed machine, then switch to **Raw JSON** mode and copy the configuration shown into a new file on your machine.

- [create a new machine in the Viam app](/cloud/machines/#add-a-new-machine) and configure it as desired or use an existing deployed machine, then switch to **Builder** mode and copy the configuration shown into a new file on your machine.

sguequierre · 2024-08-14T18:51:20Z

docs/configure/agent.md

+You can configure update behavior for the Agent and `viam-server` using the [Viam app](https://app.viam.com/).
+
+{{< alert title="Important" color="note" >}}
+When `viam-agent` updates either itself or `viam-server`, you must [restart these services](/installation/manage-viam-agent/) in order to use the new version.


Suggested change

When `viam-agent` updates either itself or `viam-server`, you must [restart these services](/installation/manage-viam-agent/) in order to use the new version.

When `viam-agent` updates either itself or `viam-server`, you must [restart these system services](/installation/manage-viam-agent/) in order to use the new version.

(opt) maybe to distinguish from resource services?

sguequierre · 2024-08-14T18:52:15Z

docs/configure/agent.md

+You can find these messages on the [**LOGS** tab](/cloud/machines/#logs) of your machine's page.
+
+`viam-agent` only sends messages when your machine is online and connected to the internet.
+If your machine is offline, log messages are queued, and are sent to the Viam app once your machine reconnects to the internet.


Suggested change

If your machine is offline, log messages are queued, and are sent to the Viam app once your machine reconnects to the internet.

If your machine is offline, log messages are queued and are sent to the Viam app once your machine reconnects to the internet.

thinmk this is oxford comma so feel free to ignore

docs/configure/agent.md

docs/fleet/provision.md

Otterverse

Okay, finished reading through these new/updated pages. Sorry there are so many notes. Lots are duplicates though. Feel free to slack me with questions or if you need clarifications.

Otterverse · 2024-08-15T19:21:54Z

docs/installation/_index.md


-1. Go to the [Viam app](https://app.viam.com).
-   Create an account if you haven't already.
+   - `manual`: installs `viam-server` directly on your machine.


This isn't very clear. What does "directly" mean in this context? "Manual" actually points to the AppImage install instructions for most drop-down combinations. Might be better worded as "Installs only viam-server"

Otterverse · 2024-08-15T19:23:35Z

docs/installation/_index.md

-1. Go to the [Viam app](https://app.viam.com).
-   Create an account if you haven't already.
+   - `manual`: installs `viam-server` directly on your machine.
+   - `viam-agent`: installs [`viam-agent`](/configure/agent/) which provisions a machine as it first comes online with a pre-defined configuration.


This doesn't make sense to me, in the context of the steps below for this option, nor how it contrasts with the "manual" option above. Would reword as something like "Installs viam-agent, which will automatically install/updated viam-server, AND provide additional functions such as provisioning (link_to_provisioning) and OS update configuration."

Otterverse · 2024-08-15T19:26:19Z

docs/installation/_index.md


-1. Once you have followed the steps on the setup instructions, `viam-server` is installed and running.
-   Wait for confirmation that your computer has successfully connected.
+   On your machine's page on [the Viam app](https://app.viam.com), your machine will show that it's **Live**.


Both these tabs show almost identical information, which could be summerized as "follow the instructions, and wait for it to come online." I also find it slightly confusing to switch tabs ONLY for steps 6-7 of a multi-step process. I thought the box glitched at first and wasn't showing earlier steps (as a box feels "separate" from the content outside of it.)

Otterverse · 2024-08-15T19:27:24Z

docs/installation/_index.md


 {{% /tab %}}
 {{< /tabs >}}

-{{<youtube embed_url="https://www.youtube-nocookie.com/embed/gmIW9JoWStA">}}
+{{< alert title="Linux: Automatic startup" color="note" >}}
+On Linux installs, `viam-server` will start automatically when your system boots by default, but you can [change this behavior](/installation/manage-viam-server/) if desired.


This links to docs that only work for the "manual" (aka the AppImage) install method.

Otterverse · 2024-08-15T19:27:49Z

docs/installation/_index.md


 ### Manage `viam-server`

-To learn how to run, update, or uninstall `viam-server`, see [Manage `viam-server`](/installation/manage/).
+To learn how to run, update, or uninstall `viam-server`, see [Manage `viam-server`](/installation/manage-viam-server/).


Same as above, only applies to AppImage install method.

Otterverse · 2024-08-15T21:21:19Z

docs/fleet/provision.md

+| ---------- | ------ | --------- | ----------- |
+| `manufacturer` | string | Optional | Purely informative. May be displayed on captive portal and/or mobile app. Default: `"viam"`. |
+| `model` | string | Optional | Purely informative. May be displayed on captive portal and/or mobile app. Default: `"custom"`. |
+| `fragment_id` | string | Optional | The `fragment_id` of the fragment to configure machines with. If present, the Viam mobile app can pre-configure a robot for a user by using this [TODO: and otherwise it can't??]. |


Currently, we expect a fragment with our Mobile App experience. The mobile app is responsible for adding said fragment to the newly created machine's configuration.

docs/fleet/provision.md

Otterverse · 2024-08-15T21:23:12Z

docs/fleet/provision.md

+| `hotspot_prefix` | string | Optional | Viam agent will prepend this to the hostname of the device append and use the resulting string for the provisioning hotspot SSID. Default: `"viam-setup"`. |
+| `disable_dns_redirect` | boolean | Optional | By default, ALL DNS lookups using the provisioning hotspot will redirect to the device. This causes most phones/mobile devices to automatically redirect the user to the captive portal as a "sign in" screen. When disabled, only domains ending in .setup (ex: viam.setup) will be redirected. This generally avoids displaying the portal to users and is mainly used in conjunction with a mobile provisioning application workflow. Default: `false`. |
+| `hotspot_password` | string | Optional | The Wifi password for provisioning hotspot. Default: `"viamsetup"`. |
+| `roaming_mode` | boolean | Optional | By default, the device will only attempt to connect to a single wifi network (the one with the highest priority), usually provided during initial provisioning/setup using the Viam app or the Viam mobile app. Wifi connection alone is enough to consider the device as "online" even if the global internet is not reachable. When enabled, the device will attempt connections to all configured networks, and only considers the device online if the internet is reachable. See [roaming mode](#how-an-end-user-would-use-it). Default: `false`. |


Suggested change

| `roaming_mode` | boolean | Optional | By default, the device will only attempt to connect to a single wifi network (the one with the highest priority), usually provided during initial provisioning/setup using the Viam app or the Viam mobile app. Wifi connection alone is enough to consider the device as "online" even if the global internet is not reachable. When enabled, the device will attempt connections to all configured networks, and only considers the device online if the internet is reachable. See [roaming mode](#how-an-end-user-would-use-it). Default: `false`. |

| `roaming_mode` | boolean | Optional | By default, the device will only attempt to connect to a single wifi network (the one with the highest priority), usually provided during initial setup using the Viam mobile app or captive web portal. Wifi connection alone is enough to consider the device as "online" even if the global internet is not reachable. When enabled, the device will instead attempt connections to all configured networks, and only considers the device online if the internet is reachable. See [roaming mode](#how-an-end-user-would-use-it). Default: `false`. |

docs/fleet/provision.md

Otterverse · 2024-08-15T21:25:26Z

docs/fleet/provision.md

+| `offline_timeout` | boolean | Optional | Will only enter provisioning mode (hotspot) after being disconnected longer than this time. Useful on flaky connections, or when part of a system where the device may start quickly, but the wifi/router may take longer to be available. Default: `"2m"` (2 minutes). |
+| `user_timeout` | boolean | Optional | Amount of time before considering a user (using the provisioning portal using web or mobile app) idle, and resuming normal behavior. Used to avoid interrupting provisioning mode (for example for network tests/retries) when a user might be busy entering details. Default: `"5m"` (5 minutes). |
+| `fallback_timeout` | boolean | Optional | Provisioning mode will exit after this time, to allow other unmanaged (for example wired) or manually configured connections to be tried. Provisioning mode will restart if the connection/online status doesn't change. Default: `"10m"` (10 minutes). |
+| `networks` | boolean | Optional | The type of the network. See [Networks](/configure/agent/#networks). Default: `[]`. |


This is a complex structure, (same as in attributes.) It's not just "the type of the network." While it CAN be set here, it's advised/preferred that manufacturers instead directly enter wifi settings in the OS (e.g. directly in NetworkManager.)

docs/configure/agent.md

npentrel · 2024-08-16T14:57:46Z

docs/configure/agent.md

+<!-- prettier-ignore -->
+| Option | Type | Required? | Description |
+| ------ | ---- | --------- | ----------- |
+| `attributes` | object | Optional | <ul><li>`logging`: parameters for logging<ul>`disable`: when set to `true`, removes any prior tweaks to the logging config and disables the use of defaults??.<li>`system_max_use`: sets the maximum disk space journald will user for persistent log storage. Numeric values are in bytes, with optional single letter suffix for larger units, for example. K, M, or G. Default: `512M`.</li><li>`runtime_max_use`: sets the runtime/temporary limit. Numeric values are in bytes, with optional single letter suffix for larger units, for example. K, M, or G. Default: `512M`.</li></ul></li><li>`upgrades`: Using `upgrades` installs the `unattended-upgrades` package, and replace `20auto-upgrades` and `50unattended-upgrades` in <FILE>/etc/apt/apt.conf.d/</FILE>, with the latter's Origins-Pattern list being generated automatically from configured repositories on the system, so custom repos (at the time the setting is enabled) will be included.<ul><li>`type`: Configured unattended upgrades for Debian bullseye and bookworm. Options: `""` (no effect), `"disable"` (disables automatic upgrades), `"security"` (only enables updates from sources with security in their codename, ex: bookworm-security), `"all"` (enable updates from all configured sources).</li></ul></li></ul> |


@Otterverse I don't understand the disable option. It disables the use of defaults? What does that mean?

Co-authored-by: Sierra Guequierre <[email protected]> Co-authored-by: James Otting <[email protected]>

Otterverse

Only a few more things it looks like. Much better overall, IMHO! Thanks for dealing with all my suggestions from yesterday.

docs/fleet/provision.md

Otterverse · 2024-08-16T18:20:17Z

docs/fleet/provision.md


-### View Viam Agent logs
+   - The [`agent-provisioning` configuration](#configuration) is at <file>/etc/viam-provisioning.json</file.
+   - The [`viam-agent` configuration](/configure/agent/#configuration), if provided, is at <file>/etc/viam.json</file> alongside the rest of the machine configuration, including which fragments to use (if any).


This is not correct. The machine configuration (including fragments) is in the cloud/App. /etc/viam.json contains the machine credentials to connect TO the cloud.

Otterverse · 2024-08-16T18:21:47Z

docs/fleet/provision.md

-If your machine is offline, log messages are queued, and are sent to the Viam app once your machine reconnects to the internet.
+   - By default, the hotspot network is named `viam-setup-HOSTNAME`, where `HOSTNAME` is replaced with the hostname of your machine.
+     The WiFi password for this hotspot network is `viamsetup` by default.
+     You can customize these values in the machine's or fragment's [`viam-agent` configuration](/configure/agent/#configuration).


These are mostly meant to be customized in the provisioning configuration (/etc/viam-provisioning.json), not the Cloud configuration, as only that can be read/used when offline (e.g. before the user has first provisioned the machine.)

that makes sense but why is it configurable in the agent config as well then?

maybe it isn't

Can you check the attributes in https://docs-test.viam.dev/3243/configure/agent/#agent-provisioning

Otterverse · 2024-08-16T18:22:43Z

docs/fleet/provision.md


-The Viam Agent writes log messages to the [Viam app](https://app.viam.com/).
-You can find these messages on the [**LOGS** tab](/cloud/machines/#logs) of your machine's page.
+1. The end user uses their mobile device or computer and connects to the WiFi hotspot.


If they're using the mobile app, they should open that first (while still on the internet) and follow the instructions there. (It needs to do stuff BEFORE connecting to the hotspot, and will then tell the user when to switch networks to the hotspot.)

docs/fleet/provision.md

docs/installation/_index.md

Otterverse · 2024-08-16T18:34:43Z

docs/installation/_index.md

+{{< alert title="Linux: Automatic startup" color="note" >}}
+On manual Linux installs, `viam-server` will start automatically when your system boots.
+You can [change this behavior](/installation/manage-viam-server/) if desired.
+{{< /alert >}}


This happens for agent too, just how you manage it is slightly different (e.g. it's the viam-agent service, instead of the viam-server service.)

Otterverse · 2024-08-16T18:38:07Z

docs/installation/manage-viam-agent.md

+  ```sh {class="command-line" data-prompt="$"}
+  sudo systemctl restart viam-agent
+  ```
+


This should probably also include the enable and disable commands (similar to what's on the viam-server version of this page) The commands are almost the same, "viam-server" just becomes "viam-agent" in each.

Still think this would be good to add, especially as this is now linked from the alert about "Automatic Startup"

Co-authored-by: James Otting <[email protected]>

npentrel · 2024-08-16T19:57:35Z

docs/configure/agent.md

+<!-- prettier-ignore -->
+| Option | Type | Required? | Description |
+| ------ | ---- | --------- | ----------- |
+| `attributes` | object | Optional | <ul><li>`hotspot_password`: Set a password for the WiFi hotspot a machine creates during provisioning.</li><li>`networks`: Networks a machine can automatically connect to when roaming mode is enabled in the [`agent-provision`](/fleet/provision/#configuration) and either no primary network was configured by the end user in the provisioning app or the primary network cannot be connected to. See [#networks].</li><li>`roaming_mode`: If enabled, lets the machine connect to additional configured netowrks. See [Networks](#networks).</li></ul> |


@Otterverse can you check these? Is hotspot_password meant to be configurable here? Maybe I put that here wrong.

Under the hood, everything in provisioning's "attributes" is/can be identical to that in "/etc/viam-provisioning.json" The on-machine file is meant to be customized by the manufacturer, to provide "out of the box" settings. The attributes (in the cloud config) can let the user override those if they wish, but (as it's in the cloud) only after the machine gets online. Most of the initial stuff (like manufactuer, model, fragment_id, etc) the user generally shouldn't change, but the hotspot_password is one they can/should (for security), along with roaming_mode and any additional networks they want to configure. Anything here overrides what is set by the manufacturer in "/etc/viam-provisioning.json"

Ok, I'll add that it overrides those settings and add the rest of the settings I guess.

Sorry, wasn't saying you need to add that specifically. Was clarifying for YOUR understanding primarily. The reason for only listing SOME of the available options here is that it's only recommended to change these (for the end user.)

I understand - I think if I didn't understand it other might not either, so I think adding it might be good

Co-authored-by: James Otting <[email protected]>

docs/installation/_index.md

Otterverse

A couple small notes, but nothing critical, so I'll approve this for now. As mentioned though, I think it would be nice (but not required) to clean up the mobile app provisioning description, and to add the enable/disable commands to the "manage viam-agent" page.

docs/configure/agent.md

Otterverse · 2024-08-16T20:38:43Z

docs/configure/agent.md

+<!-- prettier-ignore -->
+| Option | Type | Required? | Description |
+| ------ | ---- | --------- | ----------- |
+| `attributes` | object | Optional | <ul><li>`hotspot_password`: Set a password for the WiFi hotspot a machine creates during provisioning.</li><li>`networks`: Networks a machine can automatically connect to when roaming mode is enabled in the [`agent-provision`](/fleet/provision/#configuration) and either no primary network was configured by the end user in the provisioning app or the primary network cannot be connected to. See [#networks].</li><li>`roaming_mode`: If enabled, lets the machine connect to additional configured netowrks. See [Networks](#networks).</li></ul> |


Sorry, wasn't saying you need to add that specifically. Was clarifying for YOUR understanding primarily. The reason for only listing SOME of the available options here is that it's only recommended to change these (for the end user.)

Otterverse · 2024-08-16T20:43:58Z

docs/fleet/provision.md


-### Manage the Viam Agent
+{{< tabs >}}
+{{% tab name="Mobile app" min-height="703px" %}}


I'm unclear on the mobile app flow. Previously (when I last used it) you could only use it to provision NEW machines. If that's still the case, then the reference below to where configuration is for machines that already exist is pointless (but also unlikely to be harmful.) I'm fine with it either way, so I'll leave this section for @ale7714 to sign off on.

I'll remove it.

for now, will actually test this in the next week

npentrel · 2024-08-16T20:51:54Z

docs/configure/agent.md

+<!-- prettier-ignore -->
+| Option | Type | Required? | Description |
+| ------ | ---- | --------- | ----------- |
+| `attributes` | object | Optional | <ul><li>`hotspot_password`: Set a password for the WiFi hotspot a machine creates during provisioning.</li><li>`networks`: Networks a machine can automatically connect to when roaming mode is enabled in the [`agent-provision`](/fleet/provision/#configuration) and either no primary network was configured by the end user in the provisioning app or the primary network cannot be connected to. See [#networks].</li><li>`roaming_mode`: If enabled, lets the machine connect to additional configured netowrks. See [Networks](#networks).</li></ul> |


Suggested change

| `attributes` | object | Optional | <ul><li>`hotspot_password`: Set a password for the WiFi hotspot a machine creates during provisioning.</li><li>`networks`: Networks a machine can automatically connect to when roaming mode is enabled in the [`agent-provision`](/fleet/provision/#configuration) and either no primary network was configured by the end user in the provisioning app or the primary network cannot be connected to. See [#networks].</li><li>`roaming_mode`: If enabled, lets the machine connect to additional configured netowrks. See [Networks](#networks).</li></ul> |

| `attributes` | object | Optional | <ul><li>`hotspot_password`: Set a password for the WiFi hotspot a machine creates during provisioning.</li><li>`networks`: Networks a machine can automatically connect to when roaming mode is enabled in the [`agent-provision`](/fleet/provision/#configuration) and either no primary network was configured by the end user in the provisioning app or the primary network cannot be connected to. See [networks](#networks).</li><li>`roaming_mode`: If enabled, lets the machine connect to additional configured netowrks. See [Networks](#networks).</li></ul> |

docs/fleet/provision.md

viambot · 2024-08-16T21:04:07Z

You can view a rendered version of the docs from this PR at https://docs-test.viam.dev/3243

viambot added the safe to build This pull request is marked safe to build from a trusted zone label Aug 13, 2024

npentrel changed the title ~~Update install and agent docs~~ DOCS-2046: Update install and agent docs Aug 13, 2024

npentrel force-pushed the viam-agent-full branch from 77081c3 to 8e18263 Compare August 13, 2024 12:47

npentrel mentioned this pull request Aug 13, 2024

DOCS-2581: Make provisioning accept non-internet wifi #3242

Closed

npentrel force-pushed the viam-agent-full branch 9 times, most recently from abb4345 to 7b710fa Compare August 14, 2024 18:24

sguequierre reviewed Aug 14, 2024

View reviewed changes

npentrel force-pushed the viam-agent-full branch 10 times, most recently from 53fec63 to 6ddd704 Compare August 15, 2024 18:20

npentrel requested review from Otterverse and ale7714 August 15, 2024 18:21

Update install and agent docs

16aa33f

npentrel force-pushed the viam-agent-full branch from 6ddd704 to 16aa33f Compare August 15, 2024 18:27

Otterverse requested changes Aug 15, 2024

View reviewed changes

npentrel commented Aug 16, 2024

View reviewed changes

docs/configure/agent.md Outdated Show resolved Hide resolved

npentrel force-pushed the viam-agent-full branch 5 times, most recently from 0c603b8 to d6137c4 Compare August 16, 2024 14:23

npentrel commented Aug 16, 2024

View reviewed changes

npentrel force-pushed the viam-agent-full branch 2 times, most recently from d704175 to 9432ade Compare August 16, 2024 16:15

npentrel requested a review from Otterverse August 16, 2024 16:18

npentrel force-pushed the viam-agent-full branch 2 times, most recently from 6ff5ae1 to 162df2c Compare August 16, 2024 16:38

Apply suggestions from code review

efa532d

Co-authored-by: Sierra Guequierre <[email protected]> Co-authored-by: James Otting <[email protected]>

npentrel force-pushed the viam-agent-full branch from 162df2c to efa532d Compare August 16, 2024 16:39

Otterverse requested changes Aug 16, 2024

View reviewed changes

npentrel and others added 2 commits August 16, 2024 21:21

Apply suggestions from code review

6f0400d

Co-authored-by: James Otting <[email protected]>

Updates

9c26636

npentrel commented Aug 16, 2024

View reviewed changes

npentrel requested a review from Otterverse August 16, 2024 19:57

Apply suggestions from code review

2a716a9

Co-authored-by: James Otting <[email protected]>

npentrel commented Aug 16, 2024

View reviewed changes

docs/installation/_index.md Outdated Show resolved Hide resolved

npentrel added 2 commits August 16, 2024 22:05

Update docs/installation/_index.md

f43b84f

Update the agent provisioning config attributes

172293d

npentrel force-pushed the viam-agent-full branch from 22c2df3 to 172293d Compare August 16, 2024 20:18

Otterverse approved these changes Aug 16, 2024

View reviewed changes

npentrel commented Aug 16, 2024

View reviewed changes

docs/fleet/provision.md Outdated Show resolved Hide resolved

Update docs/fleet/provision.md

356faf5

npentrel merged commit 4194100 into viamrobotics:main Aug 16, 2024
9 checks passed

npentrel deleted the viam-agent-full branch August 16, 2024 21:07

	To see how to provision machines using `viam-agent`, see
	To provision machines using `viam-agent`, see


		1. Create a configuration file with the desired configuration for your machine. You can:

		- [create a new machine in the Viam app](/cloud/machines/#add-a-new-machine) and configure it as desired or use an existing deployed machine, then switch to Raw JSON mode and copy the configuration shown into a new file on your machine.

	When `viam-agent` updates either itself or `viam-server`, you must [restart these services](/installation/manage-viam-agent/) in order to use the new version.
	When `viam-agent` updates either itself or `viam-server`, you must [restart these system services](/installation/manage-viam-agent/) in order to use the new version.

	If your machine is offline, log messages are queued, and are sent to the Viam app once your machine reconnects to the internet.
	If your machine is offline, log messages are queued and are sent to the Viam app once your machine reconnects to the internet.

DOCS-2046: Update install and agent docs #3243

DOCS-2046: Update install and agent docs #3243

Conversation

npentrel commented Aug 13, 2024 • edited Loading

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

Otterverse 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

Otterverse Aug 15, 2024 • edited by npentrel Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Otterverse 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

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

Otterverse 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

viambot commented Aug 16, 2024

npentrel commented Aug 13, 2024 •

edited

Loading

Otterverse Aug 15, 2024 •

edited by npentrel

Loading