Fix incorrectly formatted links in Mastodon notifications via Zapier bot integration.

[PieterCK]

Bug Overview

Sometimes the Mastodon notification over at #mastodon channel sends messages containing links that have extra whitespaces in it thus breaking the link. The Mastodon integration is set up via our Zapier integration bot.

Instances of notification with buggy links from the Mastodon integration:

    > Notes: there are plenty more examples over at the Mastodon channel, please check them out for more references

Leads

Our Zapier webhook bot is only forwarding messages from Zapier. In the backend, we didn't do any formatting at all for any incoming messages to the Zapier bot. Over at the front end, I couldn't find features or quirks that might incorrectly format links. This leads me to think that it might be a problem from upstream over at Zapier or Mastodon.

If we go to the original post from these notifications with broken links, we can see that the links in the actual Mastodon post are displayed without the "https:" part and if it's too long, the links are also truncated. Over at our side, these same links are added the "https:" part and the truncated section is added back. However, these are white spaces between these added parts that breaks the link. This is a consistent pattern across the messages with broken links.

Further investigation and reproducing the bug might be warranted.

Original Mastodon posts of the notifications above:

    > Note: the links to the original Mastodon post are also in the notification sent by the Zapier bot

**Zulip Server and web app version:** - [ ] Zulip Cloud (`*.zulipchat.com`) - [ ] Zulip Server 8.0+ - [ ] Zulip Server 7.0+ - [ ] Zulip Server 6.0+ - [ ] Zulip Server 5.0 or older - [x] Other or not sure

[PieterCK]

@zulipbot add "area: integrations"

[zulipbot]

Hello @zulip/server-integrations members, this issue was labeled with the "area: integrations" label, so you may want to check it out!

[Faisal-imtiyaz123]

@alya can I work?

[alya]

@Faisal-imtiyaz123 Sure! Please post a comment describing your proposed approach when you're ready. You can claim the issue after you have a rough plan for how to address it. Thanks!

[gaurav21687]

Hey @alya , I have completely understood the issue and am interested to work on the issue. I am a beginner , so can you please guide me how should i approach the problem.

[gaurav21687]

@zulipbot claim

[zulipbot]

Welcome to Zulip, @gaurav21687! We just sent you an invite to collaborate on this repository at https://github.com/zulip/zulip/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!

Here's some tips to get you off to a good start:

• Join me on the Zulip developers' server, to get help, chat about this issue, and meet the other developers.
• Unwatch this repository, so that you don't get 100 emails a day.

As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.

See you on the other side (that is, the pull request side)!

[alya]

@gaurav21687 Please refer to our guide to asking great questions for some tips on how to get help figuring out how to approach an issue. It's very difficult to answer general questions along the lines of, "how do I get started?" Thanks!

[Faisal-imtiyaz123]

@zulipbot claim

[zulipbot]

Hello @Faisal-imtiyaz123, it looks like you've currently claimed 1 issue in this repository. We encourage new contributors to focus their efforts on at most 1 issue at a time, so please complete your work on your other claimed issues before trying to claim this issue again.

We look forward to your valuable contributions!

[OmarAmeen01]

@zulipbot claim

[devyk100]

@zulipbot claim

[zulipbot]

Welcome to Zulip, @devyk100! We just sent you an invite to collaborate on this repository at https://github.com/zulip/zulip/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!

Here's some tips to get you off to a good start:

• Join me on the Zulip developers' server, to get help, chat about this issue, and meet the other developers.
• Unwatch this repository, so that you don't get 100 emails a day.

As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.

See you on the other side (that is, the pull request side)!