@mtcute/core 0.5.0 → 0.7.0

package/cjs/highlevel/types/media/web-page.d.ts

@@ -0,0 +1,151 @@
+import { tl } from '@mtcute/tl';
+import { RawDocument } from './document.js';
+import { Photo } from './photo.js';
+/**
+ * Web page preview.
+ *
+ * **Warning**: Documentation of this class also contains my
+ * personal research about how Telegram
+ * handles different pages and embeds. **By no means**
+ * this should be considered the definitive source of truth,
+ * as this is not documented officially, and only consists
+ * of my own observations and experiments.
+ */
+export declare class WebPage {
+    readonly raw: tl.RawWebPage;
+    readonly type: "webpage";
+    constructor(raw: tl.RawWebPage);
+    /**
+     * Unique ID of the preview
+     */
+    get id(): tl.Long;
+    /**
+     * Original page URL
+     */
+    get url(): string;
+    /**
+     * URL to be displayed to the user.
+     *
+     * Usually a normal URL with stripped protocol and garbage.
+     */
+    get displayUrl(): string;
+    /**
+     * Type of the preview, taken directly from TL object
+     *
+     * Officially documented are:
+     * `article, photo, audio, video, document, profile, app`,
+     * but also these are encountered:
+     * `telegram_user, telegram_bot, telegram_channel, telegram_megagroup, telegram_story`:
+     *
+     * - `telegram_*` ones seem to be used for `t.me` links.
+     * - `article` seems to be used for almost all custom pages with `og:*` tags
+     * - `photo`, `audio` and `video` seem to be derived from `og:type`,
+     *    and the page itself may contain a preview photo and an embed link
+     *    for the player. This may not correctly represent actual content type:
+     *    Spotify links are `audio`, but SoundCloud are `video`. YouTube links are `video`,
+     *    but tweets with video are `photo`.
+     * - `document` seem to be used for files downloadable directly from the URL,
+     *    like PDFs, audio files, videos, etc. {@link document} seem to be
+     *    present if `type` is `document`.
+     * - `profile` doesn't seem to be used
+     * - `app` doesn't seem to be used
+     *
+     * `unknown` is returned if no type is returned in the TL object.
+     */
+    get previewType(): string;
+    /**
+     * Page title
+     *
+     * Usually defined by `og:site_name` meta tag or website domain
+     */
+    get siteName(): string | null;
+    /**
+     * Page title
+     *
+     * Usually defined by `og:title` meta tag or `<title>` tag
+     */
+    get title(): string | null;
+    /**
+     * Page description
+     *
+     * Usually defined by `description` or `og:description` meta tag
+     */
+    get description(): string | null;
+    /**
+     * Page author
+     *
+     * The source for this is unknown, seems to be
+     * custom-made for services like Twitter.
+     *
+     * In official apps this seems to be used as a fallback for description.
+     */
+    get author(): string | null;
+    /**
+     * The embed URL.
+     *
+     * Based on my research, Telegram only allows
+     * embedding pages from a server-side white-list of domains.
+     *
+     * That is, you can't just copy-paste meta tags
+     * from YouTube to your own domain and expect Telegram
+     * to return a webpage with embed.
+     *
+     * IDK why is that, maybe they are concerned about
+     * leaking users' IPs to 3rd parties or something
+     * (but why allow embedding in the first place then?)
+     *
+     * Telegram for Android does not show "play" button for
+     * webpages without embeds, and instead treats it like a simple
+     * photo (why?).
+     *
+     * TDesktop does not support embeds and seems
+     * to use {@link type} to determine them, and specifically
+     * [checks](https://github.com/telegramdesktop/tdesktop/blob/3343880ed0e5a86accc7334af54b3470e29ee686/Telegram/SourceFiles/history/view/media/history_view_web_page.cpp#L561)
+     * for `YouTube` in {@link siteName} to display YouTube icon.
+     */
+    get embedUrl(): string | null;
+    /**
+     * Embed type.
+     *
+     * Now this is actually stupid.
+     * As per [official documentation](https://core.telegram.org/constructor/webPage),
+     * `embed_type` contains «MIME type of the embedded preview, (e.g., text/html or video/mp4)».
+     * But in fact every time I encountered it it contained a simple string `iframe`.
+     *
+     * I couldn't find any usage of this field in official apps either.
+     */
+    get embedType(): string | null;
+    /**
+     * Width of the embed in pixels, 0 if not available.
+     */
+    get embedWidth(): number;
+    /**
+     * Height of the embed in pixels, 0 if not available.
+     */
+    get embedHeight(): number;
+    /**
+     * A photo inside this webpage preview.
+     *
+     * Used for most of the preview types.
+     */
+    get photo(): Photo | null;
+    /**
+     * Document inside this webpage preview.
+     *
+     * Seems that this is only used for `document` previews.
+     *
+     * Can be a {@link Photo}, {@link Video},
+     * {@link Audio}, {@link Document}.
+     */
+    get document(): RawDocument | null;
+    /**
+     * Input media TL object generated from this object,
+     * to be used inside {@link InputMediaLike} and
+     * {@link TelegramClient.sendMedia}.
+     *
+     * WebPage can't provide an input media, since some
+     * can only be auto-generated from a link. This getter
+     * is only provided to allow using `msg.media.inputMedia`
+     */
+    get inputMedia(): tl.TypeInputMedia;
+}

package/cjs/highlevel/types/media/web-page.js

@@ -0,0 +1,197 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.WebPage = void 0;
+const errors_js_1 = require("../../../types/errors.js");
+const index_js_1 = require("../../utils/index.js");
+const memoize_js_1 = require("../../utils/memoize.js");
+const document_utils_js_1 = require("./document-utils.js");
+const photo_js_1 = require("./photo.js");
+/**
+ * Web page preview.
+ *
+ * **Warning**: Documentation of this class also contains my
+ * personal research about how Telegram
+ * handles different pages and embeds. **By no means**
+ * this should be considered the definitive source of truth,
+ * as this is not documented officially, and only consists
+ * of my own observations and experiments.
+ */
+class WebPage {
+    constructor(raw) {
+        this.raw = raw;
+        this.type = 'webpage';
+    }
+    /**
+     * Unique ID of the preview
+     */
+    get id() {
+        return this.raw.id;
+    }
+    /**
+     * Original page URL
+     */
+    get url() {
+        return this.raw.url;
+    }
+    /**
+     * URL to be displayed to the user.
+     *
+     * Usually a normal URL with stripped protocol and garbage.
+     */
+    get displayUrl() {
+        return this.raw.displayUrl;
+    }
+    /**
+     * Type of the preview, taken directly from TL object
+     *
+     * Officially documented are:
+     * `article, photo, audio, video, document, profile, app`,
+     * but also these are encountered:
+     * `telegram_user, telegram_bot, telegram_channel, telegram_megagroup, telegram_story`:
+     *
+     * - `telegram_*` ones seem to be used for `t.me` links.
+     * - `article` seems to be used for almost all custom pages with `og:*` tags
+     * - `photo`, `audio` and `video` seem to be derived from `og:type`,
+     *    and the page itself may contain a preview photo and an embed link
+     *    for the player. This may not correctly represent actual content type:
+     *    Spotify links are `audio`, but SoundCloud are `video`. YouTube links are `video`,
+     *    but tweets with video are `photo`.
+     * - `document` seem to be used for files downloadable directly from the URL,
+     *    like PDFs, audio files, videos, etc. {@link document} seem to be
+     *    present if `type` is `document`.
+     * - `profile` doesn't seem to be used
+     * - `app` doesn't seem to be used
+     *
+     * `unknown` is returned if no type is returned in the TL object.
+     */
+    get previewType() {
+        return this.raw.type || 'unknown';
+    }
+    /**
+     * Page title
+     *
+     * Usually defined by `og:site_name` meta tag or website domain
+     */
+    get siteName() {
+        return this.raw.siteName ?? null;
+    }
+    /**
+     * Page title
+     *
+     * Usually defined by `og:title` meta tag or `<title>` tag
+     */
+    get title() {
+        return this.raw.title ?? null;
+    }
+    /**
+     * Page description
+     *
+     * Usually defined by `description` or `og:description` meta tag
+     */
+    get description() {
+        return this.raw.description ?? null;
+    }
+    /**
+     * Page author
+     *
+     * The source for this is unknown, seems to be
+     * custom-made for services like Twitter.
+     *
+     * In official apps this seems to be used as a fallback for description.
+     */
+    get author() {
+        return this.raw.author ?? null;
+    }
+    /**
+     * The embed URL.
+     *
+     * Based on my research, Telegram only allows
+     * embedding pages from a server-side white-list of domains.
+     *
+     * That is, you can't just copy-paste meta tags
+     * from YouTube to your own domain and expect Telegram
+     * to return a webpage with embed.
+     *
+     * IDK why is that, maybe they are concerned about
+     * leaking users' IPs to 3rd parties or something
+     * (but why allow embedding in the first place then?)
+     *
+     * Telegram for Android does not show "play" button for
+     * webpages without embeds, and instead treats it like a simple
+     * photo (why?).
+     *
+     * TDesktop does not support embeds and seems
+     * to use {@link type} to determine them, and specifically
+     * [checks](https://github.com/telegramdesktop/tdesktop/blob/3343880ed0e5a86accc7334af54b3470e29ee686/Telegram/SourceFiles/history/view/media/history_view_web_page.cpp#L561)
+     * for `YouTube` in {@link siteName} to display YouTube icon.
+     */
+    get embedUrl() {
+        return this.raw.embedUrl ?? null;
+    }
+    /**
+     * Embed type.
+     *
+     * Now this is actually stupid.
+     * As per [official documentation](https://core.telegram.org/constructor/webPage),
+     * `embed_type` contains «MIME type of the embedded preview, (e.g., text/html or video/mp4)».
+     * But in fact every time I encountered it it contained a simple string `iframe`.
+     *
+     * I couldn't find any usage of this field in official apps either.
+     */
+    get embedType() {
+        return this.raw.embedType ?? null;
+    }
+    /**
+     * Width of the embed in pixels, 0 if not available.
+     */
+    get embedWidth() {
+        return this.raw.embedWidth || 0;
+    }
+    /**
+     * Height of the embed in pixels, 0 if not available.
+     */
+    get embedHeight() {
+        return this.raw.embedHeight || 0;
+    }
+    /**
+     * A photo inside this webpage preview.
+     *
+     * Used for most of the preview types.
+     */
+    get photo() {
+        if (this.raw.photo?._ !== 'photo') {
+            return null;
+        }
+        return new photo_js_1.Photo(this.raw.photo);
+    }
+    /**
+     * Document inside this webpage preview.
+     *
+     * Seems that this is only used for `document` previews.
+     *
+     * Can be a {@link Photo}, {@link Video},
+     * {@link Audio}, {@link Document}.
+     */
+    get document() {
+        if (this.raw.document?._ !== 'document') {
+            return null;
+        }
+        return (0, document_utils_js_1.parseDocument)(this.raw.document);
+    }
+    /**
+     * Input media TL object generated from this object,
+     * to be used inside {@link InputMediaLike} and
+     * {@link TelegramClient.sendMedia}.
+     *
+     * WebPage can't provide an input media, since some
+     * can only be auto-generated from a link. This getter
+     * is only provided to allow using `msg.media.inputMedia`
+     */
+    get inputMedia() {
+        throw new errors_js_1.MtArgumentError('WebPage cannot provide an InputMedia');
+    }
+}
+exports.WebPage = WebPage;
+(0, memoize_js_1.memoizeGetters)(WebPage, ['photo', 'document']);
+(0, index_js_1.makeInspectable)(WebPage, undefined, ['inputMedia']);
+//# sourceMappingURL=web-page.js.map

package/cjs/highlevel/types/media/web-page.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"web-page.js","sourceRoot":"","sources":["../../../../../src/highlevel/types/media/web-page.ts"],"names":[],"mappings":";;;AAEA,wDAA0D;AAC1D,mDAAsD;AACtD,uDAAuD;AAEvD,2DAAmD;AACnD,yCAAkC;AAElC;;;;;;;;;GASG;AACH,MAAa,OAAO;IAGhB,YAAqB,GAAkB;QAAlB,QAAG,GAAH,GAAG,CAAe;QAF9B,SAAI,GAAG,SAAkB,CAAA;IAEQ,CAAC;IAE3C;;OAEG;IACH,IAAI,EAAE;QACF,OAAO,IAAI,CAAC,GAAG,CAAC,EAAE,CAAA;IACtB,CAAC;IAED;;OAEG;IACH,IAAI,GAAG;QACH,OAAO,IAAI,CAAC,GAAG,CAAC,GAAG,CAAA;IACvB,CAAC;IAED;;;;OAIG;IACH,IAAI,UAAU;QACV,OAAO,IAAI,CAAC,GAAG,CAAC,UAAU,CAAA;IAC9B,CAAC;IAED;;;;;;;;;;;;;;;;;;;;;;OAsBG;IACH,IAAI,WAAW;QACX,OAAO,IAAI,CAAC,GAAG,CAAC,IAAI,IAAI,SAAS,CAAA;IACrC,CAAC;IAED;;;;OAIG;IACH,IAAI,QAAQ;QACR,OAAO,IAAI,CAAC,GAAG,CAAC,QAAQ,IAAI,IAAI,CAAA;IACpC,CAAC;IAED;;;;OAIG;IACH,IAAI,KAAK;QACL,OAAO,IAAI,CAAC,GAAG,CAAC,KAAK,IAAI,IAAI,CAAA;IACjC,CAAC;IAED;;;;OAIG;IACH,IAAI,WAAW;QACX,OAAO,IAAI,CAAC,GAAG,CAAC,WAAW,IAAI,IAAI,CAAA;IACvC,CAAC;IAED;;;;;;;OAOG;IACH,IAAI,MAAM;QACN,OAAO,IAAI,CAAC,GAAG,CAAC,MAAM,IAAI,IAAI,CAAA;IAClC,CAAC;IAED;;;;;;;;;;;;;;;;;;;;;;OAsBG;IACH,IAAI,QAAQ;QACR,OAAO,IAAI,CAAC,GAAG,CAAC,QAAQ,IAAI,IAAI,CAAA;IACpC,CAAC;IAED;;;;;;;;;OASG;IACH,IAAI,SAAS;QACT,OAAO,IAAI,CAAC,GAAG,CAAC,SAAS,IAAI,IAAI,CAAA;IACrC,CAAC;IAED;;OAEG;IACH,IAAI,UAAU;QACV,OAAO,IAAI,CAAC,GAAG,CAAC,UAAU,IAAI,CAAC,CAAA;IACnC,CAAC;IAED;;OAEG;IACH,IAAI,WAAW;QACX,OAAO,IAAI,CAAC,GAAG,CAAC,WAAW,IAAI,CAAC,CAAA;IACpC,CAAC;IAED;;;;OAIG;IACH,IAAI,KAAK;QACL,IAAI,IAAI,CAAC,GAAG,CAAC,KAAK,EAAE,CAAC,KAAK,OAAO,EAAE;YAC/B,OAAO,IAAI,CAAA;SACd;QAED,OAAO,IAAI,gBAAK,CAAC,IAAI,CAAC,GAAG,CAAC,KAAK,CAAC,CAAA;IACpC,CAAC;IAED;;;;;;;OAOG;IACH,IAAI,QAAQ;QACR,IAAI,IAAI,CAAC,GAAG,CAAC,QAAQ,EAAE,CAAC,KAAK,UAAU,EAAE;YACrC,OAAO,IAAI,CAAA;SACd;QAED,OAAO,IAAA,iCAAa,EAAC,IAAI,CAAC,GAAG,CAAC,QAAQ,CAAC,CAAA;IAC3C,CAAC;IAED;;;;;;;;OAQG;IACH,IAAI,UAAU;QACV,MAAM,IAAI,2BAAe,CAAC,sCAAsC,CAAC,CAAA;IACrE,CAAC;CACJ;AA9LD,0BA8LC;AAED,IAAA,2BAAc,EAAC,OAAO,EAAE,CAAC,OAAO,EAAE,UAAU,CAAC,CAAC,CAAA;AAC9C,IAAA,0BAAe,EAAC,OAAO,EAAE,SAAS,EAAE,CAAC,YAAY,CAAC,CAAC,CAAA","sourcesContent":["import { tl } from '@mtcute/tl'\n\nimport { MtArgumentError } from '../../../types/errors.js'\nimport { makeInspectable } from '../../utils/index.js'\nimport { memoizeGetters } from '../../utils/memoize.js'\nimport { RawDocument } from './document.js'\nimport { parseDocument } from './document-utils.js'\nimport { Photo } from './photo.js'\n\n/**\n * Web page preview.\n *\n * **Warning**: Documentation of this class also contains my\n * personal research about how Telegram\n * handles different pages and embeds. **By no means**\n * this should be considered the definitive source of truth,\n * as this is not documented officially, and only consists\n * of my own observations and experiments.\n */\nexport class WebPage {\n    readonly type = 'webpage' as const\n\n    constructor(readonly raw: tl.RawWebPage) {}\n\n    /**\n     * Unique ID of the preview\n     */\n    get id(): tl.Long {\n        return this.raw.id\n    }\n\n    /**\n     * Original page URL\n     */\n    get url(): string {\n        return this.raw.url\n    }\n\n    /**\n     * URL to be displayed to the user.\n     *\n     * Usually a normal URL with stripped protocol and garbage.\n     */\n    get displayUrl(): string {\n        return this.raw.displayUrl\n    }\n\n    /**\n     * Type of the preview, taken directly from TL object\n     *\n     * Officially documented are:\n     * `article, photo, audio, video, document, profile, app`,\n     * but also these are encountered:\n     * `telegram_user, telegram_bot, telegram_channel, telegram_megagroup, telegram_story`:\n     *\n     * - `telegram_*` ones seem to be used for `t.me` links.\n     * - `article` seems to be used for almost all custom pages with `og:*` tags\n     * - `photo`, `audio` and `video` seem to be derived from `og:type`,\n     *    and the page itself may contain a preview photo and an embed link\n     *    for the player. This may not correctly represent actual content type:\n     *    Spotify links are `audio`, but SoundCloud are `video`. YouTube links are `video`,\n     *    but tweets with video are `photo`.\n     * - `document` seem to be used for files downloadable directly from the URL,\n     *    like PDFs, audio files, videos, etc. {@link document} seem to be\n     *    present if `type` is `document`.\n     * - `profile` doesn't seem to be used\n     * - `app` doesn't seem to be used\n     *\n     * `unknown` is returned if no type is returned in the TL object.\n     */\n    get previewType(): string {\n        return this.raw.type || 'unknown'\n    }\n\n    /**\n     * Page title\n     *\n     * Usually defined by `og:site_name` meta tag or website domain\n     */\n    get siteName(): string | null {\n        return this.raw.siteName ?? null\n    }\n\n    /**\n     * Page title\n     *\n     * Usually defined by `og:title` meta tag or `<title>` tag\n     */\n    get title(): string | null {\n        return this.raw.title ?? null\n    }\n\n    /**\n     * Page description\n     *\n     * Usually defined by `description` or `og:description` meta tag\n     */\n    get description(): string | null {\n        return this.raw.description ?? null\n    }\n\n    /**\n     * Page author\n     *\n     * The source for this is unknown, seems to be\n     * custom-made for services like Twitter.\n     *\n     * In official apps this seems to be used as a fallback for description.\n     */\n    get author(): string | null {\n        return this.raw.author ?? null\n    }\n\n    /**\n     * The embed URL.\n     *\n     * Based on my research, Telegram only allows\n     * embedding pages from a server-side white-list of domains.\n     *\n     * That is, you can't just copy-paste meta tags\n     * from YouTube to your own domain and expect Telegram\n     * to return a webpage with embed.\n     *\n     * IDK why is that, maybe they are concerned about\n     * leaking users' IPs to 3rd parties or something\n     * (but why allow embedding in the first place then?)\n     *\n     * Telegram for Android does not show \"play\" button for\n     * webpages without embeds, and instead treats it like a simple\n     * photo (why?).\n     *\n     * TDesktop does not support embeds and seems\n     * to use {@link type} to determine them, and specifically\n     * [checks](https://github.com/telegramdesktop/tdesktop/blob/3343880ed0e5a86accc7334af54b3470e29ee686/Telegram/SourceFiles/history/view/media/history_view_web_page.cpp#L561)\n     * for `YouTube` in {@link siteName} to display YouTube icon.\n     */\n    get embedUrl(): string | null {\n        return this.raw.embedUrl ?? null\n    }\n\n    /**\n     * Embed type.\n     *\n     * Now this is actually stupid.\n     * As per [official documentation](https://core.telegram.org/constructor/webPage),\n     * `embed_type` contains «MIME type of the embedded preview, (e.g., text/html or video/mp4)».\n     * But in fact every time I encountered it it contained a simple string `iframe`.\n     *\n     * I couldn't find any usage of this field in official apps either.\n     */\n    get embedType(): string | null {\n        return this.raw.embedType ?? null\n    }\n\n    /**\n     * Width of the embed in pixels, 0 if not available.\n     */\n    get embedWidth(): number {\n        return this.raw.embedWidth || 0\n    }\n\n    /**\n     * Height of the embed in pixels, 0 if not available.\n     */\n    get embedHeight(): number {\n        return this.raw.embedHeight || 0\n    }\n\n    /**\n     * A photo inside this webpage preview.\n     *\n     * Used for most of the preview types.\n     */\n    get photo(): Photo | null {\n        if (this.raw.photo?._ !== 'photo') {\n            return null\n        }\n\n        return new Photo(this.raw.photo)\n    }\n\n    /**\n     * Document inside this webpage preview.\n     *\n     * Seems that this is only used for `document` previews.\n     *\n     * Can be a {@link Photo}, {@link Video},\n     * {@link Audio}, {@link Document}.\n     */\n    get document(): RawDocument | null {\n        if (this.raw.document?._ !== 'document') {\n            return null\n        }\n\n        return parseDocument(this.raw.document)\n    }\n\n    /**\n     * Input media TL object generated from this object,\n     * to be used inside {@link InputMediaLike} and\n     * {@link TelegramClient.sendMedia}.\n     *\n     * WebPage can't provide an input media, since some\n     * can only be auto-generated from a link. This getter\n     * is only provided to allow using `msg.media.inputMedia`\n     */\n    get inputMedia(): tl.TypeInputMedia {\n        throw new MtArgumentError('WebPage cannot provide an InputMedia')\n    }\n}\n\nmemoizeGetters(WebPage, ['photo', 'document'])\nmakeInspectable(WebPage, undefined, ['inputMedia'])\n"]}

package/cjs/highlevel/types/messages/dialog.d.ts

@@ -0,0 +1,108 @@
+import { tl } from '@mtcute/tl';
+import { Chat } from '../peers/chat.js';
+import { PeersIndex } from '../peers/peers-index.js';
+import { DraftMessage } from './draft-message.js';
+import { Message } from './message.js';
+/**
+ * Type used as an input for a folder in client methods
+ *
+ * You can pass folder object, id or title
+ */
+export type InputDialogFolder = string | number | tl.RawDialogFilter;
+/**
+ * A dialog.
+ *
+ * Think of it as something that is listed
+ * in Telegram's main window.
+ */
+export declare class Dialog {
+    readonly raw: tl.RawDialog;
+    readonly _peers: PeersIndex;
+    readonly _messages: Map<number, tl.TypeMessage>;
+    constructor(raw: tl.RawDialog, _peers: PeersIndex, _messages: Map<number, tl.TypeMessage>);
+    /**
+     * Parse a list of dialogs from a TL object
+     *
+     * @param client  Client instance
+     * @param dialogs  TL object
+     * @param limit  Maximum number of dialogs to parse
+     */
+    static parseTlDialogs(dialogs: tl.messages.TypeDialogs | tl.messages.TypePeerDialogs, limit?: number): Dialog[];
+    /**
+     * Find pinned dialogs from a list of dialogs
+     *
+     * @param dialogs  Dialogs list
+     * @param folder  If passed, status of pin will be checked against this folder, and not globally
+     */
+    static findPinned(dialogs: Dialog[], folder?: tl.RawDialogFilter): Dialog[];
+    /**
+     * Create a filter predicate for the given Folder.
+     * Returned predicate can be used in `Array.filter()`
+     *
+     * @param folder  Folder to filter for
+     * @param excludePinned  Whether to exclude pinned folders
+     */
+    static filterFolder(folder: tl.TypeDialogFilter, excludePinned?: boolean): (val: Dialog) => boolean;
+    /**
+     * Whether this dialog is pinned
+     */
+    get isPinned(): boolean;
+    /**
+     * Whether this chat was manually marked as unread
+     */
+    get isManuallyUnread(): boolean;
+    /**
+     * Whether this chat should be considered unread
+     * (i.e. has more than 1 unread message, or has
+     * a "manually unread" mark)
+     */
+    get isUnread(): boolean;
+    /**
+     * Whether this dialog is muted
+     */
+    get isMuted(): boolean;
+    /**
+     * Whether this dialog is archived
+     */
+    get isArchived(): boolean;
+    /**
+     * Chat that this dialog represents
+     */
+    get chat(): Chat;
+    /**
+     * The latest message sent in this chat
+     */
+    get lastMessage(): Message;
+    /**
+     * ID of the last read outgoing message in this dialog
+     */
+    get lastReadOutgoing(): number;
+    /**
+     * ID of the last read ingoing message in this dialog
+     */
+    get lastReadIngoing(): number;
+    /**
+     * ID of the last read message in this dialog
+     */
+    get lastRead(): number;
+    /**
+     * Number of unread messages
+     */
+    get unreadCount(): number;
+    /**
+     * Number of unread mentions
+     */
+    get unreadMentionsCount(): number;
+    /**
+     * Number of unread reactions
+     */
+    get unreadReactionsCount(): number;
+    /**
+     * Draft message in this dialog
+     */
+    get draftMessage(): DraftMessage | null;
+    /**
+     * TTL period of all messages in this dialog
+     */
+    get ttlPeriod(): number | null;
+}