This morning I woke up to the news that Twitter had flagged all Visual Signals urls until further noticed. If anyone tries posting a link from the site, you’ll be presented with this lovely message:
I read over the Help Center information and I’ve come to the conclusion when we added the Newsletter signup, because we didn’t have SSL, someone could commit phishing attempts on the behalf of the website. I’ve never owned an SSL certificate before and I never thought I’d need one but here we are. So I purchased an SSL certificate and now any time you use the site, it’ll always begin with an https. This means all connection between the website and your computer are encrypted. This is great for privacy and security, so all in all, whatever happens with Twitter, the website is in better shape.
So where do we stand? I contacted Twitter via their Authenticity on Twitter feature to let them know this is a mistake but it would be great if you can also do the same.
Twitter did get back to me with an automated message, but it doesn’t give me hope:
Thanks for your report.
In order to make Twitter more secure, we have automations in place that could impact your ability to Tweet certain links. If you’re having issues Tweeting a link, our team will review your request and take appropriate action on the reported URL. You can find more information on this topic in this help center article: https://support.twitter.com/articles/90491
Though we cannot respond to individual reports, the information provided helps us make Twitter better for everyone.
If you’ve experienced this before and think the SSL isn’t enough, please let me know on Discord. I’m desperate to not have my only stream of interacting with the scene away from the project.
Thanks — KITE0080