Tdesktop: Able to Edit Channel Messages at any given time.

[RaudelJr]

Hi,

I was wondering if the ability to be able to edit Channel Messages even after some time has passed can be enabled.

I have Entries that I would like to Update with new information where not the entire entry is outdated, only a line or two.

Given that it is a Channel owned by an administrator, I don't see why the Administrator can't edit it at will.

The Channel member can be notified of the Edited message as it gets edited.

Just a thought.

Thanks

Raudel

[john-preston]

@RaudelJr The edit time limit is a server side restriction, sorry. There is nothing I can do for that.

[stek29]

What about posting without notification and removing old post?

[tdesktop-closer]

Hey there!

We're automatically closing this issue since there was no activity in this issue since 366 days ago. We therefore assume that the user has lost interest or resolved the problem on their own. Closed issues that remain inactive for a long period may get automatically locked.

Don't worry though; if this is in error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

_{(Please note that this is an automated comment.)}

[amyodov]

If this is a server side restriction - should not it be controllable for channels/groups you own, and should not it be lifted, or lifted upon your settings of the channel?

[stek29]

There are various reasons why the limit is global and non-configurable:

• Consistency -- Users would be confused if they can edit 2day old message in one chat and can't in other.
• Optimization -- I don't know if it applies to telegram, but knowing that messages can't be edited after some time would allow to make some optimizations on how you store messages.

[amyodov]

Then the question is why it is possible to edit the groups forever (where there are many users, and the message ownership is distributed) but not the channels (where the messages are owned by the channel author/s), rather than vice versa. Not only it violates the consistency, it is a little bit... against the common sense, I truly expected being able to edit the channels in any way, it is a form of controlled media...
And as for optimization – it is claimed that the message editing shares the same backend/architecture for groups and for channels, so it would be reasonable (again, for consistency) to have the messages editable, without any implications on the message storage.

[RememberTheAir]

@amyodov the 2 days limit applies to every kind of chat. The only users who can edit messages without any kind of time trestriction are supergroups administrators with the "pin messages" permission. That's because they might need to edit an old pinned message that has been sent more than 2 days ago without having to send and pin a new one. Yes this might be a bit inconsistent, but the only users that will notice that are those who administrate a supergroup, so you would assume they have a little more experience with the app

About the limit itself, we can argue whether it makes sense or not to apply such a limit, or if 2 days are too short. But that's something that depends on the API

[LocutusVonBorg-GG]

Will this issue be changed? This is very annoying, that you can update old "Pinned"-Messages, but not old channel-messages...

[zimirrr]

I also would like to edit old messages in my own private group. For example if I use my group as my notebook

[RememberTheAir]

@zimirrr you should use your saved messages for that. There's no time limit for edits, there

[zimirrr]

@zimirrr you should use your saved messages for that. There's no time limit for edits, there

I am using saved messages, but this private groups are for my other projects

[ruv]

In a super-group admins can edit the past messages in any time. And you can convert your private group into a private super-group.

[amyodov]

The original issue covers the channels (rather than groups) though.
And by the way, why the issue is still auto-closed by tdesktop-closer and not reopened afterwards, even though, according to the comments, it seems rather user confusing and counter-intuitive, hence pretty much legit?

[RememberTheAir]

@amyodov this was closed as an API issue (autoclosed by the bot first, and then labeled as API issue). Telegram Desktop can't let you edit a message at any given time if the server rejects your request

[amyodov]

@RememberTheAir , so, fixing the server-side of Telegram will be a part of resolving the issue in general, rather than excuse to close it, won’t it? That’s why this issue is here and the discussion is going on – to get it fixed, and to fix all intermediate layers required for that (if needed).

[RememberTheAir]

@amyodov this is just the wrong place where to discuss this, this is why it has been closed here. This repository is only for discussion about what's in the capabilities of tdesktop. Telegram Desktop's developer probably doesn't take part to the discussion about how platform-wise features should be implemented. You can bug Telegram on Twitter or suggest that to the in-app support

[amyodov]

Well, Telegram Desktop is the official desktop client for Telegram, moreover a primary one on multiple platforms. So any issues of internal communications between various teammates (like, between GUI developers and backend developers) of the same Telegram project should not bother any end-user of Telegram.

[RememberTheAir]

This issue tracker is just for issues about the desktop app, not for platform-wise requests. The specific issue about the 48 hours edit limit in channels is a platform-wise request and tdesktop can't do nothing about it until the API doesn't support that. This is why it's offtopic here - the fact that tdesktop is an official app doesn't change the fact that this issue tracker is only for client-side discussions, platform-wise requests are out of the scope of the developer's capabilities. These things should be suggested to the in-app support or to the Twitter account

[RememberTheAir]

By the way, since a few days ago (probably), the API started to let users edit channel messages with no time limit, so the limit is probably going to be lifted on all clients too (I guess at the moment it's hardcoded or passed to the client as a server configuration property)

Though, I'm just assuming they removed the limit from the API because all the clients are going to be updated to behave accordingly, but this is just speculation by me

[amyodov]

Well, seems this issue finally is getting fixed then, thanks for insistence of everyone involved (and regardless of intra-Telegram-project management/communication difficulties).