Who’s driving this: PEAC is open-source (Apache 2.0), started by a small group of developers who care about web standards, but it’s meant to be community-stewarded from the start. No one “owns” it; anyone can contribute, pilot, or join the working group (GitHub or the form). The real goal is collective evolution.
Business model: There isn’t one. It’s pure OSS, free to use or adapt, no strings or monetization. Just focused on enabling fair consent and attribution for everyone.
On “infrastructure”: Good catch. I meant the application layer (CDNs like Cloudflare, content platforms), not lower networking layers. This is about access and content rules, extending things like robots.txt.
On "X”: X is just one option. GitHub issues, HN, email, or the working group form all work (links in repo/blog).
If you or anyone here has thoughts or critiques, I’d love to hear. How would you design the ideal solution?
jithinraj•6mo ago
Should these rules be set by individual publishers, infrastructure providers, AI companies, open standards, or by community consensus?
What would your ideal solution look like? Who should decide? What’s broken today?
Context:
• Perplexity: https://www.perplexity.ai/hub/blog/agents-or-bots-making-sen...
• Cloudflare: https://blog.cloudflare.com/perplexity-is-using-stealth-unde...