I understand.
In #PrivateDataWG we are trying to come up with clear terms & E2EE is used to describe MLS style messaging.
Private shared data includes an appview as well as PDS & it’s not clear if encrypted-at-rest is possible.
We can discuss in the forum. We can’t do this short form.
In #PrivateDataWG we are trying to come up with clear terms & E2EE is used to describe MLS style messaging.
Private shared data includes an appview as well as PDS & it’s not clear if encrypted-at-rest is possible.
We can discuss in the forum. We can’t do this short form.
October 23, 2025 at 1:35 PM
I understand.
In #PrivateDataWG we are trying to come up with clear terms & E2EE is used to describe MLS style messaging.
Private shared data includes an appview as well as PDS & it’s not clear if encrypted-at-rest is possible.
We can discuss in the forum. We can’t do this short form.
In #PrivateDataWG we are trying to come up with clear terms & E2EE is used to describe MLS style messaging.
Private shared data includes an appview as well as PDS & it’s not clear if encrypted-at-rest is possible.
We can discuss in the forum. We can’t do this short form.
Sounds like a great topic to bring up for the #privatedatawg! Would you be up for starting a thread over on the Discourse forum? discourse.atprotocol.community/c/privatedat...
WG Private Data
The Private Data Working Group is for coordinating and interop for those building various versions of private data on ATProto.
discourse.atprotocol.community
October 13, 2025 at 12:20 AM
Sounds like a great topic to bring up for the #privatedatawg! Would you be up for starting a thread over on the Discourse forum? discourse.atprotocol.community/c/privatedat...
I have several trollish provocations about whether this is a discussion for the #PrivateDataWG. My overall observation is that there's a lot of stuff being built for MCP use cases that look like parallel construction w/ discussions being had about #ATProto. Who should have access to what stuff?
‘We're proposing a new deferred payment scheme for the x402 protocol. This new scheme is specifically designed for agentic payments that don't need immediate settlement and can be handled either through traditional payment methods or stablecoins.’
blog.cloudflare.com/x402/
blog.cloudflare.com/x402/
Launching the x402 Foundation with Coinbase, and support for x402 transactions
Cloudflare is partnering with Coinbase to create the x402 Foundation and adding x402 support to the Agents SDK & MCP Servers.
blog.cloudflare.com
September 23, 2025 at 3:49 PM
I have several trollish provocations about whether this is a discussion for the #PrivateDataWG. My overall observation is that there's a lot of stuff being built for MCP use cases that look like parallel construction w/ discussions being had about #ATProto. Who should have access to what stuff?
We have a #PrivateDataWG that is just kicking off to discuss this discourse.atprotocol.community/c/privatedat...
But, short answer: pick a PDS that has a TOS you agree with, run by an entity you trust.
For at risk users, make backups & keep your own rotation key.
But, short answer: pick a PDS that has a TOS you agree with, run by an entity you trust.
For at risk users, make backups & keep your own rotation key.
September 19, 2025 at 3:10 PM
We have a #PrivateDataWG that is just kicking off to discuss this discourse.atprotocol.community/c/privatedat...
But, short answer: pick a PDS that has a TOS you agree with, run by an entity you trust.
For at risk users, make backups & keep your own rotation key.
But, short answer: pick a PDS that has a TOS you agree with, run by an entity you trust.
For at risk users, make backups & keep your own rotation key.
OK! Set the time for our first #PrivateDataWG to next Thursday, Sept 18th at 8am PST / 12pm EST / 1700 CEST
Please join the forum & the group to get the Zoom link. We'll do intros and discuss goals, discuss Montreal in person and ->
discourse.atprotocol.community/t/private-da...
Please join the forum & the group to get the Zoom link. We'll do intros and discuss goals, discuss Montreal in person and ->
discourse.atprotocol.community/t/private-da...
Private Data WG001: Kick Off Meeting
Let’s do our first synchronous meeting to kick off the working group! We’ll typically take notes and record calls and share them afterwards. Meetings will be scheduled for an hour with “off the recor...
discourse.atprotocol.community
September 11, 2025 at 10:52 PM
OK! Set the time for our first #PrivateDataWG to next Thursday, Sept 18th at 8am PST / 12pm EST / 1700 CEST
Please join the forum & the group to get the Zoom link. We'll do intros and discuss goals, discuss Montreal in person and ->
discourse.atprotocol.community/t/private-da...
Please join the forum & the group to get the Zoom link. We'll do intros and discuss goals, discuss Montreal in person and ->
discourse.atprotocol.community/t/private-da...
Você aí gostaria de colaborar com a discussão sobre como dados privados poderiam ser feitos no ATProto?
Se junte ao Grupo de Trabalho no Discourse linkado no quote!
As comunicações são em inglês, e o grupo tem encontros virtuais para evoluir a discussão.
#PrivateDataWG
🧵 1/3
Se junte ao Grupo de Trabalho no Discourse linkado no quote!
As comunicações são em inglês, e o grupo tem encontros virtuais para evoluir a discussão.
#PrivateDataWG
🧵 1/3
OK! Today's the day! Kicking off the home for the #PrivateDataWG in the new @atprotocol.dev hosted Discourse forum
Thanks to @ngerakines.me for spinning up the infra, including login with ATProto powered by AIP
If you're interested in Private Data, login and introduce yourself.
Thanks to @ngerakines.me for spinning up the infra, including login with ATProto powered by AIP
If you're interested in Private Data, login and introduce yourself.
Introductions and kick off
Hello! It’s time to kick off the Private Data Working Group! The goal of this group is to coordinate on implementations, documentation, interop of private data solutions for AT Proto. This may be off...
discourse.atprotocol.community
September 5, 2025 at 12:38 PM
Você aí gostaria de colaborar com a discussão sobre como dados privados poderiam ser feitos no ATProto?
Se junte ao Grupo de Trabalho no Discourse linkado no quote!
As comunicações são em inglês, e o grupo tem encontros virtuais para evoluir a discussão.
#PrivateDataWG
🧵 1/3
Se junte ao Grupo de Trabalho no Discourse linkado no quote!
As comunicações são em inglês, e o grupo tem encontros virtuais para evoluir a discussão.
#PrivateDataWG
🧵 1/3
A thread on the Private Data Working Group that is kicking off #PrivateDataWG
It’s also one of the first discussions happening in the new ATProto Community Discourse forum - including login with your ATProto account.
It’s also one of the first discussions happening in the new ATProto Community Discourse forum - including login with your ATProto account.
OK! Today's the day! Kicking off the home for the #PrivateDataWG in the new @atprotocol.dev hosted Discourse forum
Thanks to @ngerakines.me for spinning up the infra, including login with ATProto powered by AIP
If you're interested in Private Data, login and introduce yourself.
Thanks to @ngerakines.me for spinning up the infra, including login with ATProto powered by AIP
If you're interested in Private Data, login and introduce yourself.
Introductions and kick off
Hello! It’s time to kick off the Private Data Working Group! The goal of this group is to coordinate on implementations, documentation, interop of private data solutions for AT Proto. This may be off...
discourse.atprotocol.community
September 4, 2025 at 11:55 PM
A thread on the Private Data Working Group that is kicking off #PrivateDataWG
It’s also one of the first discussions happening in the new ATProto Community Discourse forum - including login with your ATProto account.
It’s also one of the first discussions happening in the new ATProto Community Discourse forum - including login with your ATProto account.
Excited to see #PrivateDataWG kick off today! 🎉
September 4, 2025 at 11:13 PM
Excited to see #PrivateDataWG kick off today! 🎉
What is Private Data? is itself a thing that needs definition! I've made a wiki page in the group that is a synthesis of discussions discourse.atprotocol.community/t/what-is-pr...
How wrong is this? Let's discuss!
#PrivateDataWG
How wrong is this? Let's discuss!
#PrivateDataWG
September 4, 2025 at 10:52 PM
What is Private Data? is itself a thing that needs definition! I've made a wiki page in the group that is a synthesis of discussions discourse.atprotocol.community/t/what-is-pr...
How wrong is this? Let's discuss!
#PrivateDataWG
How wrong is this? Let's discuss!
#PrivateDataWG
OK! Today's the day! Kicking off the home for the #PrivateDataWG in the new @atprotocol.dev hosted Discourse forum
Thanks to @ngerakines.me for spinning up the infra, including login with ATProto powered by AIP
If you're interested in Private Data, login and introduce yourself.
Thanks to @ngerakines.me for spinning up the infra, including login with ATProto powered by AIP
If you're interested in Private Data, login and introduce yourself.
Introductions and kick off
Hello! It’s time to kick off the Private Data Working Group! The goal of this group is to coordinate on implementations, documentation, interop of private data solutions for AT Proto. This may be off...
discourse.atprotocol.community
September 4, 2025 at 10:52 PM
OK! Today's the day! Kicking off the home for the #PrivateDataWG in the new @atprotocol.dev hosted Discourse forum
Thanks to @ngerakines.me for spinning up the infra, including login with ATProto powered by AIP
If you're interested in Private Data, login and introduce yourself.
Thanks to @ngerakines.me for spinning up the infra, including login with ATProto powered by AIP
If you're interested in Private Data, login and introduce yourself.
@dholms.xyz's post requesting a BOF is here.
The IETF tickets are pricey, but the hackathon day is open to all, and we'll be looking at outside-the-IETF gathers on particular topics.
#PrivateDataWG is one of the likely things to discuss.
Contribute on the wiki for other topics.
The IETF tickets are pricey, but the hackathon day is open to all, and we'll be looking at outside-the-IETF gathers on particular topics.
#PrivateDataWG is one of the likely things to discuss.
Contribute on the wiki for other topics.
August 29, 2025 at 10:24 PM
@dholms.xyz's post requesting a BOF is here.
The IETF tickets are pricey, but the hackathon day is open to all, and we'll be looking at outside-the-IETF gathers on particular topics.
#PrivateDataWG is one of the likely things to discuss.
Contribute on the wiki for other topics.
The IETF tickets are pricey, but the hackathon day is open to all, and we'll be looking at outside-the-IETF gathers on particular topics.
#PrivateDataWG is one of the likely things to discuss.
Contribute on the wiki for other topics.
Aside from coding and testing different #PrivateDataWG implementations - the thing you can do today is read the linked RFC.
Protocol work is reading & critiquing specs and use cases.
@davenash.com maybe we start a “comment on this issue to prove you’ve read the RFC”?
Protocol work is reading & critiquing specs and use cases.
@davenash.com maybe we start a “comment on this issue to prove you’ve read the RFC”?
I gotta write up notes and set a kick off date/time for #PrivateDataWG
In the meantime - go read @davenash.com’s RFC and leave a comment or make a PR github.com/knasher/rfcs...
In the meantime - go read @davenash.com’s RFC and leave a comment or make a PR github.com/knasher/rfcs...
August 29, 2025 at 3:41 AM
Aside from coding and testing different #PrivateDataWG implementations - the thing you can do today is read the linked RFC.
Protocol work is reading & critiquing specs and use cases.
@davenash.com maybe we start a “comment on this issue to prove you’ve read the RFC”?
Protocol work is reading & critiquing specs and use cases.
@davenash.com maybe we start a “comment on this issue to prove you’ve read the RFC”?
I gotta write up notes and set a kick off date/time for #PrivateDataWG
In the meantime - go read @davenash.com’s RFC and leave a comment or make a PR github.com/knasher/rfcs...
In the meantime - go read @davenash.com’s RFC and leave a comment or make a PR github.com/knasher/rfcs...
August 29, 2025 at 3:24 AM
I gotta write up notes and set a kick off date/time for #PrivateDataWG
In the meantime - go read @davenash.com’s RFC and leave a comment or make a PR github.com/knasher/rfcs...
In the meantime - go read @davenash.com’s RFC and leave a comment or make a PR github.com/knasher/rfcs...
Only germ is “private” and it’s out of protocol as part of prototyping how MLS + ATProto will work.
Anisota only is still on the protocol in the open.
But yes, people want #PrivateDataWG ;)
Anisota only is still on the protocol in the open.
But yes, people want #PrivateDataWG ;)
August 24, 2025 at 7:17 PM
Only germ is “private” and it’s out of protocol as part of prototyping how MLS + ATProto will work.
Anisota only is still on the protocol in the open.
But yes, people want #PrivateDataWG ;)
Anisota only is still on the protocol in the open.
But yes, people want #PrivateDataWG ;)
P.P.P.S. @bnewbold.net let me know that he has made the time to come join us, so I expect a lot of OAuth Scopes talk...
...and maybe a real start to #PrivateDataWG????
...and maybe a real start to #PrivateDataWG????
August 14, 2025 at 10:13 PM
P.P.P.S. @bnewbold.net let me know that he has made the time to come join us, so I expect a lot of OAuth Scopes talk...
...and maybe a real start to #PrivateDataWG????
...and maybe a real start to #PrivateDataWG????
The working theory / requirements is that encrypted data on the public relay is not a good pattern (I agree)
And that encrypted data for groups won’t scale to 50K - 100K users (Signal maxes at 10K for reference)
More classic server protected by auth scales to that size no problem. #PrivateDataWG
And that encrypted data for groups won’t scale to 50K - 100K users (Signal maxes at 10K for reference)
More classic server protected by auth scales to that size no problem. #PrivateDataWG
August 11, 2025 at 3:54 AM
The working theory / requirements is that encrypted data on the public relay is not a good pattern (I agree)
And that encrypted data for groups won’t scale to 50K - 100K users (Signal maxes at 10K for reference)
More classic server protected by auth scales to that size no problem. #PrivateDataWG
And that encrypted data for groups won’t scale to 50K - 100K users (Signal maxes at 10K for reference)
More classic server protected by auth scales to that size no problem. #PrivateDataWG
Oh and making things work both in a web browser and on native apps, securely.
I actually have full confidence in the E2EE work.
The #PrivateDataWG doesn’t even have consensus on requirements.
If I had to guess … I don’t think it will end up encrypted: it will be privately transferred from PDS.
I actually have full confidence in the E2EE work.
The #PrivateDataWG doesn’t even have consensus on requirements.
If I had to guess … I don’t think it will end up encrypted: it will be privately transferred from PDS.
July 9, 2025 at 11:50 PM
Oh and making things work both in a web browser and on native apps, securely.
I actually have full confidence in the E2EE work.
The #PrivateDataWG doesn’t even have consensus on requirements.
If I had to guess … I don’t think it will end up encrypted: it will be privately transferred from PDS.
I actually have full confidence in the E2EE work.
The #PrivateDataWG doesn’t even have consensus on requirements.
If I had to guess … I don’t think it will end up encrypted: it will be privately transferred from PDS.
In this case, ATProto Wiki doesn't need more chat, it needs wikis and threads and ATProto logins.
Various other bits of ATProto community should definitely consider Roomy! Maybe for #PrivateDataWG?
Various other bits of ATProto community should definitely consider Roomy! Maybe for #PrivateDataWG?
July 7, 2025 at 6:29 PM
In this case, ATProto Wiki doesn't need more chat, it needs wikis and threads and ATProto logins.
Various other bits of ATProto community should definitely consider Roomy! Maybe for #PrivateDataWG?
Various other bits of ATProto community should definitely consider Roomy! Maybe for #PrivateDataWG?
There's no "they", it's us!
We'll need to kick off a #PrivateDataWG and get a set of committed, funded people & orgs to work together on getting this done.
Bsky team doesn't even have time to start on this for 6+ months AFAIK.
We'll need to kick off a #PrivateDataWG and get a set of committed, funded people & orgs to work together on getting this done.
Bsky team doesn't even have time to start on this for 6+ months AFAIK.
July 7, 2025 at 6:20 PM
There's no "they", it's us!
We'll need to kick off a #PrivateDataWG and get a set of committed, funded people & orgs to work together on getting this done.
Bsky team doesn't even have time to start on this for 6+ months AFAIK.
We'll need to kick off a #PrivateDataWG and get a set of committed, funded people & orgs to work together on getting this done.
Bsky team doesn't even have time to start on this for 6+ months AFAIK.
They are! We will do many of these things!
Everyone wants #E2EEWG and it’s rolling nicely with multiple folks. no one has seriously started #PrivateDataWG which is next.
Start your engines, it’s #HotATProtoPrivateSummer
I’m sorry / you’re welcome @tessa.germnetwork.com
Everyone wants #E2EEWG and it’s rolling nicely with multiple folks. no one has seriously started #PrivateDataWG which is next.
Start your engines, it’s #HotATProtoPrivateSummer
I’m sorry / you’re welcome @tessa.germnetwork.com
July 3, 2025 at 7:55 PM
They are! We will do many of these things!
Everyone wants #E2EEWG and it’s rolling nicely with multiple folks. no one has seriously started #PrivateDataWG which is next.
Start your engines, it’s #HotATProtoPrivateSummer
I’m sorry / you’re welcome @tessa.germnetwork.com
Everyone wants #E2EEWG and it’s rolling nicely with multiple folks. no one has seriously started #PrivateDataWG which is next.
Start your engines, it’s #HotATProtoPrivateSummer
I’m sorry / you’re welcome @tessa.germnetwork.com
Feels like preferences is less critical low hanging fruit.
Also, yes, I agree: we need to experiment and learn.
My big question is if the Bluesky team is open to running #PrivateDataWG as an actual working group.
Without that, can’t really help or make progress on final architecture.
Also, yes, I agree: we need to experiment and learn.
My big question is if the Bluesky team is open to running #PrivateDataWG as an actual working group.
Without that, can’t really help or make progress on final architecture.
May 11, 2025 at 10:24 PM
Feels like preferences is less critical low hanging fruit.
Also, yes, I agree: we need to experiment and learn.
My big question is if the Bluesky team is open to running #PrivateDataWG as an actual working group.
Without that, can’t really help or make progress on final architecture.
Also, yes, I agree: we need to experiment and learn.
My big question is if the Bluesky team is open to running #PrivateDataWG as an actual working group.
Without that, can’t really help or make progress on final architecture.
Forward Email has a new technical whitepaper forwardemail.net/technical-wh...
Of interest "unique approach to email storage using individually encrypted SQLite mailboxes with optimized PRAGMA settings"
Yes, this might be relevant to future ATProto #PrivateDataWG
Of interest "unique approach to email storage using individually encrypted SQLite mailboxes with optimized PRAGMA settings"
Yes, this might be relevant to future ATProto #PrivateDataWG
May 6, 2025 at 7:13 AM
Forward Email has a new technical whitepaper forwardemail.net/technical-wh...
Of interest "unique approach to email storage using individually encrypted SQLite mailboxes with optimized PRAGMA settings"
Yes, this might be relevant to future ATProto #PrivateDataWG
Of interest "unique approach to email storage using individually encrypted SQLite mailboxes with optimized PRAGMA settings"
Yes, this might be relevant to future ATProto #PrivateDataWG