Add Mastodon bridge

[selfhoster1312]

New attempt at fixing linter errors

The context is passed by function argument as recommended by golang.

Deferred error checking is applied, simply printing a warning in case of error.

And errors are typed.

[selfhoster1312]

Still a few errors silently discarded that should be logged. Don't merge yet

[lil5]

https://hemaks.org/posts/why-your-obsession-with-code-linting-is-excessive/

Consider these questions when evaluating your linting setup:

• Does this rule prevent actual bugs? If not, consider removing it.
• Would a new team member understand why this rule exists? If you can’t explain it in one sentence, it might be too complex.
• Are we spending more time configuring tools than solving problems? If yes, you’ve gone too far.
• Do our linting rules reflect our team’s actual coding standards? Rules that everyone ignores or works around are worse than no rules. Remember, the best code is code that works, is maintainable, and can be understood by your teammates. If your linting setup supports these goals, great. If it becomes an obstacle to them, it’s time to reassess.

[selfhoster1312]

Added some helper tweaks in #20. Once it is merged this PR can be rebased and reviewed properly.

[poVoq]

@lil5 could you please test if this is still working as expected? Thanks.