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
i still love having delayed db slave(s) as recovery mechanisms. not only covers sysadmin errors but also user/moderator incidents where soft delete might not be a thing. also in a similar way i colour code shell tabs according to their danger level
We actually have a standby slave now (was set up after the incident too), but it's not delayed.
i probably rely on it more than i should (like multiple times a month). gdpr delete request accidentally applied by support team to wrong user? no worries ssh delayed 'mysqldump -w "user_id=1234" --insert-ignore -ntfq --skip-add-locks --skip-disable-keys osu' | ssh master mysql
of course have to first catch it up to just before the mistake happened if you want to avoid data loss, but indispensable as a tool :D
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
emoji into the zsh prompt of prod hosts.
The only data lost was a user that had registered themselves in the time between the backup and the accident. We have structured logs which include everything but the password, so I manually re-created them.