Recommendations for a free notification service with markdown, long messages and code snippets (special characters)

[87435]

I was curious to hear recommendations for a notification service that would work well with code Markdown and code snippets.
I have used Telegram in the past but had a lot of notifications not going through because of their rules that require manually escaping characters in markdown messages. That is not convenient when receiving code that might include lots of special characters.
My typical notification will include code snippets and ideally I would like to be able to have proper markdown for:

• hyperlinks
• formatting (bold, italic)
• code blocks ("raw" format + monospace?)
  Discord handles it well but has a limit of 2000 characters which is not always enough for me.

[caronc]

Are you experiencing issues with the escaping Apprise is doing for Telegram?

[caronc]

Just for clarification, it sounds like it's working as intended.

By default, Apprise passes everything it gets unmangled if it doesn't know what the source format is. The individual services know what the upstream service is expecting, (html, markdown, or text) but doesn't do too much extra tasks knowing this. There are a few rare circumstances where this isn't the case.

Now .. once you set the body_format, you've given Apprise enough information to ignore the unmangled state. It now knows what you're feeding it (source content), and it already knew what the upstream service was expecting, so conversions, and escaping kicks in if input format != output format. In this case, Telegram by default trys to output html

Where the ?format= in the URL comes in, is now your telling Apprise to use the services output renderer of markdown instead of HTML. This causes you to actually pass this through Telegrams markdown upstream settings (vs default html in this case).

Summary: body_format controls the input and can not be controlled by the url string. While ?format= on the URL controls the output handling prior to being passed to the service. This is doable applicable for services that support more then one (but Telegram fits this bill).

I guess after writing this novel response (😉 sorry about that), it could be argued that when you provided the body_format=markdown, it's conversions to HTML (default output format) prior to being sent to the Telegram service should have been valid; i can look into this.

If the conversion exceeded 2000 character and you leverage overflow=split, that can potentially bust up the html with non closed tags causing it to fail as well.

Thoughts?

[87435]

understood, I think I got it for the most part.
As I said before, Discord's notifications seem to send out 100% of the time and the format is correct. Is it because its default output is markdown?

[87435]

So to go back to my original question - would you have a recommendation for me by any chance? I'm sure you've tested a bunch of services so your opinion is valuable.

[caronc]

For markdown, I mean Apprise can handle the conversion, so passing markdown into even email and setting the bodyformat as such will format nicely, discord too.

Personally i like Telegram too, it seems you're just hitting size limits, but the split option as discussed should take care of that for you.

As per snippets, I'm at my day job now, but perhaps this weekend i could put together something for you.

What specifically is the main problem you're trying to solve? What will you be generally be publishing? What is your audience?

[87435]

Audience most of the time is only me - receiving alerts for various things like errors in a script, notification about events (a website change, code change, etc) or other various messages. They can be quite long especially if they contain code blocks. I guess my main problem is reliability and good handling of the format. I need the message to go through as often as possible (which is where I've been having issues with silent failures with Telegram) and be easily readable whether on desktop or mobile (splitting is not ideal).