Content pfp
Content
@
0 reply
0 recast
0 reaction

Dan Romero pfp
Dan Romero
@dwr.eth
Introducing Group Direct Casts on Warpcast - Live on mobile and web - Groups can have up to 100 members - You can only invite people following you. If you don’t follow someone, they cannot invite you to a group. You can leave a group at any time - You can also mute a group that’s too noisy
51 replies
79 recasts
275 reactions

Dan Romero pfp
Dan Romero
@dwr.eth
More info: https://warpcast.notion.site/Group-Direct-Casts-42261fa84e8543f2b7cec593d77df094
1 reply
0 recast
3 reactions

Agost Biro pfp
Agost Biro
@agostbiro
"Casts are private and stored securely" -> what does stored securely mean exactly?
1 reply
0 recast
0 reaction

Dan Romero pfp
Dan Romero
@dwr.eth
In our AWS instance. :)
1 reply
0 recast
1 reaction

Agost Biro pfp
Agost Biro
@agostbiro
Could you share more? Who can access the DB? Is it accessible over a public network? Is the DB encrypted at rest? How are backups handled? Is there isolation between production/testing/dev? I care a lot about privacy and turning off E2EE hurt. Would be good to have an answer to these Qs to rebuild trust 🙏
2 replies
0 recast
2 reactions

Cassie Heart pfp
Cassie Heart
@cassie
Encrypted at rest, yes. Turning off E2EE hurt me too, but we’re at the mercy of Google to add PRF support for profile-based passkeys, but they refuse to commit to a timeframe.
1 reply
0 recast
7 reactions

Agost Biro pfp
Agost Biro
@agostbiro
Thanks, I get the reason and I sympathize, but “not E2EE” is a pretty wide spectrum. Encrypted at rest is encouraging, but do I have to assume that everyone at Merkle has access, data leaks into dev environments and the DB is publicly addressable?
1 reply
0 recast
1 reaction

Cassie Heart pfp
Cassie Heart
@cassie
No, things are properly segregated. DBs are not publicly addressable. Access control to cache/DB is also controlled, as well as access to encryption keys.
1 reply
0 recast
4 reactions