You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Today in software being horrible: NetworkManager's l2tp-ipsec breaks if you have any other IPsec configs. Not active (of course that is completely broken), just configured at all. Why? Because it makes its secrets file root-only, which charon can't read after dropping privs.
Why does it matter if you have any other configs? Because charon tries to reload secrets after dropping privs. If it fails, it still works. If it succeeds in reading *some* secrets though (like if you make your secrets file owned by ipsec), then it drops the NM secrets.
The fix is chown root:root /etc/ipsec.secrets; chmod 600 /etc/ipsec.secrets and just let charon keep failing at re-reading *all* secrets, not just NetworkManager's, so it doesn't drop those keys on the floor. I'm sure this breaks some other use case though ¯\_(ツ)_/¯
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
