On Monday, it appears X attempted to encourage users to cease referring to it as Twitter and instead adopt the name X. Some [users](https://twitter.com/t3dotgg/status/1777425000133468582 "(opens in a new window)") began [noticing](https://twitter.com/___frye/status/1777432913497465082 "(opens in a new window)") that posts [viewed](https://twitter.com/__justplaying/status/1777433986500853845 "(opens in a new window)") via X for iOS were [changing](https://twitter.com/luzfic/status/1777417205992562873 "(opens in a new window)") any [references](https://twitter.com/Arcticstar0/status/1777554091604103486 "(opens in a new window)") of "Twitter.com" to "X.com" automatically.

If a user typed in "Twitter.com," they would see "Twitter.com" as they typed it before hitting "Post." But, after submitting, the platform would show "X.com" in its place on the X for iOS app, without the user's permission, for everyone viewing the post.

And shortly after this revelation, it became clear that there was another big issue: X was changing anything ending in "Twitter.com" to "X.com."

  • sincle354@kbin.social
    link
    fedilink
    arrow-up
    85
    arrow-down
    1
    ·
    1 year ago

    Some poor mfer's shitty regex just got put on blast at a Twitter emergency software dev meeting.

    • TexasDrunk@lemmy.world
      link
      fedilink
      English
      arrow-up
      25
      ·
      1 year ago

      Some poor mfer's shitty regex just got put on blast

      Oh fuck, oh fuck, oh fuck

      at a Twitter emergency software dev meeting.

      Oh thank goodness!!!

    • Poplar?@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      I can't imagine how bad things must be for amateurish mistakes like that to have gotten through to the actual app.