/explore
|
You are here 
|
platformengineering.org | ||
| | | | |
lisilinhart.info
|
|
| | | | | AI's role in coding is set to expand, integrating synthesized code and automated suggestions into the developer's toolkit. While this promises greater accessibility for non-traditional coders, expertise will remain essential. | |
| | | | |
emilymstark.com
|
|
| | | | | In my last blog post, I discussed why people often view the web as a uniquely unsuited platform for implementing end-to-end encryption (E2EE). This view is that the web doesn't offer a long-term trustable notion of what the application is. In that earlier post, I explored the idea of treating the application as untrustworthy and isolating sensitive data from it. In this post, I'm going to pontificate on whether web applications are truly less trustworthy than native applications, especially in an E2EE setting, and if so, how we should bridge the gap. The gap is narrower than it appears at first glance, especially with desktop applications. To close it, though, the devil is in the (UX- and deployment-related) details. | |
| | | | |
www.danritz.com
|
|
| | | | | I want to see how they work. I want to personally explore and critique their potential value. I want to have a "library" of experiments to pull from as I encounter new obstacles. Experiments I can combine or extend from memory without needing time to figure out how to do them in the moment. | |
| | | | |
it-notes.dragas.net
|
|
| | | Using nginx to cache proxied media in snac to improve performance and privacy | ||
