A plugin can spawn arbitrary processes so if neovim is not started in a sandbox (container, namespace, firejail...) they can basically do whatever your user has the right to do.

Pretty big supply chain risks here.

And often times sandboxing it is hard.

E.g.: what do you use to edit ~/.ssh/config or ~/.profile?

The devlog videos are great : https://github.com/eduard-permyakov/permafrost-engine#devlog

Thank you so much for making this in the open and documenting everything !

Compiling it yourself from source is quite easy, you can find instruction here: https://www.sqlite.org/howtocompile.html

Here is an article from Julia Evans explaining it: https://jvns.ca/blog/2019/10/28/sqlite-is-really-easy-to-com...

Or if you are familiar with Docker, you can use a more recent Debian in a container and install sqlite inside it.

If you compile it yourself, how do security updates get to your system?

As for a more recent Debian version: The latest stable Debian has sqlite3 3.27.2 in the repos, so that is not an option.

The problem lies in baking entire distribution into an image.

Using distroless images or "FROM scratch" with statically compiled app reduces the risks.

You still have to watch for your app dependencies updates but that's less work than for an entire distribution.

Huh, I didn't know that was possible. So you could specify an app container that is then overlaid atop the OS container?

I suppose installing the dependencies ends up being easier if you know they'll end up in, e.g. a ubuntu 18.04 image, hence that's what people do.

If you want your content to be accessible for most people you also need to transcode your video to several resolutions. This coupled with an adaptive bitrate player [0][1] will allow clients to choose the resolution they can afford (so that people with different bandwidth can access your content)

When dealing with more than 10s or 100s concurrent viewers the required bandwidth on your server will be high and putting a CDN in front may be required.

[0]: https://github.com/Dash-Industry-Forum/dash.js [1]: https://github.com/video-dev/hls.js

> If you want your content to be accessible for most people you also need to transcode your video to several resolutions.

Let's be more concrete. How many people will you lose today from your audience if you just offer 720p? Hard numbers please!

It depends on your market. If you're aiming for people at home in Seoul, yeah that's probably alright. Their connection should be great and stable. If you're aiming at people transiting in Mumbai and watching stuff on their phone in the local train, 720p won't do.

> It depends on your market.

I was referring to (small and medium sized) personal blogs and websites (like the one in this post), i.e. not a digital commodity on a market. If you're out there to make money I realize you have to be more fancy with what you put out there.

I feel that learning from (bad) past choices to build a better solution is a good engineering practice ? Sure the initial db choice didn't scale but they learned from it and they seem to be happy with how they built their new db now

This FFmpeg Python bindings [0] provides wrapper for filter_complex which simplifies its use a lot !

[0]: https://github.com/kkroening/ffmpeg-python

That's actually awesome. Didn't know about this feature but I'll take a look for sure.

It appears to simply apply this CSS to the selected elements:

.___blur-blur { filter: blur(5px); }

We have more precise data about global warming. Sensors are good at measuring temperature or sea rising, less at measuring divorce rates.

Great website ! It's nice to see the different instructions while the animation is running.

I also use http://www.cs.usfca.edu/~galles/visualization/Algorithms.htm... when I want to visualize algorithms.