97
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 10 Apr 2024
97 points (100.0% liked)
technology
23313 readers
70 users here now
On the road to fully automated luxury gay space communism.
Spreading Linux propaganda since 2020
- Ways to run Microsoft/Adobe and more on Linux
- The Ultimate FOSS Guide For Android
- Great libre software on Windows
- Hey you, the lib still using Chrome. Read this post!
Rules:
- 1. Obviously abide by the sitewide code of conduct. Bigotry will be met with an immediate ban
- 2. This community is about technology. Offtopic is permitted as long as it is kept in the comment sections
- 3. Although this is not /c/libre, FOSS related posting is tolerated, and even welcome in the case of effort posts
- 4. We believe technology should be liberating. As such, avoid promoting proprietary and/or bourgeois technology
- 5. Explanatory posts to correct the potential mistakes a comrade made in a post of their own are allowed, as long as they remain respectful
- 6. No crypto (Bitcoin, NFT, etc.) speculation, unless it is purely informative and not too cringe
- 7. Absolutely no tech bro shit. If you have a good opinion of Silicon Valley billionaires please manifest yourself so we can ban you.
founded 4 years ago
MODERATORS
I'm by no means an expert at website things, but wouldn't it be way simpler to take any request to twitter.com and just redirect it to x.com? Pretty sure websites do this all the time, like if you type chapo.chat into the address bar it loads hexbear.net instead.
Actually they literally already do this in the opposite direction. x.com goes to twitter.com. So someone types twitter.com in a tweet, twitter filters it to x.com, then when you click on it it loads twitter.com. Great job Elon, 10/10 no notes.
This is a branding move. He wants the name "x.com" to show up more.
The rewritten url still hyperlinks to "twitter.com" and "x.com" still redirects to "twitter.com"
They didn't want to change domain names because that's a nightmare for backend tooling. I'll bet there's over a decade of internal tools that check for "twitter.com" in some response or something.
Damn that sucks, hope he didn't fire all of his experienced engineers who could have gone through the backend and made those changes.