Article 6FH21 Threads gets an edit button, no subscription required

Threads gets an edit button, no subscription required

by
Kris Holt
from Engadget is a web magazine with obsessive daily coverage of everything new in gadgets and consumer electronics on (#6FH21)

Threads is now rolling out a pair of useful updates as Meta tries to give the app some more momentum. One of the new features is an edit button, which will help folks avoid having to repost something when they want to correct a mistake.

X (formerly Twitter) took 16 years to add an edit button, and then it placed it behind the Twitter Blue/X Premium paywall. Threads took just over three months to introduce a similar option, which is free to all users and will be available on mobile and the web.

e700c520-6933-11ee-8fff-82ff7be9fb94Adam Mosseri / Threads

After you post something on Threads, you'll have five minutes to edit it, as 9to5Google points out. That's a reasonable enough timeframe (X users have up to an hour to tweak their tweets). On the downside, Threads doesn't show the edit history for a post. That's bad for transparency, especially if someone significantly changes the substance of a post that gains traction very quickly.

Meta CEO Mark Zuckerberg also noted that Threads is adding the option to post voice clips. These feature "karaoke-style transcription." That's another welcome update, especially for those who prefer speaking to typing (or using voice-to-text features). Meanwhile, it appears that Threads is working on a trending topics feature.

eb574e00-6933-11ee-a9f5-d01e090fdba8Adam Mosseri / ThreadsThis article originally appeared on Engadget at https://www.engadget.com/threads-is-rolling-out-an-edit-button-that-you-dont-have-to-pay-for-180341726.html?src=rss
External Content
Source RSS or Atom Feed
Feed Location https://www.engadget.com/rss.xml
Feed Title Engadget is a web magazine with obsessive daily coverage of everything new in gadgets and consumer electronics
Feed Link https://www.engadget.com/
Feed Copyright copyright Yahoo 2024
Reply 0 comments