Explore >> Select a destination
|
You are here 
|
blog.soykaf.com | ||
| | | | |
akkoma.dev
|
|
| | | | | akkoma - Magically expressive social media | |
| | | | |
evanp.me
|
|
| | | | | One important pattern in social networking is end-to-end encryption for direct messages. This is a structure in which the native or Web clients encrypt the message on the user's device, and no intermediate actor -- neither user's servers, nor any network node -- can read the message. This wasn't a big part of our planning... | |
| | | | |
flak.tedunangst.com
|
|
| | | | | ||
| | | | |
nguyenhuythanh.com
|
|
| | | Overview Generally, there are two ways of web rendering: the first is SSR, stands for Server-Side Rendering; the second is CSR, stands for Client-Side Rendering. Both come with different trade-offs. Someone has compared that to a cycle, where we first started with SSR, then moved to CSR/SPA as the client-side application state became complex. Because CSR has its problems, we (re)discovered SSR 1 with HTMX, or even NextJS SSR. There were many writing about issues of CSR and SPA 2 3, but I would summarize them essentially as a state synchronization problem between the client and the server that results in complexity 4. | ||
