this post was submitted on 23 Jun 2026
170 points (98.9% liked)

Technology

85683 readers
4669 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 3 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
170
Cloudflare teams up with Chrome, Edge, and Firefox to tackle bot traffic without CAPTCHAs (www.techspot.com)
submitted 1 day ago* (last edited 1 day ago) by FTonsilStones@lemmy.ca to c/technology@lemmy.world
33 comments fedilink hide all child comments
 

Cloudflare is working with the makers of Chrome, Edge, and Firefox on a new way for websites to tell whether incoming traffic is legitimate โ€“ without resorting to the usual mix of CAPTCHAs, logins, and extra tracking.

The system is called Private Access Control Tokens, or PACT, and it arrives at a time when bots have surpassed human traffic online.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] shortwavesurfer@lemmy.zip 2 points 19 hours ago

I think that would depend a lot on the amount of servers serving that service.

If you've only got one server, then the proof of work is going to ramp up quite quickly because of the fact that it can only serve so many requests at a time. If you have 10,000 servers serving the same website, then the proof of work would ramp up pretty slowly because then you can serve a ton more requests at once before needing to kick the proof of work up. Tor currently has a zero proof of work if the service is not under load at all, and then ramps the proof of work up as the service comes under more requests. My thought would be to not have any point where there's a zero proof of work and have a minimum proof of work required of one.