fix(#210): Reduce chances of XSS injections

[abhiabhi94]

• on the content field.

fixes #210

[Radi85]

Great work!
@abhiabhi94 Could you please rebase your PR?

[abhiabhi94]

Hey @Radi85, this status reporting in taking too long on travis-ci. It maybe due to an issue at either end. Do you consider switching to GitHub actions? A lot of open-source repositories have migrated to it, and I too have had satisfactory experience.

Although, It maybe a backroom strategy by Microsoft to have this migration.

[Radi85]

Hey @Radi85, this status reporting in taking too long on travis-ci. It maybe due to an issue at either end. Do you consider switching to GitHub actions? A lot of open-source repositories have migrated to it, and I too have had satisfactory experience.

I have no never used actions but I would not mind to migrate since we are facing issues with Travis. I will have a look at it as soon as I have a time.

Although, It maybe a backroom strategy by Microsoft to have this migration.

Microsoft 😆

[abhiabhi94]

I have no never used actions but I would not mind to migrate since we are facing issues with Travis. I will have a look at it as soon as I have a time.

I will try to make a patch for this one soon.

[abhiabhi94]

One more thing, you'll have to add the password token to the secrets for automated release to PyPI with actions. I would suggest using a manual release as there have been instances in the past when secrets have been leaked(also I don't like microsoft).

I can handle the release process, if you don't have the time. In case, you have any other suggestions, they are welcome.