|
|
|
|
|
by dc396
312 days ago
|
|
Yeah, so maybe interesting, but you might want to provide a bit more context/background on who is driving this, business model, and explain when you say "infrastructure", you're talking about content, not actual layer-<everything below application layer> infrastructure. Also "share ideas on X"? No thanks. |
|
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?