Connect with us

Published

on

Instagram users who regret sending that poorly worded direct message can now breathe a sigh of relief.

Engineers at parent company Meta Platforms Inc. have enabled a feature allowing Instagram users to edit their DMs within a 15-minute window after hitting the send button, according to the tech behemoth.

Instagram users need to press and hold on the sent message — which will then prompt a drop-down menu with an “edit” option, according to a blog posting by Meta.

The service will also enable users to choose up to three group or one-on-one chats and “pin” them to the top of their inbox, according to Meta.

Instagram users will only need to swipe left or tap and hold on the chat. Then they can choose the “pin” option.

The company also announced it will enable Instagram users to activate a “read receipts” option that lets others know that they’ve read their message.

Meta announced the change on Tuesday — the same day that users worldwide reported outages of its online platforms including Facebook, Instagram, WhatsApp and Threads.

The disruptions started at around 10 a.m. Eastern Time, with many users saying on rival social media platform X they had been booted out of Facebook and Instagram and were unable to log in.

Two hours later, services appeared to have been restored.

At the peak of the outage, there were more than 550,000 reports of disruptions for Facebook and about 92,000 for Instagram, according to outage tracking website Downdetector.com.

“Earlier today, a technical issue caused people to have difficulty accessing some of our services. We resolved the issue … for everyone who was impacted,” Meta spokesperson Andy Stone said in a post on X, without elaborating on the issue.

Shares of Meta were up 1.5% as of 1:00 p.m. Eastern Time on Wednesday.

The company has about 3.19 billion daily active users across its family of apps, which also includes WhatsApp and Threads.

Its status dashboard earlier showed the application programming interface for WhatsApp Business was also facing issues.

However, the outage for WhatsApp and Threads was much smaller, according to Downdetector, which tracks outages by collating status reports from several sources including users.

Several employees of Meta said on anonymous messaging app Blind that they were unable to log in to their internal work systems, which left them wondering if they were laid off, according to posts seen by Reuters.

The outage was among the top trending topics on X, formerly Twitter, with the platform’s owner Elon Musk taking a shot at Meta with a post that said: “If you’re reading this post, it’s because our servers are working.”

X itself has faced several disruptions to its service after Musk’s $44 billion purchase of the social media platform in October 2022, with an outage in December causing issues for more than 77,000 users in countries from the US to France.

With Post Wires

Continue Reading

Sports

Larson miscue ends in crash at Indy 500 practice

Published

on

By

Larson miscue ends in crash at Indy 500 practice

INDIANAPOLIS — Kyle Larson experienced his first crash at Indianapolis Motor Speedway on Thursday, the second day that Indianapolis 500 drivers participated in open testing on the 2.5-mile oval.

The 2021 NASCAR champion spun coming out of the first turn, hit the wall and bounced down to the warmup lane before tapping the wall a second time and eventually rolling to a stop.

Larson blamed himself, saying he forgot to hit the weight jacker going into the turn. But he also tried to find some positive from the incident.

“I’m happy to crash my first Indy car and live through it,” Larson said.

An Arrow McLaren official told The Indianapolis Star that Larson will not take part in the Thursday afternoon practice session due to the crash damage. The team decided not to rush the repairs, which would have left minimal practice time at best, the official said.

Larson is attempting to complete “the double” by racing in both the Indianapolis 500 and NASCAR’s Coca-Cola 600 on May 25. His first attempt was thwarted by a rain delay in the 2024 Indy 500 that saw him arrive to the NASCAR race just as that race was called off for weather.

He wasn’t the only familiar name to crash Thursday. Two-time Indianapolis 500 winner Takuma Sato crashed shortly after Larson, losing the back end of his car in the first turn and smacking the wall hard in the short chute before rolling to a stop.

“Lost it,” Sato said. “I simply lost it.”

Both drivers were checked at the infield hospital and released.

Graham Rahal also tapped the wall late in Wednesday’s practice.

Series officials added horsepower to the cars for the Thursday morning session as they test the IndyCar hybrid, which makes its IMS debut next month. An afternoon session without the boost closes out the two-day test.

The Associated Press contributed to this report.

Continue Reading

Sports

Spire releases crew chief Childers after 9 races

Published

on

By

Spire releases crew chief Childers after 9 races

CHARLOTTE, N.C. — Spire Motorsports has parted ways with championship-winning crew chief Rodney Childers after only nine races with the team.

Childers, one of the winningest active crew chiefs in the Cup Series, won the 2014 championship with Kevin Harvick at Stewart-Haas Racing. When that team closed at the end of last season, Childers moved to Spire to crew chief Justin Haley.

Through the first nine races, Haley is 23rd in the Cup standings. His best finish this year is 10th at Homestead, but Haley is coming off a 13th-place finish at Bristol, where he scored a season-high 13 stage points.

The decision to release Childers came after NASCAR’s only off weekend of the season. The team announced Thursday that Ryan Sparks, competition director and former crew chief, will be Haley’s crew chief for the rest of this season.

“NASCAR is an ever-evolving sport and the path to improvement isn’t always comfortable,” Spire Motorsports co-owner Jeff Dickerson said in a statement. “The break in the Cup Series schedule gave us a chance to evaluate where we are as a program. We took the opportunity to discuss the best paths forward for everyone involved and the team and Rodney agreed that it would be best for us to part ways.

“Rodney has worked at the highest level of our sport for 20 years, and he knows what it takes to win championships. With that in mind, we collectively acknowledged challenges with the team dynamic. Having the right combination of talent is just as important as the results on track. As we move in a new direction it is not lost on us that Rodney has been an invaluable asset to our organization, as he will continue to be for others in this sport.”

Childers addressed his departure on social media, writing: “I know this is a shock. But also know that not everything works out perfect all the time. That’s how life works. This was just one of those things that just wasn’t working for either of us. I appreciate my time at Spire, working with JH and the entire 7 team. We did a lot of good that is yet to be seen, and I wish them the best in the future.”

He said he would take some time off, focus on his family and “honestly just see what the racing world holds for me next.”

Childers is tied for second in wins among active crew chiefs. Childers and Adam Stevens each have 40 Cup wins. Paul Wolfe ranks first with 42 series victories.

Continue Reading

Politics

The hidden risk of updatable firmware

Published

on

By

The hidden risk of updatable firmware

The hidden risk of updatable firmware

Opinion by: Igor Zemtsov, chief technology officer at TBCC

Crypto security is a ticking time bomb. Updatable firmware might just be the match that lights the fuse.

Hardware wallets have become the holy grail of self-custody, the ultimate safeguard against hackers, scammers and even government overreach. There’s an inconvenient truth, however, that most people ignore: Firmware updates aren’t just security patches. 

They’re potential backdoors, waiting for someone — whether a hacker, a rogue developer or a shady third party — to kick them wide open.

Every time a hardware wallet manufacturer pushes an update, users are forced to make a choice. Hit that update button and hope for the best, or refuse to update and risk using outdated software with unknown vulnerabilities. Either way, it’s a gamble. 

In crypto, a bad gamble can mean waking up to an empty wallet.

Firmware updates aren’t always your friend

Updating firmware sounds like common sense. More security! Fewer bugs! Better user experience!

Here’s the thing: Every update is also an opportunity not just for the wallet provider but for anyone with the power, or motivation, to tamper with the process.

Hackers dream of firmware vulnerabilities. A rushed or poorly audited update can introduce tiny, almost imperceptible flaws — ones that sit in the background, waiting for the right moment to drain funds. And the best part? Users will never know what hit them.

Then there’s the more unsettling possibility: deliberate backdoors.

Recent: Hardware wallet Ledger helps competitor Trezor resolve security vulnerability

Tech companies have been forced to include government-mandated surveillance tools before. What makes anyone think hardware wallet makers are exempt? If a regulatory agency — or worse, a criminal organization — wants access to private keys, firmware updates are the perfect attack vector. One hidden function. One disguised line of code. 

That’s all it takes. Still think firmware updates are harmless? 

Firmware vulnerabilities are already being exploited

This isn’t some far-fetched, doomsday scenario. It has already happened.

Ledger, one of the biggest names in crypto security, had a major security crisis in 2018 when security researcher Saleem Rashid exposed a vulnerability that allowed attackers to replace Ledger Nano S firmware and hijack private keys. Nearly 1 million devices were at risk before a fix was rolled out. The scary part? There was no way for users to know if their devices had already been compromised.

In 2023, OneKey suffered a similar nightmare. White hat hackers demonstrated that its firmware could be cracked in mere seconds. No crypto was lost — this time. But what if real attackers had found the flaw first?

Then came the “Dark Skippy” exploit, taking firmware-based attacks to an entirely new level. With just two signed transactions, hackers could extract a user’s entire seed phrase — without setting off a single alarm. If firmware updates can be manipulated this easily, how can anyone be sure their assets are safe?

The hidden price of updatable firmware

To be fair, not all firmware updates are security disasters. Ledger uses a proprietary operating system and secure element chips for added protection now. Trezor takes an open-source approach, allowing the community to scrutinize its firmware. Coldcard and BitBox02 give users manual control over updates, reducing — but not eliminating — risk.

Here’s the real question: Can users ever be 100% sure that an update won’t introduce a fatal flaw?

Some wallets have decided to eliminate the risk altogether. Tangem ships with fixed, non-updatable firmware, meaning that its code can never be altered once the device leaves the factory. No updates. No patches. 

Of course, this approach has its trade-offs. If a vulnerability is discovered, there’s no way to fix it. But in security, predictability matters. 

Real crypto security means taking back control

The crypto market was worth $2.79 trillion as of March 2025. With that much money on the table, cybercriminals, rogue insiders and overreaching governments are always looking for weak points. Hardware wallet makers should be laser-focused on security.

Choosing a hardware wallet shouldn’t feel like gambling with private keys. It shouldn’t involve blind trust in a corporation’s ability to push updates responsibly. Users deserve more than vague reassurances. They deserve security models that put control where it belongs — with them.

Security isn’t about convenience. It’s about control. Any system that requires trusting unknown developers, opaque update processes or firmware that can be changed at will? That’s not control. That’s a liability.

The only real way to keep a hardware wallet safe? Remove the guesswork. Strip away the blind trust. Always research the developers’ backgrounds, check their track record for security incidents, and see how they’ve handled past vulnerabilities. Stick to verifiable facts — security should never be based on assumptions.

Opinion by: Igor Zemtsov, chief technology officer at TBCC.

This article is for general information purposes and is not intended to be and should not be taken as legal or investment advice. The views, thoughts, and opinions expressed here are the author’s alone and do not necessarily reflect or represent the views and opinions of Cointelegraph.

Continue Reading

Trending