Urgent.News

What's breaking now, across hundreds of outlets.

Tech

The pros and cons of using a VPN over encrypted DNS

Explore the perks and drawbacks of choosing a VPN over encrypted DNS, from privacy and security to speed, costs, and control over your browsing habits.

The pros and cons of using a VPN over encrypted DNS

In 2026, "dumb phones" are once again gaining popularity as devices that offer basic features such as calls, text messages, and alarm settings. These pared-down devices are designed to minimize distractions often caused by modern smartphones, which are filled with social media, emails, and constant notifications. However, there are pros and cons to using a dumb phone in today's world.

One of the main advantages of a dumb phone is the reduction in screen time. With limited access to apps and features, users can avoid the temptation to constantly check their phone, which can be challenging with smartphones. Most dumb phones are limited to basic apps for making calls, sending messages, and setting alarms, while others run a basic version of Android that allows for some app installations but not as many as modern smartphones.

Another benefit of using a dumb phone is its long battery life. With small screens and underpowered chips, these phones can last for days on a single charge. The TCL Flip Go, for example, has a battery rated to last around 14 days on standby, making it an ideal companion for adventures like road trips or hikes.

Privacy is also a concern for some users, as dumb phones typically don't have third-party apps, meaning fewer trackers can collect user data for ad targeting purposes. Additionally, dumb phones are significantly cheaper than most smartphones, with the cheapest Android models usually costing twice as much as dumb phones.

However, there are several drawbacks to using a dumb phone. These devices sacrifice many conveniences offered by smartphones, such as mobile wallets like Apple Pay or Samsung Pay, portable cameras, and access to popular streaming apps like Spotify or Apple Music. Additionally, messaging options may be limited to SMS or RCS, and internet access is often restricted to 4G networks.

In conclusion, dumb phones can be a great option for those looking to reduce screen time and privacy concerns, but they come with several limitations. For most people, a dumb phone should be considered as a secondary device rather than a full replacement for a smartphone.

Rewritten by urgent.news; may contain errors — check the original.

Other reports of this story

Every outlet that reported this, and when →

Read the original at engadget.com →

Report a problem with this story

More in Tech

Headless UI for Beginners: Accessible Components Without the Styling

Building a dropdown or a modal sounds simple until you try to do it properly. Keyboard navigation, focus trapping, screen reader announcements, closing on Escape — accessibility is a long checklist.

  • Headless UI provides accessible components without styling.
  • Implement dropdown using Menu, Menu.Button, Menu.Items, Menu.Item components.
  • Headless UI handles keyboard interactions automatically.

I let a script audit my own product copy — it caught three lies

I run a small store that sells digital kits for people running LLM agents — eval suites, ops runbooks, prompt libraries. Every product page makes claims: "62 prompts," "10 skills," "12 runbooks." Last…

  • Store owner wrote script to audit product copy
  • Found three instances of false claims in descriptions
  • Audit process compares numbers in copy to actual files

No Algorithm Lock-In: Why a Chronological On-Chain Feed Is Regulation-Proof by Design

Governments are moving to force social platforms to offer a chronological, non-algorithmic feed option. On iBird, chronology is not a compliance setting — it is the substrate.

  • iBird platform on Hedera offers chronological feed unaltered by algorithms
  • Each post includes consensus timestamp and immutable sequence number
  • Consensus layer ensures publicly verifiable, non-revocable chronological feed

Large log records in Dynatrace: limits, native support and best practices

A ticket lands: « the partner call is cut off halfway through in the logs ». You open the record and it simply stops. The payload crossed a limit somewhere.

  • Default log entry body limit is 10 MB for Grail path, 512 kB for Classic pipeline
  • API requests limited to 10 MB, batch over 16 MB after preprocessing results in HTTP 413 error
  • OpenPipeline expands record size limit to 16 MB, 50,000 attributes per log with 32 kB cap

More from Saturday 21 November →