FEATURE: Use Twitter for Outbound Posting to raise awareness

[CodeBunTes]

I floated this idea out briefly at Pre-Spark Hackathon. While the ability to read from Twitter was removed in the updated 'Free' API, they retained the ability to post outbound on Free tier. This still made it impossible to listen to the Tweets people make and was why we had to move all things over to Mastodon.

However as a write-only ability still exists in the new free API, there could still be an opportunity to still exploit this a little differently to help draw more attention to the good things people are doing and sharing in the community for those still over on the Twitter side. When it is detected that a new post has been made to Mastodon, the h5yr Twitter account could do a fresh post out to Twitter too mentioning the fact that someone has shared thanks with someone else in order to help raise awareness. We wouldn't be able to link directly to the usernames (so the @ would be dropped) as we couldn't be sure the usernames would be the same across both platforms. And probably shouldn't link directly to the toot, as though they did back down on 'officially' banning people posting links to Mastodon, I'd be willing to bet Elon has probably still set up Twitter to be sensitive over a lot of links to a rival platform. But it should be safe to link back to the overall website in general terms.

So for example if I'd posted 'Hey a big #h5yr to @OwainWilliams for shipping out my new shirt' over on Mastodon, Mastodon could do its normal boosting and bring it through to the website, while Twitter could have something vaguer posted to it from the h5yr Twitter account like 'CodeBunTes has just given a #h5yr to OwainWilliams. Find out more on h5yr.com'.

As there are no triggers for this on the Twitter side, the hook for this would need to happen wherever the Mastodon bot currently sits listening for new toots. At the moment I believe this is a separate application sitting on a mini server somewhere rather than being directly in the h5yr codebase. But it could be either updated here, or the whole Mastodon bot process possibly moved to the website code via Umbraco scheduled tasks or Hangfire.