Forwarded from KeralaGram [Official]®
Telegram auto enabled Forward hidden privacy options for Deleted Account
Now you can't find user of a Deleted Account from the forwarded message
Before from a forwarded message of Deleted account it was possible to find user id and there was a possibility to find the user by opening the profile if we had a chat with the same user.
#privacy #forward #Message
ℹ️ @KeralagramChannel
Now you can't find user of a Deleted Account from the forwarded message
Before from a forwarded message of Deleted account it was possible to find user id and there was a possibility to find the user by opening the profile if we had a chat with the same user.
#privacy #forward #Message
ℹ️ @KeralagramChannel
Forwarded from KeralaGram [Official]®
Privacy Exceptions
A consolidated page where you can change all privacy settings for a specific user or group
#Telegramx #tgx #android #beta #privacy
ℹ @KeralaGramChannel
A consolidated page where you can change all privacy settings for a specific user or group
#Telegramx #tgx #android #beta #privacy
ℹ @KeralaGramChannel
Forwarded from BotNews
Bot API 6.2
Custom Emoji
• Bots can identify custom emoji sent by Telegram Premium users via the new type "custom_emoji" and field custom_emoji_id added to the MessageEntity class.
• Added the method getCustomEmojiStickers to obtain information about specific emoji.
• Added the fields type and custom_emoji_id to the Sticker class.
• Added sticker_type as a new field for StickerSet and as a new parameter for createNewStickerSet.
Web Apps
• Implemented support for native dialog windows including alerts, popups with custom buttons and confirmation messages.
• A confirmation dialog can now be shown when users close the web app. The dialog can be toggled via the enableClosingConfirmation and disableClosingConfirmation functions.
• Added the field is_premium to the WebAppUser class — the standard User class already included this field, see version 6.1.
• Added has_restricted_voice_and_video_messages to the Chat class to support the new premium setting.
• And more, see the full changelog for details:
https://core.telegram.org/bots/api-changelog#august-12-2022
Note: The documentation for createNewStickerSet and StickerSet no longer mentions the contains_masks parameter and field respectively. In both instances, contains_masks will continue to work for backward compatibility but developers should use sticker_type instead.
Custom Emoji
• Bots can identify custom emoji sent by Telegram Premium users via the new type "custom_emoji" and field custom_emoji_id added to the MessageEntity class.
• Added the method getCustomEmojiStickers to obtain information about specific emoji.
• Added the fields type and custom_emoji_id to the Sticker class.
• Added sticker_type as a new field for StickerSet and as a new parameter for createNewStickerSet.
Web Apps
• Implemented support for native dialog windows including alerts, popups with custom buttons and confirmation messages.
• A confirmation dialog can now be shown when users close the web app. The dialog can be toggled via the enableClosingConfirmation and disableClosingConfirmation functions.
• Added the field is_premium to the WebAppUser class — the standard User class already included this field, see version 6.1.
• Added has_restricted_voice_and_video_messages to the Chat class to support the new premium setting.
• And more, see the full changelog for details:
https://core.telegram.org/bots/api-changelog#august-12-2022
Note: The documentation for createNewStickerSet and StickerSet no longer mentions the contains_masks parameter and field respectively. In both instances, contains_masks will continue to work for backward compatibility but developers should use sticker_type instead.
Forwarded from BotNews
Bot API 6.2
Custom Emoji
• Bots can identify custom emoji sent by Telegram Premium users via the new type "custom_emoji" and field custom_emoji_id added to the MessageEntity class.
• Added the method getCustomEmojiStickers to obtain information about specific emoji.
• Added the fields type and custom_emoji_id to the Sticker class.
• Added sticker_type as a new field for StickerSet and as a new parameter for createNewStickerSet.
Web Apps
• Implemented support for native dialog windows including alerts, popups with custom buttons and confirmation messages.
• A confirmation dialog can now be shown when users close the web app. The dialog can be toggled via the enableClosingConfirmation and disableClosingConfirmation functions.
• Added the field is_premium to the WebAppUser class — the standard User class already included this field, see version 6.1.
• Added has_restricted_voice_and_video_messages to the Chat class to support the new premium setting.
• And more, see the full changelog for details:
https://core.telegram.org/bots/api-changelog#august-12-2022
Note: The documentation for createNewStickerSet and StickerSet no longer mentions the contains_masks parameter and field respectively. In both instances, contains_masks will continue to work for backward compatibility but developers should use sticker_type instead.
Custom Emoji
• Bots can identify custom emoji sent by Telegram Premium users via the new type "custom_emoji" and field custom_emoji_id added to the MessageEntity class.
• Added the method getCustomEmojiStickers to obtain information about specific emoji.
• Added the fields type and custom_emoji_id to the Sticker class.
• Added sticker_type as a new field for StickerSet and as a new parameter for createNewStickerSet.
Web Apps
• Implemented support for native dialog windows including alerts, popups with custom buttons and confirmation messages.
• A confirmation dialog can now be shown when users close the web app. The dialog can be toggled via the enableClosingConfirmation and disableClosingConfirmation functions.
• Added the field is_premium to the WebAppUser class — the standard User class already included this field, see version 6.1.
• Added has_restricted_voice_and_video_messages to the Chat class to support the new premium setting.
• And more, see the full changelog for details:
https://core.telegram.org/bots/api-changelog#august-12-2022
Note: The documentation for createNewStickerSet and StickerSet no longer mentions the contains_masks parameter and field respectively. In both instances, contains_masks will continue to work for backward compatibility but developers should use sticker_type instead.
Forwarded from Telegram Info English (DbSergey)
Non-Obvious Privacy Aspects When Sending Star Reactions
In August 2024, Telegram introduced the ability for users to send star reactions to channel posts, and in February 2025 — the ability to send such reactions not only on their own behalf, but also on behalf of any of their public channels.
The privacy settings for both types of reactions are not obvious. If you expect that no one will know your name, keep in mind the following:
1. When sending a paid reaction on your own behalf, the application allows you to disable the "Show me in Top Senders" option. If the user disables it, then neither their name nor their profile picture will be displayed to other channel subscribers, even if they are among the three donors who sent the most stars to the post.
However, even in this case, the owner of the channel to which the stars were sent will see the sender's name in the "Monetization" tab in the channel settings.
2. When sending a paid reaction, the application allows the user to select one of the public channels that they own. In this case, the list of the top 3 senders will not display the name of the sender, but the name of the channel that they chose.
However, the owner of the channel to which the stars were sent will see the sender's name in the "Monetization" tab in the channel settings. By comparing it with the list of top 3 senders of stars to a specific post, the channel owner can find out who exactly owns the channel on whose behalf the stars were sent.
Be careful: Telegram applications do not warn users sending star reactions about these nuances.
#reactions #stars #privacy
In August 2024, Telegram introduced the ability for users to send star reactions to channel posts, and in February 2025 — the ability to send such reactions not only on their own behalf, but also on behalf of any of their public channels.
The privacy settings for both types of reactions are not obvious. If you expect that no one will know your name, keep in mind the following:
1. When sending a paid reaction on your own behalf, the application allows you to disable the "Show me in Top Senders" option. If the user disables it, then neither their name nor their profile picture will be displayed to other channel subscribers, even if they are among the three donors who sent the most stars to the post.
However, even in this case, the owner of the channel to which the stars were sent will see the sender's name in the "Monetization" tab in the channel settings.
2. When sending a paid reaction, the application allows the user to select one of the public channels that they own. In this case, the list of the top 3 senders will not display the name of the sender, but the name of the channel that they chose.
However, the owner of the channel to which the stars were sent will see the sender's name in the "Monetization" tab in the channel settings. By comparing it with the list of top 3 senders of stars to a specific post, the channel owner can find out who exactly owns the channel on whose behalf the stars were sent.
Be careful: Telegram applications do not warn users sending star reactions about these nuances.
#reactions #stars #privacy