You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Instantly share code, notes, and snippets.
👁️
Miles Richardson
Miles Richardson
milesrichardson
👁️
Miles Richardson
founder at @splitgraph, acquired by @EnterpriseDB where I am now Director, Product Management (but I still code sometimes!)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
What you NEED to know before touching a video file
What you NEED to Know Before Touching a Video File
Hanging out in subtitling and video re-editing communities,
I see my fair share of novice video editors and video encoders,
and see plenty of them make the classic beginner mistakes when it comes to working with videos.
A man can only read "Use Handbrake to convert your mkv to an mp4 :)" so many times before losing it,
so I am writing this article to channel the resulting psychic damage into something productive.
If you are new to working with videos (or, let's face it, even if you aren't),
please read through this guide to avoid making mistakes that can cost you lots of time, computing power, storage space, or video quality.
Notes on sandboxing untrusted code - why Python can't be sandboxed, comparing Firecracker/gVisor/WASM approaches
Sandboxing Untrusted Python
Python doesn't have a built-in way to run untrusted code safely. Multiple attempts have been made, but none really succeeded.
Why? Because Python is a highly introspective object-oriented language with a mutable runtime. Core elements of the interpreter can be accessed through the object graph, frames and tracebacks, making runtime isolation difficult.
This means that even aggressive restrictions can be bypassed: