samfundev

Glad to see that they brought in humans to validate and patch vulnerabilities. Although, I really wish they linked to the actual patches. Here's what I could find:

https://cgit.ghostscript.com/cgi-bin/cgit.cgi/ghostpdl.git/c...

https://github.com/OpenSC/OpenSC/pull/3554

https://github.com/dloebl/cgif/pull/84

Coolify does support zero downtime deployments, but the documentation isn't live yet: https://github.com/coollabsio/documentation-coolify/blob/640...

It uses docker stop once the new container is healthy with a 30 second timeout, which I believe lets existing connections drain out.

Coolify does support zero downtime deployments, but the documentation isn't live yet: https://github.com/coollabsio/documentation-coolify/blob/640...

Coolify does support zero downtime deployments, but the documentation isn't live yet: https://github.com/coollabsio/documentation-coolify/blob/640...

While I also worry about lobbying, we'll have to lobby harder.

I have built a few different pieces of software around the idea of pacing. The idea of pacing is that if you can measure the progress of something (i.e. current/goal), you can compare that to the time progress (i.e. elapsed time/total time) to tell you how far ahead or behind you are from completing the goal in time. Basically, you can tell if you are "on pace" with any measurable goal. If you're not on pace, it can tell you how much you need to do to catch up.

I used this to write papers by putting in how many words I needed to write and how many words I had written into a web app that I made for pacing. I made a widget for my watch that shows me if I am on pace with how many steps I want to take every day. And the big one, using it to pace out when I spend time on distracting apps on my phone. If the amount of time I have spent on distracting apps is behind the pace, then I can use the app otherwise it kicks me out.

I'm sure they are more applications I haven't thought of. I haven't made the code public yet, but I could if people are interested.

> The features of LSP are exactly the features of VS Code. So if you create a different editor, it will only support what VS Code does.

This is not true since LSPs can add extensions to the existing API. For example: https://github.com/rust-lang/rust-analyzer/blob/master/docs/...

> If you create an LSP, it will work best in VS Code.

Any editor can work just as well as (or even better than) VS Code.

To clear up some confusion, I believe people are using the terms SSR and hydration interchangeably. Hydration is a new technology that uses SSR and then adds reactivity: https://en.wikipedia.org/wiki/Hydration_(web_development)

The server code will use the framework to handle SSR and hydration. Meaning that all you have to do is write the frontend and you get SSR for free.

A lot of people are talking about the quality of DDG results and I thought I would mention that there is a way to tell DDG about their search results. It's pretty hidden but there is a "Send Feedback" button in the bottom right. They should really make it more visible so that they can get community feedback about what results they need to improve.