Verifiable Credentials, HTTP Next, and the Mitigation of Bots

Credentials Community Group,

Hello. Recently, a news article indicated that: “automated traffic takes up 64% of internet traffic – and whilst just 25% of automated traffic was made up by good bots, such as search engine crawlers and social network bots, 39% of all traffic was from bad bots, a Barracuda report reveals” [1].

I would like to indicate the applicability of verifiable credentials technologies for automated CAPTCHA scenarios (see also: [2]).

Brainstorming, these uses of verifiable credentials could be built into HTTP Next (e.g., HTTP 4.0). Reasons for building these capabilities into HTTP Next include, but are not limited to: (1) human end-users could conveniently, automatically, distinguish themselves from software bots, and (2) human end-users could then be connected with priority servers, receive prioritized traffic routing, and consume more bandwidth over software bots.

Any thoughts on these topics?

Best regards,
Adam Sobieski


Received on Wednesday, 8 September 2021 23:55:34 UTC