You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
馃挕 The Idea
I came up here to suggest adding a property or anything else so we can handle platform native options separate from the Apprise, I saw some issues requesting support for some of telegram features and you should do development to wrap any new feature to be consistent & compatible with Apprise ecosystem. I guess this can be a trouble for you because of efforts for development & conventions are pain like in #880, Also for users it's not always easy to switch or wait for new feature support. I my self hope support for message entities like buttons to be supported
馃敤 Breaking Feature
The text was updated successfully, but these errors were encountered:
Can you give me an example outside of #880 which wasn't too trivial to fix in #883? I don't mind requests coming in and adding them on a per-service needs.
Some service are more popular then others; so to implement some global strategy and go over all of them to see which one requires a modification might be a bit more work then it's worth?
馃挕 The Idea
I came up here to suggest adding a property or anything else so we can handle platform native options separate from the Apprise, I saw some issues requesting support for some of telegram features and you should do development to wrap any new feature to be consistent & compatible with Apprise ecosystem. I guess this can be a trouble for you because of efforts for development & conventions are pain like in #880, Also for users it's not always easy to switch or wait for new feature support. I my self hope support for message entities like buttons to be supported
馃敤 Breaking Feature
The text was updated successfully, but these errors were encountered: