iOS 18 Beta 3: What’s New for Developers in the Latest Update

It’s Mobile Monday, and we’re delighted to see that Apple has embraced the occasion by releasing iOS 18 Beta 3 today. This latest beta version brings a range of updates and refinements, moving closer to the official launch of iOS 18. With a focus on enhancing user experience, streamlining interfaces, and adding new features, this update highlights Apple’s ongoing commitment to improving its operating system based on feedback from developers and users.

Designer: Apple

One of the significant updates in iOS 18 Beta 3 is the introduction of Dark Mode icons for several third-party apps, including Facebook, Etsy, Telegram, Signal, Slack, Notion, and YouTube. These icons now automatically adjust to Dark Mode, with secondary colors becoming the main color and backgrounds turning black. More complex app icons are tinted darker, while developers have the option to provide their own dark-tinted icons for better customization.

The Photos app has received a usability enhancement by adding a Select button for a more accessible selection of multiple images, eliminating the need to swipe down. The Search button has also been updated to a blue-highlighted magnifying glass, improving visibility and ease of use.

Messages have undergone significant changes, particularly in its emoji and sticker interface. The new design combines emoji, Memoji, and stickers into a single interface, navigable through small icons at the bottom of the display. Users can create and use stickers directly in messages, with non-moving stickers displayed similarly to emojis. Emojis are now shown larger, providing more detail but requiring more scrolling to see additional characters. These enhancements pave the way for the introduction of Apple Intelligence, including features like Genmoji and Image Playground.

Apple has also added a dynamic wallpaper option that transitions through different colors based on the time of day, making iOS 18 visually engaging. The flashlight interface has been refined, offering a more extensive and intuitive control for adjusting brightness and LED flash spread when activated from the Dynamic Island.

The Maps app continues to receive tweaks, particularly its icon colors, when Dark Mode is enabled, ensuring a consistent and seamless user experience. Additionally, the interface for RCS in the Messages settings has been updated to a tap-in menu that provides more context, such as the use of wireless data and the sharing of cellular network identifiers with carriers.

Hints of Apple Intelligence are becoming more apparent, with code references to features like Genmoji, Image Playground, Writing Tools, and Image Wand. These forthcoming AI enhancements are expected to significantly augment the capabilities of iOS 18, offering users a smarter, more responsive experience.

iOS 18 beta 3 is a clear sign that Apple is committed to making its operating system better and more user-friendly with every update. This release shows how Apple listens to feedback and continues to refine features, fix bugs, and add new capabilities to ensure users have a smooth and enjoyable experience with each new version.

The post iOS 18 Beta 3: What’s New for Developers in the Latest Update first appeared on Yanko Design.

Microsoft Notepad just got spellcheck in the year 2024

It has finally happened. Microsoft’s text editor Notepad just got a spellcheck feature, more than 40 years after the software launched in 1983. For the history buffs, Ronald Reagan was still president in 1983 and Ghostbusters, then called Ghost Smashers, was an unmade script set to star Eddie Murphy. It was a long time ago.

Microsoft just rolled out the new spellcheck tool to the Notepad app in Windows 11 and it works how one would expect. It automatically checks spelling errors. The company began testing the feature, to whatever extent it required testing, back in March and now it has been quietly updating the software these last few days, as reported by The Verge.

Specifically, the feature works nearly the same as it does in Word or Edge. Misspelled words are highlighted via a red underline. When you right-click on the misspelled word a couple of times, you get a list of correct spelling options to change to. Microsoft has also added autocorrect to the mix, which automatically fixes errors. You get the gist. It’s 2024.

One interesting aspect, however, is that you can disable spellcheck on the basis of file type in Notepad via the settings menu. In other words, you can toggle the feature off for file types like .md or .srt. It’s automatically disabled with file types associated with coding, like log files. Also, it takes an extra click on Notepad to replace a spelling error when compared to Word. As for Word, it first got a spellcheck in 1985. Ronald Reagan was still president and Ghostbusters had just proven itself to be a massive hit.

Microsoft is about to remove the WordPad app from Windows 11 later this year, so it’s beefing up Notepad to pick up the slack. Notepad has recently gotten a dark mode, actual tabs, a character count and, well, a virtual fidget spinner. It’s also been stuffed to the gills with AI, in the form of Copilot integration.

This article originally appeared on Engadget at https://www.engadget.com/microsoft-notepad-just-got-spellcheck-in-the-year-2024-154043158.html?src=rss

Nike is killing the app for its futuristic Adapt BB sneakers

Nike is discontinuing its self-lacing Adapt BB sneakers and providing a case in point of what can happen to tech that relies on apps. First announced in 2019, the sneakers used a Back to the Future II style power-lacing system called FitAdapt that was adjustable either manually or with an app. Now, the company will no longer make new Adapt shoes and is retiring the Nike Adapt App, it announced in a help document spotted by The Verge

"After five years, we’re retiring the Adapt App and removing it from the Apple and Android app stores, globally, on August 6, 2024," the page states. "Don’t worry, your Adapt shoes will continue to work without the app. See below for more information about the retirement of the Adapt App."

A FAQ goes on to state that the Adapt app "should continue to function" follow its removal, if you already have it installed. You won't be able to move it to a new device, though, and future iOS updates may limit or end functionality. 

Nike goes on to state that if the app is removed, the shoes will retain the last light color selected. Features still available without it include power on, check battery status, adjust your fit, save your fit, unlace shoes and power off. 

Perhaps the biggest loss with the end of Adapt is in accessibility, as the shoes were marketed in part as a way to make shoe tying easier for people with limited mobility. It also shows the danger of tying functionality of physical technology to custom apps — once the app loses support, the product gets a lot worse and there's not much you can do about it. 

This article originally appeared on Engadget at https://www.engadget.com/nike-is-killing-the-app-for-its-futuristic-adapt-bb-sneakers-120039424.html?src=rss

Nike is killing the app for its futuristic Adapt BB sneakers

Nike is discontinuing its self-lacing Adapt BB sneakers and providing a case in point of what can happen to tech that relies on apps. First announced in 2019, the sneakers used a Back to the Future II style power-lacing system called FitAdapt that was adjustable either manually or with an app. Now, the company will no longer make new Adapt shoes and is retiring the Nike Adapt App, it announced in a help document spotted by The Verge

"After five years, we’re retiring the Adapt App and removing it from the Apple and Android app stores, globally, on August 6, 2024," the page states. "Don’t worry, your Adapt shoes will continue to work without the app. See below for more information about the retirement of the Adapt App."

A FAQ goes on to state that the Adapt app "should continue to function" follow its removal, if you already have it installed. You won't be able to move it to a new device, though, and future iOS updates may limit or end functionality. 

Nike goes on to state that if the app is removed, the shoes will retain the last light color selected. Features still available without it include power on, check battery status, adjust your fit, save your fit, unlace shoes and power off. 

Perhaps the biggest loss with the end of Adapt is in accessibility, as the shoes were marketed in part as a way to make shoe tying easier for people with limited mobility. It also shows the danger of tying functionality of physical technology to custom apps — once the app loses support, the product gets a lot worse and there's not much you can do about it. 

This article originally appeared on Engadget at https://www.engadget.com/nike-is-killing-the-app-for-its-futuristic-adapt-bb-sneakers-120039424.html?src=rss

OpenAI hit by two big security issues this week

OpenAI seems to make headlines every day and this time it's for a double dose of security concerns. The first issue centers on the Mac app for ChatGPT, while the second hints at broader concerns about how the company is handling its cybersecurity.

Earlier this week, engineer and Swift developer Pedro José Pereira Vieito dug into the Mac ChatGPT app and found that it was storing user conversations locally in plain text rather than encrypting them. The app is only available from OpenAI's website, and since it's not available on the App Store, it doesn't have to follow Apple's sandboxing requirements. Vieito's work was then covered by The Verge, and after the exploit attracted attention, OpenAI released an update that added encryption to locally stored chats.

For the non-developers out there, sandboxing is a security practice that keeps potential vulnerabilities and failures from spreading from one application to others on a machine. And for non-security experts, storing local files in plain text means potentially sensitive data can be easily viewed by other apps or malware.

The second issue occurred in 2023 with consequences that have had a ripple effect continuing today. Last spring, a hacker was able to obtain information about OpenAI after illicitly accessing the company's internal messaging systems. The New York Times reported that OpenAI technical program manager Leopold Aschenbrenner raised security concerns with the company's board of directors, arguing that the hack implied internal vulnerabilities that foreign adversaries could take advantage of.

Aschenbrenner now says he was fired for disclosing information about OpenAI and for surfacing concerns about the company’s security. A representative from OpenAI told The Times that “while we share his commitment to building safe A.G.I., we disagree with many of the claims he has since made about our work” and added that his exit was not the result of whistleblowing.

App vulnerabilities are something that every tech company has experienced. Breaches by hackers are also depressingly common, as are contentious relationships between whistleblowers and their former employers. However, between how broadly ChatGPT has been adopted into major players' services and how chaotic the company's oversight, practices and public reputation have been, these recent issues are beginning to paint a more worrying picture about whether OpenAI can manage its data.

This article originally appeared on Engadget at https://www.engadget.com/openai-hit-by-two-big-security-issues-this-week-214316082.html?src=rss

OpenAI hit by two big security issues this week

OpenAI seems to make headlines every day and this time it's for a double dose of security concerns. The first issue centers on the Mac app for ChatGPT, while the second hints at broader concerns about how the company is handling its cybersecurity.

Earlier this week, engineer and Swift developer Pedro José Pereira Vieito dug into the Mac ChatGPT app and found that it was storing user conversations locally in plain text rather than encrypting them. The app is only available from OpenAI's website, and since it's not available on the App Store, it doesn't have to follow Apple's sandboxing requirements. Vieito's work was then covered by The Verge, and after the exploit attracted attention, OpenAI released an update that added encryption to locally stored chats.

For the non-developers out there, sandboxing is a security practice that keeps potential vulnerabilities and failures from spreading from one application to others on a machine. And for non-security experts, storing local files in plain text means potentially sensitive data can be easily viewed by other apps or malware.

The second issue occurred in 2023 with consequences that have had a ripple effect continuing today. Last spring, a hacker was able to obtain information about OpenAI after illicitly accessing the company's internal messaging systems. The New York Times reported that OpenAI technical program manager Leopold Aschenbrenner raised security concerns with the company's board of directors, arguing that the hack implied internal vulnerabilities that foreign adversaries could take advantage of.

Aschenbrenner now says he was fired for disclosing information about OpenAI and for surfacing concerns about the company’s security. A representative from OpenAI told The Times that “while we share his commitment to building safe A.G.I., we disagree with many of the claims he has since made about our work” and added that his exit was not the result of whistleblowing.

App vulnerabilities are something that every tech company has experienced. Breaches by hackers are also depressingly common, as are contentious relationships between whistleblowers and their former employers. However, between how broadly ChatGPT has been adopted into major players' services and how chaotic the company's oversight, practices and public reputation have been, these recent issues are beginning to paint a more worrying picture about whether OpenAI can manage its data.

This article originally appeared on Engadget at https://www.engadget.com/openai-hit-by-two-big-security-issues-this-week-214316082.html?src=rss

You can now get AI Judy Garland or James Dean to read you the news

I love an account on X (formerly Twitter) called @LizaMinnelliOutlives (shockingly not run by the icon herself) that lists things like famous deaths or agreements. Well, in a twist, the real Liza Minnelli no longer outlives new words from her deceased mother, Judy Garland. The actress and singer has given ElevenLabs, an AI startup with cloning services, permission to recreate her mother's voice for their new Reader App. Garland joins James Dean, Burt Reynolds and Sir Laurence Olivier as deceased stars whose AI voices are in the "Iconic voice collection," thanks to deals with their estates for undisclosed sums. 

The voices will exist solely on the Reader App and people can use them for things like narrating an e-book. "It's exciting to see our mother's voice available to the countless millions of people who love her," Minnelli, the representative of the Garland Estate, said. "Through the spectacular new technology offered by ElevenLabs, our family believes that this will bring new fans to Mama, and be exciting to those who already cherish the unparalleled legacy that Mama gave and continues to give to the world." A sample of Garland reading The Wizard of Oz appears in ElevenLab's promotional video on YouTube — personally, I find it a little bit eerie, but I can see the appeal. 

ElevenLabs released its Reader App in late June to allow users to hear any text on their phone, including messages, PDFs and news articles. It's currently only available in English for iOS users in the United States, United Kingdom and Canada. However, ElevenLabs has a waitlist for Android users and claims it will launch in the Google Play store in the "coming weeks." The company also says it's working on making the app available in every language its Multilingual model supports (29 as of now) and will, subsequently, launch it globally.

This article originally appeared on Engadget at https://www.engadget.com/you-can-now-get-ai-judy-garland-or-james-dean-to-read-you-the-news-160023595.html?src=rss

The iPad and Blackmagic’s Micro Color Panel make strange bedfellows

With the current rebellion against Adobe’s subscription model, folks are taking a hard look at Blackmagic Design’s DaVinci Resolve Studio. And many like what they see. It’s arguably more powerful than Adobe’s Premiere Pro, offering better color correction tools along with built-in effects and audio apps. Best of all, it’s free (though you can pay $300 to upgrade to the Studio version).

To make it more practical for those editing on the go, Blackmagic introduced an iPad version in late 2022 with the Cut (editing) and Color pages, but no effects or audio apps. The idea was to offer creators a way to edit or color-correct on the road, with everything syncing up via Blackmagic Cloud. It was also a good option for those who prefer to work on mobile devices.

Earlier this year, Blackmagic introduced the $509 Micro Color Panel that gave users tactile control for color correction, just like the highly paid colorists in Hollywood. Better still, it can be used with Resolve on iPad, so you can click, dial and roll in a precise manner, rather than pawing inaccurately on a touch display.

DaVinci Resolve for iPad and the Micro Color Panel are cool separately
Steve Dent for Engadget

I love control surfaces, so I was eager to test the Micro Color Panel with my iPad Air M2 to see how they work together. At the same time, I wanted to try out Blackmagic’s Cloud to share projects on multiple devices.

You get two installs with DaVinci Resolve Studio, so I used my desktop key to install it on my iPad Air M2. Blackmagic recommends an iPad with an M1 or later processor, and though it will work with earlier iPads, you may be restricted to HD and features will be limited.

Blackmagic provided me with a free trial of its Cloud service so I could transfer projects from my desktop over to the iPad. That normally costs $5 per month per library, which gives you 500GB of storage and unlimited projects that can be shared with up to 10 collaborators.

You can easily share timelines, effects, metadata and media. To transfer files, you can either connect a USB-C drive or share full or proxy media (smaller versions of your video clips) on Blackmagic Cloud. That requires a fast connection — both to upload and download — but once that’s done, they live locally on your iPad. Any new media files are automatically synced to the Cloud.

DaVinci Resolve for iPad and the Micro Color Panel are cool separately
Steve Dent for Engadget

The downside of DaVinci Resolve on an iPad is the clumsy touch-based interface, especially for color correction – but that’s where the Micro Color Panel comes in. Blackmagic has a rich history of building such controllers for professional use, but the new model is its smallest and cheapest to date.

Though diminutive compared to the $859 version, the new Micro Panel still oozes quality. Its black finish can draw some dust but otherwise looks professional. The buttons light up to help you find them in a dark studio, but the labels on the dials don’t, so they can be hard to read.

The panel comes with its own battery that gives you about 15 hours on a charge. Though you can use USB-C to connect to PCs or Macs, iPads only support Bluetooth, with USB-C reserved for charging.

After pairing the Micro Control Panel to your iPad, you need to enable it in DaVinci Resolve’s preferences. Then, you can slide your iPad into the slot on the back and you’re ready to work.

DaVinci Resolve for iPad and the Micro Color Panel are cool separately
Steve Dent for Engadget

To be clear, the Micro Control Panel is not designed for editing — it’s strictly for color correction. To that end, it mirrors the interface of DaVinci Resolve’s Color Page. The main controls are for “Lift” (black levels), “Gamma” (contrast) and “Gain” (overall brightness).

Those wheels and dials offer nice levels of resistance and accuracy, compared to the Loupedeck+ and other types of control surfaces I’ve tried. They're used for things like shadows, highlights and saturation, while the buttons let you view the image full screen, move from clip to clip, add keyframes and more.

The tactile experience is a strong selling point of the Micro Control Panel, but there’s a catch-22 using it with the iPad. At home, I’d be likely to use it with my PC or Mac for more speed and versatility. When I’m on the road with my iPad, though, I’m not sure I’d take the Micro Control Panel with me, because it’s too bulky.

DaVinci Resolve for iPad and the Micro Color Panel are cool separately
Steve Dent for Engadget

So despite Blackmagic marketing this as an iPad accessory, I’d say it’s currently better for desktop DaVinci Resolve Studio users who want more tactile control. It’s great for people who only edit on iPad, but I’d imagine that in a Venn diagram of those folks and the ones willing to spend $508 on a color correction panel, there is only a tiny overlap.

In sum, Blackmagic’s Micro Color Panel is portable, attractive, well-designed, nice to use and reasonably priced. If you spend a lot of time on color correction, you’ll find it to be a timesaver once the controls become second nature. It’ll also make your editing suite look more professional.

Though not yet a great match for the iPad, that could change. Apple recently launched the iPad Pro M4, including a 13-inch model that offers similar performance to many MacBooks. At the same time, Blackmagic Design has promised to bring the iPad version of DaVinci Resolve more on par with the desktop versions. If that happens, many Resolve users may opt to use the iPad version exclusively — which would make the Micro Color Panel more desirable.

This article originally appeared on Engadget at https://www.engadget.com/the-ipad-and-blackmagics-micro-color-panel-make-strange-bedfellows-183835929.html?src=rss

What Meta should change about Threads, one year in

It’s been a year since Meta pushed out Threads in an attempt to take on the platform now known as X. At the time, Mark Zuckerberg said that he hoped it would turn into “a public conversations app with 1 billion+ people on it.”

Meta’s timing was good. Threads launched at a particularly chaotic moment for Twitter, when many people were seeking out alternatives. Threads saw 30 million sign-ups in its first day and the app has since grown to 175 million monthly users, according to Zuckerberg. (X has 600 million monthly users, according to Elon Musk.)

But the earliest iteration of Threads still felt a little bit broken. There was no web version, and a lot of missing features. The company promised interoperability with ActivityPub, the open-source standard that powers Mastodon and other apps in the fediverse, but integration remains minimal.

One year later, it’s still not really clear what Threads is actually for. Its leader has said that "the goal isn’t to replace Twitter” but to create a “public square” for Instagram users and a “less angry place for conversations.”But the service itself still has a number of issues that prevent it from realizing that vision. If Meta really wants to make that happen, here’s what it should change.

If you follow me on Threads, then you probably already know this is my top complaint. But Meta desperately needs to fix the algorithm that powers Threads’ default “For You” feed. The algorithmic feed, which is the default view in both the app and website, is painfully slow. It often surfaces days-old posts, even during major, newsworthy moments when many people are posting about the same topic.

It’s so bad it’s become a running meme to post something along the lines of “I can’t wait to read about this on my ‘For You’ feed tomorrow,” every time there’s a major news event or trending story.

The algorithmic feed is also downright bizarre. For a platform that was built off of Instagram, an app that has extremely fine-tuned recommendations and more than a decade of data about the topics I’m interested in, Threads appears to use none of it. Instead, it has a strange preference for intense personal stories from accounts I’m entirely unconnected to.

In the last year, I’ve seen countless multi-part Threads posts from complete strangers detailing childhood abuse, eating disorders, chronic illnesses, domestic violence, pet loss and other unimaginable horrors. These are not posts I’m seeking out by any means, yet Meta’s algorithm shoves them to the top of my feed.

I’ve aggressively used Threads' swipe gestures to try to rid my feed of excessive trauma dumping, and it’s helped to some extent. But it hasn’t improved the number of strange posts I see from completely random individuals. At this moment the top two posts in my feed are from an event planner offering to share wedding tips and a woman describing a phone call from her health insurance company. (Both posts are 12 hours old.) These types of posts have led to blogger Max Read dubbing Threads the “gas leak social network” because they make it feel as if everyone is “suffering some kind of minor brain damage.”

Look, I get why Meta has been cautious when it comes to content moderation on Threads. The company doesn’t exactly have a great track record on issues like extremism, health misinformation or genocide-inciting hate speech. It’s not surprising they would want to avoid similar headlines about Threads.

But if Meta wants Threads to be a “public square,” it can’t preemptively block searches for topics like COVID-19 and vaccines just because they are “potentially sensitive.” (Instagram head Adam Mosseri claimed this measure was “temporary” last October.) If Meta wants Threads to be a “public square,” it shouldn’t automatically throttle political content from users’ recommendations; and Threads’ leaders shouldn’t assume that users don’t want to see news.

A year in, it’s painfully clear that a platform like Threads is hamstrung without a proper direct messaging feature. For some reason, Threads’ leaders, especially Mosseri, have been adamantly opposed to creating a separate inbox for the app.

Instead, users hoping to privately connect with someone on Threads are forced to switch over to Instagram and hope the person they are trying to reach accepts new message requests. There is an in-app way to send a Threads post to an Instagram friend but this depends on you already being connected on Instagram.

Exactly why Threads can’t have its own messaging feature isn’t exactly clear. Mosseri has suggested that it doesn’t make sense to build a new inbox for the app, but that ignores the fact that many people use Instagram and Threads very differently. Which brings me to…

Meta has said that the reason why it was able to get Threads out the door so quickly was largely thanks to Instagram. Threads was created using a lot of Instagram’s code and infrastructure, which also helped the company get tens of millions of people to sign up for the app on day one.

But continuing to require an Instagram account to use Threads makes little sense a year on. For one, it shuts out a not-insignificant number of people who may be interested in Threads but don’t want to be on Instagram,

There’s also the fact that the apps, though they share some design elements, are completely different kinds of services. And many people, myself included, use Instagram and Threads very differently.

A “public square” platform like Threads works best for public-facing accounts where conversations can have maximum visibility. But most people I know use their Instagram accounts for personal updates, like family photos. And while you can have different visibility settings for each app, you shouldn’t be forced to link the two accounts. This also means that if you want to use Threads anonymously, you would need to create an entirely new Instagram account to serve as a login for the corresponding Threads account.

It seems that Meta is at least considering this. Mosseri said in an interview with Platformer that the company is “working on things like Threads-only accounts” and wants the app to become “more independent.”

These aren’t the only factors that will determine whether Threads will be, as Zuckerberg has speculated, Meta’s next 1 billion-user app. Meta will, eventually, need to make money from the service, which is currently advertising-free. But before Meta’s multibillion-dollar ad machine can be pointed at Threads, the company will need to better explain who its newest app is actually for.

This article originally appeared on Engadget at https://www.engadget.com/what-meta-should-change-about-threads-one-year-in-173036784.html?src=rss

What Meta should change about Threads, one year in

It’s been a year since Meta pushed out Threads in an attempt to take on the platform now known as X. At the time, Mark Zuckerberg said that he hoped it would turn into “a public conversations app with 1 billion+ people on it.”

Meta’s timing was good. Threads launched at a particularly chaotic moment for Twitter, when many people were seeking out alternatives. Threads saw 30 million sign-ups in its first day and the app has since grown to 175 million monthly users, according to Zuckerberg. (X has 600 million monthly users, according to Elon Musk.)

But the earliest iteration of Threads still felt a little bit broken. There was no web version, and a lot of missing features. The company promised interoperability with ActivityPub, the open-source standard that powers Mastodon and other apps in the fediverse, but integration remains minimal.

One year later, it’s still not really clear what Threads is actually for. Its leader has said that "the goal isn’t to replace Twitter” but to create a “public square” for Instagram users and a “less angry place for conversations.”But the service itself still has a number of issues that prevent it from realizing that vision. If Meta really wants to make that happen, here’s what it should change.

If you follow me on Threads, then you probably already know this is my top complaint. But Meta desperately needs to fix the algorithm that powers Threads’ default “For You” feed. The algorithmic feed, which is the default view in both the app and website, is painfully slow. It often surfaces days-old posts, even during major, newsworthy moments when many people are posting about the same topic.

It’s so bad it’s become a running meme to post something along the lines of “I can’t wait to read about this on my ‘For You’ feed tomorrow,” every time there’s a major news event or trending story.

The algorithmic feed is also downright bizarre. For a platform that was built off of Instagram, an app that has extremely fine-tuned recommendations and more than a decade of data about the topics I’m interested in, Threads appears to use none of it. Instead, it has a strange preference for intense personal stories from accounts I’m entirely unconnected to.

In the last year, I’ve seen countless multi-part Threads posts from complete strangers detailing childhood abuse, eating disorders, chronic illnesses, domestic violence, pet loss and other unimaginable horrors. These are not posts I’m seeking out by any means, yet Meta’s algorithm shoves them to the top of my feed.

I’ve aggressively used Threads' swipe gestures to try to rid my feed of excessive trauma dumping, and it’s helped to some extent. But it hasn’t improved the number of strange posts I see from completely random individuals. At this moment the top two posts in my feed are from an event planner offering to share wedding tips and a woman describing a phone call from her health insurance company. (Both posts are 12 hours old.) These types of posts have led to blogger Max Read dubbing Threads the “gas leak social network” because they make it feel as if everyone is “suffering some kind of minor brain damage.”

Look, I get why Meta has been cautious when it comes to content moderation on Threads. The company doesn’t exactly have a great track record on issues like extremism, health misinformation or genocide-inciting hate speech. It’s not surprising they would want to avoid similar headlines about Threads.

But if Meta wants Threads to be a “public square,” it can’t preemptively block searches for topics like COVID-19 and vaccines just because they are “potentially sensitive.” (Instagram head Adam Mosseri claimed this measure was “temporary” last October.) If Meta wants Threads to be a “public square,” it shouldn’t automatically throttle political content from users’ recommendations; and Threads’ leaders shouldn’t assume that users don’t want to see news.

A year in, it’s painfully clear that a platform like Threads is hamstrung without a proper direct messaging feature. For some reason, Threads’ leaders, especially Mosseri, have been adamantly opposed to creating a separate inbox for the app.

Instead, users hoping to privately connect with someone on Threads are forced to switch over to Instagram and hope the person they are trying to reach accepts new message requests. There is an in-app way to send a Threads post to an Instagram friend but this depends on you already being connected on Instagram.

Exactly why Threads can’t have its own messaging feature isn’t exactly clear. Mosseri has suggested that it doesn’t make sense to build a new inbox for the app, but that ignores the fact that many people use Instagram and Threads very differently. Which brings me to…

Meta has said that the reason why it was able to get Threads out the door so quickly was largely thanks to Instagram. Threads was created using a lot of Instagram’s code and infrastructure, which also helped the company get tens of millions of people to sign up for the app on day one.

But continuing to require an Instagram account to use Threads makes little sense a year on. For one, it shuts out a not-insignificant number of people who may be interested in Threads but don’t want to be on Instagram,

There’s also the fact that the apps, though they share some design elements, are completely different kinds of services. And many people, myself included, use Instagram and Threads very differently.

A “public square” platform like Threads works best for public-facing accounts where conversations can have maximum visibility. But most people I know use their Instagram accounts for personal updates, like family photos. And while you can have different visibility settings for each app, you shouldn’t be forced to link the two accounts. This also means that if you want to use Threads anonymously, you would need to create an entirely new Instagram account to serve as a login for the corresponding Threads account.

It seems that Meta is at least considering this. Mosseri said in an interview with Platformer that the company is “working on things like Threads-only accounts” and wants the app to become “more independent.”

These aren’t the only factors that will determine whether Threads will be, as Zuckerberg has speculated, Meta’s next 1 billion-user app. Meta will, eventually, need to make money from the service, which is currently advertising-free. But before Meta’s multibillion-dollar ad machine can be pointed at Threads, the company will need to better explain who its newest app is actually for.

This article originally appeared on Engadget at https://www.engadget.com/what-meta-should-change-about-threads-one-year-in-173036784.html?src=rss