Raw
Raw.GlobalPrivacySettings

Raw.GlobalPrivacySettings

Global privacy settings

globalPrivacySettings#734c4ccb flags:# archive_and_mute_new_noncontact_peers:flags.0?true keep_archived_unmuted:flags.1?true keep_archived_folders:flags.2?true hide_read_marks:flags.3?true new_noncontact_peers_require_premium:flags.4?true = GlobalPrivacySettings;
export namespace Raw {
  export class GlobalPrivacySettings {
    constructor(params: {
      archiveAndMuteNewNoncontactPeers?: boolean;
      keepArchivedUnmuted?: boolean;
      keepArchivedFolders?: boolean;
      hideReadMarks?: boolean;
      newNoncontactPeersRequirePremium?: boolean;
    }) {}
  }
}
🚫

This is a types constructor, you can’t use it as method when call invoke.

Layer: 185
Constructor ID: 0x734c4ccb

Property

  • archiveAndMuteNewNoncontactPeers : boolean or undefined

    Whether to archive and mute new chats from non-contacts

  • keepArchivedUnmuted : boolean or undefined

    Whether unmuted chats will be kept in the archive chat list when they get a new message.

  • keepArchivedFolders : boolean or undefined

    Whether unmuted chats that are always included or pinned in a folder, will be kept in the archive chat list when they get a new message. ignored if keepArchivedUnmuted is set.

  • hideReadMarks : boolean or undefined

    If this flag is set, the inputprivacykeystatustimestamp key will also apply to the ability to use messages.getoutboxreaddate on messages sent to us. meaning, users that cannot see our exact last online date due to the current value of the inputprivacykeystatustimestamp key will receive a 403 userPrivacyRestricted error when invoking messages.getoutboxreaddate to fetch the exact read date of a message they sent to us. the userfull.readDatesPrivate flag will be set for users that have this flag enabled.

  • newNoncontactPeersRequirePremium : boolean or undefined

    If set, only users that have a premium account, are in our contact list, or already have a private chat with us can write to us; a 403 privacyPremiumRequired error will be emitted otherwise. the userfull.contactRequirePremium flag will be set for users that have this flag enabled. to check whether we can write to a user with this flag enabled, if we haven’t yet cached all the required information (for example we don’t have the userfull or history of all users while displaying the chat list in the sharing ui) the users.getispremiumrequiredtocontact method may be invoked, passing the list of users currently visible in the ui, returning a list of booleans that directly specify whether we can or cannot write to each user. premium users only, non-premium users will receive a premiumAccountRequired error when trying to enable this flag.

Raw.GetFutureSaltsRaw.GroupCall