4 ms·

Probably that they rolled back the change when it became obvious it was bad.

• thrdbndndn 3y ago
  The article is pretty fresh ("This entry was posted on Wednesday 10th of April 2024 10:28 AM", and the author is from the US. Even if he's on East Coast, it would only be half an hour ago) though. Unless Twitter just fixed it within 1 hour, I think the author should mention it has been fixed (edit: or that it was limited to certain platform [iOS?], since it's not reproducible on web at least.)
  • krebsonsecurity 3y ago
    Thanks. I did update the story to reflect the apparent fix. I'm still trying to verify if this behavior remains in some form.
  • rsynnott 3y ago
    Per the older Mashable article above, it is _partially_ fixed, in that they don't do it for the examples in the article but do do it for other cases.