to add to this, there’s a few product-y reasons why I would really like a createPost API
1. we could run a server-side language detection model that actually works, so we wouldn’t need the language select in the client (it sucks)
2. you wouldn’t need to specify a createdAt time anymore (cont.)
3. for more casual API users, i.e. people doing integrations, we could do stuff like auto-detecting facets. 1000x better DX
4. we could force people to specify aspect ratios on their images 😈
5. we could check if the post is actually gonna be valid - i.e. throw an error if it would fail a threadgate
lotta product reasons here! it’s so weird from an outside perspective that our GET APIs are nice and normal, and our POST APIs are extremely unergonomic protocol-y jank. creating a post is the core feature of the app and for some reason we’re out here calculating our own TIDs 😵💫
We're working on a writeup that I'm pretty excited about --
Importing your address book to find friends is common for social, but it's insecure to enumeration attacks and database leaks so we've historically refused to implement it. The team has a proposal now that we think solves those risks.
if you don’t read this I’m hiding your reply:
1. IT’S EXTREMELY OPT-IN - bi-directional in fact, so maximally privacy-preserving
2. you don’t have to do it
3. it’s opt in
4. you don’t have to do it
5. you don’t have to tell me you’re not going to do it, I’m not going to do it either
6. see above
Salutations Victorians!
With the upcoming Negotiation and Amendments features for Update 1.12, you might be able to leave Traditionalism behind, for a price!
Join Chris and Victoria to see how you can shape the terms in your favor, but remember the fine print...
Read more here: pdxint.at/4nFVrbQ