#2249 Add Mastodon in Blog Articles

Weltraumschaf · Weltraumschaf · commit d3ce9f2ec980 · 2024-02-13T11:05:35.000+01:00
But left the old Twitter link for correctnes.

Signed-off-by: Sven Strittmatter &lt;sven.strittmatter@iteratec.com&gt;
diff --git a/documentation/blog/2020-10-15-sundown-and-eol-of-version-1.md b/documentation/blog/2020-10-15-sundown-and-eol-of-version-1.md
@@ -48,7 +48,7 @@ It may be possible to migrate the data collected by version 1 in Elastic. But at
 
 ## Please Sorry 🥺
 
-So you may face a major fuckup now. We understand that such a move is almost always quite a bit annoying. That's why we ask you for sorry and hope we won't lose you as a *secureCodeBox* user. If you need help moving to *secureCodeBox* version 2 don't hesitate to ask us for help! You can reach us at [Twitter](https://www.twitter.com/secureCodeBox), [OWASP Slack](https://owasp.org/slack/invite) (Channel `#project-securecodebox`), E-Mail (securecodebox [at] iteratec [dot] com) or just file an issue at GitHub.
+So you may face a major fuckup now. We understand that such a move is almost always quite a bit annoying. That's why we ask you for sorry and hope we won't lose you as a *secureCodeBox* user. If you need help moving to *secureCodeBox* version 2 don't hesitate to ask us for help! You can reach us at ~~[Twitter](https://www.twitter.com/secureCodeBox)~~[Mastodon](https://infosec.exchange/@secureCodeBox), [OWASP Slack](https://owasp.org/slack/invite) (Channel `#project-securecodebox`), E-Mail (securecodebox [at] iteratec [dot] com) or just file an issue at GitHub.
 
 Finally to cheer you up a little cute kitten:
 
diff --git a/documentation/blog/2020-10-16-release-of-securecodebox-version-2.md b/documentation/blog/2020-10-16-release-of-securecodebox-version-2.md
@@ -32,7 +32,7 @@ Please note that scanning random hosts may be illegal. Please scan only hosts yo
 
 :::
 
-If you miss something in our documentation or you think it is unclear or wrong described. Please feel free to file an [issue](https://github.com/secureCodeBox/documentation/issues). If you need any help with your brand new _secureCodeBox_ don't hesitate to contact us via [Twitter](https://www.twitter.com/secureCodeBox), [OWASP Slack](https://owasp.org/slack/invite) (Channel `#project-securecodebox`), E-Mail (securecodebox [at] iteratec [dot] com) or just file an [issue](https://github.com/secureCodeBox/secureCodeBox) at GitHub.
+If you miss something in our documentation or you think it is unclear or wrong described. Please feel free to file an [issue](https://github.com/secureCodeBox/documentation/issues). If you need any help with your brand new _secureCodeBox_ don't hesitate to contact us via ~~[Twitter](https://www.twitter.com/secureCodeBox)~~[Mastodon](https://infosec.exchange/@secureCodeBox), [OWASP Slack](https://owasp.org/slack/invite) (Channel `#project-securecodebox`), E-Mail (securecodebox [at] iteratec [dot] com) or just file an [issue](https://github.com/secureCodeBox/secureCodeBox) at GitHub.
 
 ## What's New in secureCodeBox v2
 
