Meta moves Threads from Threads.net to Threads.com and updates its web app, including features to more easily access custom feeds, create new columns, and more
Apple Watch turns a decade old today. Cheers to 10 amazing years! 🥂 Threads : Allow the use of cookies from Threads by Instagram on this browser? Bluesky: @thespoileralert : Is that still a thing? Huh Threads: Adam Mosseri / @mosseri : We're making some simple but meaningful updates to Threads web as we move to threads.com today. You can now create posts while scrolling your feeds, easily access custom feeds at the top of the web page, and copy and paste a post as an image for cleaner sharing on other apps. … @threads : threads.net 🤝 threads.com BinHong Lee / @binhonglee : Seems like the session didn't directly transfer over properly in some browsers. I'd imagine there might be an increase in login_success for Threads mweb and maybe IG mweb. (Not so much on FB due to sheer difference in scale / traffic. Iirc FB have a significantly larger mweb traffic compared to IG.) Jane Manchun Wong / @wongmjane : Switching Threads to .com (commercial) sounds fitting as they're launching ads on the platform Casey Newton / @crumbler : welcome to Threads dot COM Wolf Ha / @mistakenotmy : Ok .. so @threads changed the domain of the web interface to threads dot com. Which is confusing if you had fediverse sharing enabled. — My handle was threads dot net, obviously, and as far as I can see from mastodon, my posts are still being federated under that handle. … @threads : Psst: We've got a few updates for Threads on web: 🖥️ Smoother feed navigation 🖥️ A pop-up composer 🖥️ A quick way to add columns Everything you need to know 👇 See also Mediagazer
Context & Ripple Effects
Threads first made its web app broadly available with the core navigation found on mobile in its initial desktop rollout. The move to Threads.com and new workflow tools mark a more deliberate iteration on that web presence rather than a standalone product launch.
The updates arrive as Threads has also tested federated connections, beginning with cross-posting and engagement visibility through fediverse tools. That makes control over its own web experience relevant even as Meta selectively expands interoperability.
First-order effects
- Threads users get a single Threads.com destination plus a web composer that remains available while they browse feeds, reducing the interruption of switching views to post.
- Custom feeds become easier to reach and organize into columns, while image-based copying gives posts a cleaner handoff to other apps.
Second-order effects
- The changes make the web client more useful for people monitoring multiple conversations, raising the practical value of Threads' desktop experience relative to a basic mobile companion.
- Greater visibility for custom feeds can shift attention from one default feed toward user-selected topic or account groupings, giving users more control over what they monitor.
Third-order effects
- If Meta continues adding desktop-specific workflows, Threads could evolve from a mobile-first social feed into a more configurable publishing and monitoring surface, where web utility helps determine retention among heavier users.
- The combination of internal feed controls and limited federated features suggests social platforms may compete on both interface control and selective interoperability rather than treating them as mutually exclusive.
The trend: Threads is part of a broader shift in which social platforms turn web clients into configurable workspaces while retaining control of the core feed and sharing experience.