Forum post (thread) message_count updates #5206

Tin · 2022-07-18T21:33:36Z

Document API fields updates around forum post (thread)'s new message counter capability.

vvito7 · 2022-07-18T21:34:02Z

docs/resources/Channel.md

@@ -28,13 +28,14 @@ Represents a guild or DM channel within Discord.
 | last_pin_timestamp?            | ?ISO8601 timestamp                                                         | when the last pinned message was pinned. This may be `null` in events such as `GUILD_CREATE` when a message is not pinned.                                                                      |
 | rtc_region?                    | ?string                                                                    | [voice region](#DOCS_RESOURCES_VOICE/voice-region-object) id for the voice channel, automatic when set to null                                                                                  |
 | video_quality_mode?            | integer                                                                    | the camera [video quality mode](#DOCS_RESOURCES_CHANNEL/channel-object-video-quality-modes) of the voice channel, 1 when not present                                                            |
-| message_count?                 | integer                                                                    | an approximate count of messages in a thread, stops counting at 50                                                                                                                              |
+| message_count?                 | integer                                                                    | count of messages (not including starter message and deleted messsages) in a thread, stops counting at 100_000 (if the thread is created before July 1, 2022, it stops at 50)        |


Suggested change

| message_count? | integer | count of messages (not including starter message and deleted messsages) in a thread, stops counting at 100_000 (if the thread is created before July 1, 2022, it stops at 50) |

| message_count? | integer | count of messages (not including starter message and deleted messages) in a thread, stops counting at 100000 (if the thread is created before July 1, 2022, it stops at 50) |

it's easier to read with the underscore

Suggested change

| message_count? | integer | count of messages (not including starter message and deleted messsages) in a thread, stops counting at 100_000 (if the thread is created before July 1, 2022, it stops at 50) |

| message_count? | integer | total number of messages in the thread excluding starter message, stops counting at 100_000 (or if the thread was created before 1 July 2022, 50) |

vvito7 · 2022-07-18T21:34:24Z

docs/resources/Channel.md

 | member_count?                  | integer                                                                    | an approximate count of users in a thread, stops counting at 50                                                                                                                                 |
 | thread_metadata?               | a [thread metadata](#DOCS_RESOURCES_CHANNEL/thread-metadata-object) object | thread-specific fields not needed by other channels                                                                                                                                             |
 | member?                        | a [thread member](#DOCS_RESOURCES_CHANNEL/thread-member-object) object     | thread member object for the current user, if they have joined the thread, only included on certain API endpoints                                                                               |
 | default_auto_archive_duration? | integer                                                                    | default duration that the clients (not the API) will use for newly created threads, in minutes, to automatically archive the thread after recent activity, can be set to: 60, 1440, 4320, 10080 |
 | permissions?                   | string                                                                     | computed permissions for the invoking user in the channel, including overwrites, only included when part of the `resolved` data received on a slash command interaction                         |
 | flags?                         | integer                                                                    | [channel flags](#DOCS_RESOURCES_CHANNEL/channel-object-channel-flags) combined as a [bitfield](https://en.wikipedia.org/wiki/Bit_field)                                                         |
+| total_message_sent?            | integer                                                                    | count of total messages ever sent in a thread, it's similar to `message_count` on message creation, but decrement on message deletion. |


Suggested change

| total_message_sent? | integer | count of total messages ever sent in a thread, it's similar to `message_count` on message creation, but decrement on message deletion. |

| total_message_sent? | integer | count of total messages ever sent in a thread, it's similar to `message_count` on message creation, but decrement on message deletion |

vvito7 · 2022-07-18T21:36:09Z

docs/topics/Threads.md

+- `message_count` and `total_message_sent` store messages count in a thread. The difference is that the `message_count` decrement when there's message deleted, but `total_message_count` will not change in this case. They stop
+  counting at 100_000. (The UI shows "100k+", and then it will stop counting) Thread before July 1, 2022 caps at 50.


Suggested change

- `message_count` and `total_message_sent` store messages count in a thread. The difference is that the `message_count` decrement when there's message deleted, but `total_message_count` will not change in this case. They stop

counting at 100_000. (The UI shows "100k+", and then it will stop counting) Thread before July 1, 2022 caps at 50.

- `message_count` and `total_message_sent` store messages count in a thread. The difference is that the `message_count` decrement when there's message deleted, but `total_message_count` will not change in this case. They stop counting at 100000 (the UI shows "100k+", and then it will stop counting). Thread before July 1, 2022 caps at 50.

Suggested change

- `message_count` and `total_message_sent` store messages count in a thread. The difference is that the `message_count` decrement when there's message deleted, but `total_message_count` will not change in this case. They stop

counting at 100_000. (The UI shows "100k+", and then it will stop counting) Thread before July 1, 2022 caps at 50.

- `message_count` and `total_message_sent` store the amount of messages in a thread. The difference is that when a message is deleted, `message_count` is decremented, but `total_message_sent` will not. Both of these properties stop counting at 100_000 (the UI shows 100k+), except in threads created before July 1, 2022, in which case it stops at 50.

ajpalkovic · 2022-07-18T21:51:39Z

docs/resources/Channel.md

@@ -28,13 +28,14 @@ Represents a guild or DM channel within Discord.
 | last_pin_timestamp?            | ?ISO8601 timestamp                                                         | when the last pinned message was pinned. This may be `null` in events such as `GUILD_CREATE` when a message is not pinned.                                                                      |
 | rtc_region?                    | ?string                                                                    | [voice region](#DOCS_RESOURCES_VOICE/voice-region-object) id for the voice channel, automatic when set to null                                                                                  |
 | video_quality_mode?            | integer                                                                    | the camera [video quality mode](#DOCS_RESOURCES_CHANNEL/channel-object-video-quality-modes) of the voice channel, 1 when not present                                                            |
-| message_count?                 | integer                                                                    | an approximate count of messages in a thread, stops counting at 50                                                                                                                              |
+| message_count?                 | integer                                                                    | count of messages (not including starter message and deleted messsages) in a thread, stops counting at 100_000 (if the thread is created before July 1, 2022, it stops at 50)        |


I don't think we should document the upper limit, it's something that can change in the future, you've even expressed desires to change it, and there's always push back when changing documented things. It's probably fine t say it'll always be a 32 bit integer though

ajpalkovic · 2022-07-18T21:52:26Z

docs/resources/Channel.md

 | member_count?                  | integer                                                                    | an approximate count of users in a thread, stops counting at 50                                                                                                                                 |
 | thread_metadata?               | a [thread metadata](#DOCS_RESOURCES_CHANNEL/thread-metadata-object) object | thread-specific fields not needed by other channels                                                                                                                                             |
 | member?                        | a [thread member](#DOCS_RESOURCES_CHANNEL/thread-member-object) object     | thread member object for the current user, if they have joined the thread, only included on certain API endpoints                                                                               |
 | default_auto_archive_duration? | integer                                                                    | default duration that the clients (not the API) will use for newly created threads, in minutes, to automatically archive the thread after recent activity, can be set to: 60, 1440, 4320, 10080 |
 | permissions?                   | string                                                                     | computed permissions for the invoking user in the channel, including overwrites, only included when part of the `resolved` data received on a slash command interaction                         |
 | flags?                         | integer                                                                    | [channel flags](#DOCS_RESOURCES_CHANNEL/channel-object-channel-flags) combined as a [bitfield](https://en.wikipedia.org/wiki/Bit_field)                                                         |
+| total_message_sent?            | integer                                                                    | count of total messages ever sent in a thread, it's similar to `message_count` on message creation, but decrement on message deletion. |


Isn't this wrong, it's never decremented, right?

missed the "will not" 🤦

onerandomusername · 2022-07-18T21:54:47Z

What is the purpose of position, genuine question. I can't think of a usecase off the top of my head for bot devs.

ajpalkovic · 2022-07-18T21:55:39Z

docs/resources/Channel.md

@@ -266,6 +268,7 @@ Represents a message sent in a channel within Discord.
 | components?               | Array of [message components](#DOCS_INTERACTIONS_MESSAGE_COMPONENTS/component-object)                                              | sent if the message contains components like buttons, action rows, or other interactive components                                               |
 | sticker_items?            | array of [message sticker item objects](#DOCS_RESOURCES_STICKER/sticker-item-object)                                               | sent if the message contains stickers                                                                                                            |
 | stickers?                 | array of [sticker](#DOCS_RESOURCES_STICKER/sticker-object) objects                                                                 | **Deprecated** the stickers sent with the message                                                                                                |
+| position?                 | integer                                                                                                                            | position of the message in a forum post when it was sent, it will not change upon any message deletion in the parent post                    |


I think this is for all threads, not just forum posts, right?
I'd suggest: "A generally increasing integer (there may be gaps or duplicates) that represents the approximate position of the message in a thread."

onerandomusername

Should there be a note on the gateway reference for Thread Update which mentions that total_message_sent and message_count do not send THREAD_UPDATE events? This would be in line with the documentation surrounding last_message_id.

splatterxl · 2022-07-18T22:47:28Z

docs/resources/Channel.md

 | member_count?                  | integer                                                                    | an approximate count of users in a thread, stops counting at 50                                                                                                                                 |
 | thread_metadata?               | a [thread metadata](#DOCS_RESOURCES_CHANNEL/thread-metadata-object) object | thread-specific fields not needed by other channels                                                                                                                                             |
 | member?                        | a [thread member](#DOCS_RESOURCES_CHANNEL/thread-member-object) object     | thread member object for the current user, if they have joined the thread, only included on certain API endpoints                                                                               |
 | default_auto_archive_duration? | integer                                                                    | default duration that the clients (not the API) will use for newly created threads, in minutes, to automatically archive the thread after recent activity, can be set to: 60, 1440, 4320, 10080 |
 | permissions?                   | string                                                                     | computed permissions for the invoking user in the channel, including overwrites, only included when part of the `resolved` data received on a slash command interaction                         |
 | flags?                         | integer                                                                    | [channel flags](#DOCS_RESOURCES_CHANNEL/channel-object-channel-flags) combined as a [bitfield](https://en.wikipedia.org/wiki/Bit_field)                                                         |
+| total_message_sent?            | integer                                                                    | count of total messages ever sent in a thread, it's similar to `message_count` on message creation, but decrement on message deletion. |


Suggested change

| total_message_sent? | integer | count of total messages ever sent in a thread, it's similar to `message_count` on message creation, but decrement on message deletion. |

| total_message_sent? | integer | count of all messages ever sent in the thread, does not decrement on message deletion |

Also, shouldn't this be named total_messages_sent as a plural?

advaith1 · 2022-07-18T23:10:17Z

docs/topics/Threads.md

@@ -34,7 +34,8 @@ Since threads are a new [type of channel](#DOCS_RESOURCES_CHANNEL/channel-object

 Additionally, there are a few new fields that are only available on threads:

- `message_count` and `member_count` store an approximate count, but they stop counting at 50 (these are only used in our UI, so likely are not valuable to bots)
+- `member_count` store an approximate member count, but it stop counting at 50 (these are only used in our UI, so likely are not valuable to bots)
+- `message_count` and `total_message_sent` store the amount of messages in a thread. The difference is that when a message is deleted, `message_count` is decremented, but `total_message_count` will not be. (threads created before July 1, 2022 stops counting both value at 50).


Suggested change

- `message_count` and `total_message_sent` store the amount of messages in a thread. The difference is that when a message is deleted, `message_count` is decremented, but `total_message_count` will not be. (threads created before July 1, 2022 stops counting both value at 50).

- `message_count` and `total_message_sent` store the number of messages in a thread. The difference is that when a message is deleted, `message_count` is decremented, but `total_message_sent` will not be. (threads created before July 1, 2022 stop counting both values at 50).

says total_message_count here too

advaith1 · 2022-07-18T23:12:02Z

docs/resources/Channel.md

+| message_count?                 | integer                                                                    | amount of messages (not including the initial message or deleted messages) in a thread (if the thread was created before July 1, 2022, it stops counting at 50)        |
+| member_count?                  | integer                                                                    | an approximate count of users in a thread, stops counting at 50                   |
 | thread_metadata?               | a [thread metadata](#DOCS_RESOURCES_CHANNEL/thread-metadata-object) object | thread-specific fields not needed by other channels                                                                                                                                             |
 | member?                        | a [thread member](#DOCS_RESOURCES_CHANNEL/thread-member-object) object     | thread member object for the current user, if they have joined the thread, only included on certain API endpoints                                                                               |
 | default_auto_archive_duration? | integer                                                                    | default duration that the clients (not the API) will use for newly created threads, in minutes, to automatically archive the thread after recent activity, can be set to: 60, 1440, 4320, 10080 |
 | permissions?                   | string                                                                     | computed permissions for the invoking user in the channel, including overwrites, only included when part of the `resolved` data received on a slash command interaction                         |
 | flags?                         | integer                                                                    | [channel flags](#DOCS_RESOURCES_CHANNEL/channel-object-channel-flags) combined as a [bitfield](https://en.wikipedia.org/wiki/Bit_field)                                                         |
+| total_message_sent?            | integer                                                                    | amount of messages ever sent in a thread, it's similar to `message_count` on message creation, but will not decrement the amount when a message is deleted            |


Suggested change

| message_count? | integer | amount of messages (not including the initial message or deleted messages) in a thread (if the thread was created before July 1, 2022, it stops counting at 50) |

| member_count? | integer | an approximate count of users in a thread, stops counting at 50 |

| thread_metadata? | a [thread metadata](#DOCS_RESOURCES_CHANNEL/thread-metadata-object) object | thread-specific fields not needed by other channels |

| member? | a [thread member](#DOCS_RESOURCES_CHANNEL/thread-member-object) object | thread member object for the current user, if they have joined the thread, only included on certain API endpoints |

| default_auto_archive_duration? | integer | default duration that the clients (not the API) will use for newly created threads, in minutes, to automatically archive the thread after recent activity, can be set to: 60, 1440, 4320, 10080 |

| permissions? | string | computed permissions for the invoking user in the channel, including overwrites, only included when part of the `resolved` data received on a slash command interaction |

| flags? | integer | [channel flags](#DOCS_RESOURCES_CHANNEL/channel-object-channel-flags) combined as a [bitfield](https://en.wikipedia.org/wiki/Bit_field) |

| total_message_sent? | integer | amount of messages ever sent in a thread, it's similar to `message_count` on message creation, but will not decrement the amount when a message is deleted |

| message_count? | integer | amount of messages (not including the initial message or deleted messages) in a thread (if the thread was created before July 1, 2022, it stops counting at 50) |

| member_count? | integer | an approximate count of users in a thread, stops counting at 50 |

| thread_metadata? | a [thread metadata](#DOCS_RESOURCES_CHANNEL/thread-metadata-object) object | thread-specific fields not needed by other channels |

| member? | a [thread member](#DOCS_RESOURCES_CHANNEL/thread-member-object) object | thread member object for the current user, if they have joined the thread, only included on certain API endpoints |

| default_auto_archive_duration? | integer | default duration that the clients (not the API) will use for newly created threads, in minutes, to automatically archive the thread after recent activity, can be set to: 60, 1440, 4320, 10080 |

| permissions? | string | computed permissions for the invoking user in the channel, including overwrites, only included when part of the `resolved` data received on a slash command interaction |

| flags? | integer | [channel flags](#DOCS_RESOURCES_CHANNEL/channel-object-channel-flags) combined as a [bitfield](https://en.wikipedia.org/wiki/Bit_field) |

| total_message_sent? | integer | amount of messages ever sent in a thread, it's similar to `message_count` on message creation, but will not decrement the amount when a message is deleted |

table formatting

Tin · 2022-07-18T23:27:25Z

@splatterxl @advaith1 @onerandomusername @MidSpike @vvito7 @ajpalkovic Thanks for the reviews, let me know if this new version makes sense.

ajpalkovic · 2022-07-18T23:36:22Z

docs/topics/Threads.md

@@ -34,7 +34,8 @@ Since threads are a new [type of channel](#DOCS_RESOURCES_CHANNEL/channel-object

 Additionally, there are a few new fields that are only available on threads:

- `message_count` and `member_count` store an approximate count, but they stop counting at 50 (these are only used in our UI, so likely are not valuable to bots)
+- `member_count` store an approximate member count, but it stop counting at 50 (these are only used in our UI, so likely are not valuable to bots)


store -> stores
stop -> stops

Suggested change

- `member_count` store an approximate member count, but it stop counting at 50 (these are only used in our UI, so likely are not valuable to bots)

- `member_count` stores an approximate member count, but it stops counting at 50 (this is only used in our UI, so it is likely not valuable to bots)

edits the note too

advaith1 · 2022-07-18T23:49:19Z

docs/topics/Threads.md

@@ -183,6 +184,7 @@ Listed below are some of the important details of forum channels and are safe to
 - The API to create a thread in a forum will create _both_ a thread and message in the same call, and as such requires passing in parameters for both the thread and message. The name and behavior of parameters is the same as they are for the existing create thread/message endpoints to simplify integrating with it.
 - The message created by that API call will have the same id as the thread.
 - The `last_message_id` field on the forum channel object tracks the id of the most recently created thread. It has the same behavior and requirements as it does for messages, namely that you will not receive a `CHANNEL_UPDATE` when it is changed. Instead clients should update the value when receiving [Thread Create](#DOCS_TOPICS_GATEWAY/thread-create).
+- The `message_count` and `total_message_count` will increment on `MESSAGE_CREATE` and will decrement on `MESSAGE_DELETE`/`MESSAGE_DELETE_BULK`. There will be no `CHANNEL_UPDATE` event through gateway notifying those fields' changes (similar to `last_message_id` changes). Clients should update those values when receiving corresponding events.


Suggested change

- The `message_count` and `total_message_count` will increment on `MESSAGE_CREATE` and will decrement on `MESSAGE_DELETE`/`MESSAGE_DELETE_BULK`. There will be no `CHANNEL_UPDATE` event through gateway notifying those fields' changes (similar to `last_message_id` changes). Clients should update those values when receiving corresponding events.

- The `message_count` and `total_message_sent` will increment on `MESSAGE_CREATE` and will decrement on `MESSAGE_DELETE`/`MESSAGE_DELETE_BULK`. There will be no `CHANNEL_UPDATE` event through gateway notifying those fields' changes (similar to `last_message_id` changes). Clients should update those values when receiving corresponding events.

mistake in field name

splatterxl · 2022-07-19T12:52:09Z

lgtm

See discord/discord-api-docs#5206.

Forum post (thread) message_count updates

e69960d

Tin requested review from shaydewael and ajpalkovic July 18, 2022 21:33

vvito7 reviewed Jul 18, 2022

View reviewed changes

TAG-Epic mentioned this pull request Jul 18, 2022

Message counter update for docstrings nextsnake/nextcore#121

Closed

vvito7 mentioned this pull request Jul 18, 2022

feat(APIThreadChannel): add fields about new message counter capability discordjs/discord-api-types#532

Merged

ajpalkovic reviewed Jul 18, 2022

View reviewed changes

onerandomusername reviewed Jul 18, 2022

View reviewed changes

onerandomusername mentioned this pull request Jul 18, 2022

Support new thread and message attributes (position, message_count, total_message_sent) DisnakeDev/disnake#640

Closed

splatterxl reviewed Jul 18, 2022

View reviewed changes

Update message_count description based on PR feedback

72d40e7

advaith1 reviewed Jul 18, 2022

View reviewed changes

Add a section to explain no CHANNEL_UPDATE for message count changes

aec1312

Tin requested a review from ajpalkovic July 18, 2022 23:27

ajpalkovic reviewed Jul 18, 2022

View reviewed changes

ajpalkovic approved these changes Jul 18, 2022

View reviewed changes

advaith1 reviewed Jul 18, 2022

View reviewed changes

fixed some typos

ebeee7b

Tin force-pushed the forum-channel/message-counter-update branch from 4c4f147 to ebeee7b Compare July 19, 2022 15:41

change "amount" -> "number" to keep them consistent

6947898

Tin merged commit cdeb372 into main Jul 19, 2022

Tin deleted the forum-channel/message-counter-update branch July 19, 2022 15:44

almeidx mentioned this pull request Jul 19, 2022

feat: add support for guild forums discordjs/discord.js#7791

Merged

7596ff mentioned this pull request Jul 19, 2022

Forum Channels twilight-rs/twilight#1675

Closed

10 tasks

SQKo mentioned this pull request Jul 22, 2022

Add Thread total_message_sent and position, Add APPLICATION_COMMAND_BADGE, Add mention spam type and limits discord-php/DiscordPHP#864

Merged

Nihlus added a commit to Remora/Remora.Discord that referenced this pull request Jul 23, 2022

Add missing fields to channels and messages.

f246614

See discord/discord-api-docs#5206.

lukellmann mentioned this pull request Aug 30, 2022

Add forum channels kordlib/kord#592

Closed

10 tasks

lukellmann mentioned this pull request Sep 18, 2022

Implement forums kordlib/kord#684

Merged

38 tasks

NoComment1105 mentioned this pull request Nov 19, 2022

Message counts and position for channel and message kordlib/kord#726

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Forum post (thread) message_count updates #5206

Forum post (thread) message_count updates #5206

Tin commented Jul 18, 2022

vvito7 Jul 18, 2022

advaith1 Jul 18, 2022

splatterxl Jul 18, 2022 •

edited

Loading

vvito7 Jul 18, 2022

vvito7 Jul 18, 2022

splatterxl Jul 18, 2022

ajpalkovic Jul 18, 2022

ajpalkovic Jul 18, 2022

Tin Jul 18, 2022

onerandomusername commented Jul 18, 2022

ajpalkovic Jul 18, 2022

onerandomusername left a comment

splatterxl Jul 18, 2022 •

edited

Loading

advaith1 Jul 18, 2022 •

edited

Loading

advaith1 Jul 18, 2022 •

edited

Loading

advaith1 Jul 18, 2022

Tin commented Jul 18, 2022

ajpalkovic Jul 18, 2022

advaith1 Jul 18, 2022

advaith1 Jul 18, 2022

Tin Jul 19, 2022

splatterxl commented Jul 19, 2022

	\| message_count? \| integer \| count of messages (not including starter message and deleted messsages) in a thread, stops counting at 100_000 (if the thread is created before July 1, 2022, it stops at 50) \|
	\| message_count? \| integer \| count of messages (not including starter message and deleted messages) in a thread, stops counting at 100000 (if the thread is created before July 1, 2022, it stops at 50) \|

	\| message_count? \| integer \| count of messages (not including starter message and deleted messsages) in a thread, stops counting at 100_000 (if the thread is created before July 1, 2022, it stops at 50) \|
	\| message_count? \| integer \| total number of messages in the thread excluding starter message, stops counting at 100_000 (or if the thread was created before 1 July 2022, 50) \|

	\| total_message_sent? \| integer \| count of total messages ever sent in a thread, it's similar to `message_count` on message creation, but decrement on message deletion. \|
	\| total_message_sent? \| integer \| count of total messages ever sent in a thread, it's similar to `message_count` on message creation, but decrement on message deletion \|

		- `message_count` and `total_message_sent` store messages count in a thread. The difference is that the `message_count` decrement when there's message deleted, but `total_message_count` will not change in this case. They stop
		counting at 100_000. (The UI shows "100k+", and then it will stop counting) Thread before July 1, 2022 caps at 50.

	- `member_count` store an approximate member count, but it stop counting at 50 (these are only used in our UI, so likely are not valuable to bots)
	- `member_count` stores an approximate member count, but it stops counting at 50 (this is only used in our UI, so it is likely not valuable to bots)

	- The `message_count` and `total_message_count` will increment on `MESSAGE_CREATE` and will decrement on `MESSAGE_DELETE`/`MESSAGE_DELETE_BULK`. There will be no `CHANNEL_UPDATE` event through gateway notifying those fields' changes (similar to `last_message_id` changes). Clients should update those values when receiving corresponding events.
	- The `message_count` and `total_message_sent` will increment on `MESSAGE_CREATE` and will decrement on `MESSAGE_DELETE`/`MESSAGE_DELETE_BULK`. There will be no `CHANNEL_UPDATE` event through gateway notifying those fields' changes (similar to `last_message_id` changes). Clients should update those values when receiving corresponding events.

Forum post (thread) message_count updates #5206

Forum post (thread) message_count updates #5206

Conversation

Tin commented Jul 18, 2022

Choose a reason for hiding this comment

Choose a reason for hiding this comment

splatterxl Jul 18, 2022 • 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

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

onerandomusername commented Jul 18, 2022

Choose a reason for hiding this comment

onerandomusername left a comment

Choose a reason for hiding this comment

splatterxl Jul 18, 2022 • edited Loading

Choose a reason for hiding this comment

advaith1 Jul 18, 2022 • edited Loading

Choose a reason for hiding this comment

advaith1 Jul 18, 2022 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Tin commented Jul 18, 2022

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

splatterxl commented Jul 19, 2022

splatterxl Jul 18, 2022 •

edited

Loading

splatterxl Jul 18, 2022 •

edited

Loading

advaith1 Jul 18, 2022 •

edited

Loading

advaith1 Jul 18, 2022 •

edited

Loading