>>106174152>what is the proper way of handling content, and not really just on Telegram,You should build content handler (content file pipeline convert/modify/etc., models, events, storage) + publisher APIs and like I said earlier: assign types/categories to your content e.g. image with caption, text, voice
>How should it be handled in the channels?Treat each social media as an implementation/plug-in of the content publisher API and send events to those implementations.
>I want to edit the content by deleting the picture. How should it be handled in the channels?This is a good example. First, the content type is "image with caption" which is then converted to "text".
Send the change change_type event to the publishers with the id and new content. The telegram publisher impl could then complain that you can replace, but not remove the file. You can then have the impl provide solutions e.g. "use blank image", "delete old & publish new msg"
By the way, you can do whatever you want in the publisher impls that the service allows. e.g. the telegram publisher impl could handle "image with caption" content by sending two messages: an image, and a text reply => then you can delete the image without the post or replace the image with something generic.
>Or is there some other way to handle all this?There are just several hundred ways of doing this. It all depends on you, your content, and your audience. For example, it's more socially acceptable to publish errata than go back and edit in-place in a lot of fields.
Since you plan on supporting multiple social media, find the common denominator of functionality and build on that.