mirror of
https://github.com/caronc/apprise.git
synced 2025-03-03 09:31:31 +01:00
Updated Troubleshooting (markdown)
parent
f2e470c667
commit
6fd2c48b61
@ -27,7 +27,7 @@ The possible **overflow=** options are defined as:
|
||||
| ----------- | ----------- |
|
||||
| **split** | This will break the message body (and title if required) into as many smaller chunks (based on the confines of the service itself) and send out multiple messages in order to deliver everything.<br/><br/>For example, Twitter restricts public tweets to 280 characters. If your Apprise/Twitter URL was updated to look like `twitter://<auth data>/?overflow=split`, A message of say 1000 characters would be broken (and sent) via 4 smaller messages (280 + 280 + 280 + 160).
|
||||
| **truncate** | This just ensures that regardless of how much content you're sending to an remote notification service, all of it's contents will be truncated to fit within a single message. This means that any data that exceeds the maximum message side will just be removed for the message itself.
|
||||
| **upstream** | This is the default configuration.
|
||||
| **upstream** | Let the upstream notification service handle all of the data passed to it. Apprise will not mangle/change it's content in any way.<br/>**Note**: This is the default configuration option used when the `overflow=` directive is not set.
|
||||
|
||||
Please note that the **overflow=** option isn't a perfect solution:
|
||||
* It can fail for services like Telegram which can take content in the format of both _HTML_ and _Markdown_. If you're using _HTML_, then there is a very strong possibility that both the upstream and/or truncate option could cut your message in the middle of an un-closed HTML tag. Telegram doesn't fair to well to this and in the past (at the time of writing this wiki entry) would error and not display the data.
|
||||
|
Loading…
Reference in New Issue
Block a user