I maintain several twitter search monitors that allows keeping several peolple updated with mentions of keywords.
For that, I use the excellent perl module Net::Twitter::Lite::WithAPIv1_1 from many months, without any problem.
However, since yesterday it was obtaining only a “403: Forbidden” code from the Twitter API. I searched through the web and only found a report several days ago with the same problem (still unresolved).
But my good friend @chidalgo found the solution: since yesterday, api.twitter.com is restricting access only with TLS.
Luckly, the Net::Twitter::Lite::WithAPIv1_1 only requires a “ssl => 1” option to turn on TLS traffic, and voila! The search monitor is back.
Next post: DMARC y mailman
Previous post: RFC6950: Architectural Considerations on Application Features in the DNS