#h265 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #h265, aggregated by home.social.
-
Review of Rikomagic DS08 Android 13 digital signage player
-
Почему одинаковая надпись H.264 или H.265 на IP-камерах не делает их одинаковыми
На рынке видеонаблюдения есть удивительно живучий миф: если на двух IP-камерах написано H.264 или H.265, значит, и вести себя они должны примерно одинаково. Нагрузка на сеть будет похожей, архив займет сопоставимый объем, сервер разницы не заметит, а совместимость окажется чем-то само собой разумеющимся. Разберем, почему одинаковая надпись H.264 или H.265 не делает IP-камеры одинаковыми, какие параметры действительно влияют на поведение потока и на что стоит смотреть при выборе, тестировании и модернизации системы.
https://habr.com/ru/articles/1020930/
#видеонаблюдение #видео #видеоаналитика #vms #видеоархив #сетевые_технологии #h264 #h265 #кодеки #система_видеонаблюдения
-
Irgendwie hat die Jellyfin-App auf der Streambar von Roku seit einiger Zeit Probleme HEVC (H265) abzuspielen.
Abspielen klappt schon, allerdings kommt es zu sehr nervigen Unterbrechungen weil dauernd gebuffert wird.
Die Bitrate der Dateien ist nicht so außergewöhnlich verglichen mit denen, die problemlos abgespielt werden können.
... alle H265 Dateien nochmal zu konvertieren und durch H264 auszutauschen... Darauf habe ich keine Lust -.-
In Findroid auf dem Smartphone funktionieren einige (aber nicht alle) H265-Dateien ohne andauerndes Gebuffer.
Mal schauen, wie viele H265-Dateien ich überhaupt habe. War mein Standard-Codec für eine gewisse Zeit, bis ich wieder H264 mit Nvenc enkodiert habe.
-
Comment on this video (which us not shown on my Fedi instance, yay federation!)
https://tube.kockatoo.org/w/63cGWTvhzqu2bwMGsh3QcF
I cannot believe that that GPU is not usable for video work. That is what GPUs are made for!
Poorly, there are a few caveats:
- there are always more DEcoders supported than ENcoders. I guess not being able to play a video (it would play but be less efficiently decoded on the CPU) is worse than being bound to #h265 instead of #av1 for recording.
- thus it makes sense that GPUs generally work flawlessly for gaming, as that is just displaying videos (or rendering content, which is kinda different, no idea why video codecs are more difficult than rendering methods)
- for every video format out there exists an encoder. If you use software rendering (on the CPU), you can use ANYTHING. Like encode to modern (and free!) AV1 using #svtav1 on any old CPU.
- if you want to encode videos on a GPU, you need drivers, but also a different encoder. On #NVIDIA you use #NVENC (NVidia ENCoder), for example nvenc_x265 for h265/HEVC videos. On #IntelArc (and afaik AMD GPUs), you use the #QSV (quick sync video) library which builds on top of #VAAPI, which is open source. So you can encode to AV1 using qsv_av1 for example.What encoders are supported depends on the GPU a lot. Intel Arc seems to have supported the free, efficient and future-proof AV1 codec the earliest, but also the older free codecs VP9 and VP8 (also used in webm), like in a GPU I recently bought used. My older NVIDIA GPU only supports H265, which is proprietary and often less efficient than AV1 (not always, video codecs are black magic).
As OBS can use your GPU for video capture (encoding), the issue is purely in software support.
I only have experience with #ffmpeg for re-encoding videos, but that is also in many video editing tools. Try if you can get them somehow.
For NVIDIA I needed the latest proprietary drivers (#NixOS makes this extremely easy, can recommend) and ffmpeg, nvenc worked out of the box.
For intel Arc I used the regular drivers included in the kernel, but after adding the QSV runtime to my "hardware.graphics.extraPackages" I needed to recompile the entire kernel. Using a #longterm kernel (currently 6.18) makes this more viable... longterm XD.
-
M5Stack AI-8850 LLM Accelerator M.2 Kit offers an alternative to Raspberry Pi AI HAT+ 2
-
MUSE Book laptop review – Testing an octa-core RISC-V Linux laptop in 2026
-
VisionFive 2 Lite SBC Review – Ubuntu 24.04 on a low-cost RISC-V SBC in 2026
-
Видеокодек AV2 готов. Почему нам важны открытые стандарты
Новые видеокодеки моментально улучшают жизнь миллионов людей. Тем не нужно прикладывать практически никаких усилий, разве что обновить железо или софт. После этого видеофайлы магически уменьшаются в размере, качество картинки становится лучше, видео в интернете перестаёт тормозить и т. д. Например, новый видеокодек AV2 уменьшает трафик на 30%. Единственный недостаток — скорость кодирования многократно возрастает, потому что используются сложные интеллектуальные технологии (например, психофизические модели зрения и мозга, новые способы предсказания будущего (межкадровых изменений) по предыдущим кадрам, последние открытия в математике (вроде треллис-квантования ). Появляется ощущение некоего волшебства. Вообще, эффективное сжатие напрямую связано с пониманием данных, то есть с уровнем интеллекта. Чем глубже понимание смысла, тем больше мы видим аналогий, паттернов, циклов и рекурсий, которые можно использовать для «упаковки» информации. Как говорится, достаточно продвинутая технология неотличима от магии. Так и видеокодеки нового поколения — это настоящая программная магия.
https://habr.com/ru/companies/ruvds/articles/970584/
#av2 #av1 #hevc #h265 #сжатие_данных #AOMedia #avm #psnr #ssim #ruvds_статьи
-
Well .. it takes quite a bit longer to encode #h265 than I was expecting. Still crazy to me that CPU encoding is still superior to GPU encoding.
-
В последнее время стал жать видео в AV1 через #ffmpeg и #HandBrake. Из трёх кодировщиков: libsvtav1, libaom-av1 и librav1e стабильно работает первый, хорошо и эффективнее жмёт маленькие видео по сравнению с распространённым H265, но пытаюсь ужать видео в 2,2 ГБ и размер его только увеличивается 🙄
Обратился к интернету и вот результатыСравнение libsvtav1 и libaom-av1: ключевые различия
libaom-av1 — это эталонный кодировщик AV1, разработанный Альянсом открытых медиа (AOMedia), в основном при участии Google. Он ориентирован на достижение максимального качества и сжатия, часто используется как точка отсчёта при сравнении других кодировщиков. В то время как SVT-AV1 (libsvtav1) — это проект, созданный Intel и Netflix, с акцентом на высокую скорость и масштабируемость, особенно в многопоточных средах.
SVT-AV1 разработан для практических применений, включая трансляции и массовое перекодирование, где важна производительность.
Ниже приведено детальное сравнение двух кодировщиков по ключевым параметрам.Качество и эффективность сжатия
libaom-av1 традиционно считается лидером по качеству, особенно на медленных пресетах (например, cpu-used=2). В тестах с метриками вроде VMAF он может давать чуть лучшее качество при одинаковом битрейте, особенно на сложных сценах и статике. Это делает его предпочтительным для архивного перекодирования или когда качество важнее времени.
SVT-AV1 немного уступает в пиковой эффективности, но разница минимальна — «на волосок». При этом он предлагает гораздо более предсказуемое и стабильное качество на пресетах средней и высокой скорости. Благодаря оптимизациям, он эффективен даже при низких битрейтах, что важно для стриминга.
Скорость и производительность
SVT-AV1 значительно превосходит libaom-av1 по скорости кодирования, особенно на современных CPU. Например, тесты на Snapdragon 680 показали, что SVT-AV1 работает в 2–3 раза быстрее при сопоставимом качестве. Это достигается за счёт отказа от некоторых сложных функций AV1 и использования эффективной многопоточной архитектуры на основе тайлов и строк.
libaom-av1, напротив, известен своей медлительностью, особенно в однопоточном режиме. Его многопоточность слабо оптимизирована, что делает его менее пригодным для массового использования.
Применение и экосистема
libaom-av1 — идеален для задач, где важна максимальная эффективность сжатия, а время кодирования не критично (например, перекодирование фильмов).
SVT-AV1 — выбор для live-стриминга, медиасерверов (например, Nimble Streamer), облачных транскодеров и любых сценариев, где важна масштабируемость и скорость.
ВЫВОД
Выбирайте libaom-av1, если вам нужно максимальное качество и вы готовы ждать.
Выбирайте SVT-AV1, если важна скорость, масштабируемость и производительность в реальных условиях.
SVT-AV1 считается более «практичным» кодировщиком будущего, тогда как libaom-av1 остаётся «золотым стандартом» для измерения качества.
-
So I have hundreds of videos of ~1 minute recorded from my phone ~10 years ago, and they generally don’t have that great compression, nor they are stored in a modern and advanced video format.
For archiving purposes, I want to take advantage of my workstation’s mighty GPU to process them so that the quality is approximately the same, but the file size would be strongly reduced.
Nevertheless, compressing videos is terribly hard, and way more complex than compressing pictures, so I wouldn’t really know how to do this, what format to use, what codec, what bitrate, what parameters to keep an eye on, etc.
I don’t care if the compression takes a lot of time, I just want smaller but good looking videos.
Any tips? (Links to guides and tutorials are ok too)
Also, unfortunately I am forced to use Windows for this (don’t ask me why 🫠), but I know nothing about Windows because I hate it. Practical software suggestions are very much welcome, too!
#ffmpeg #help #askFedi #codec #AVI #H265 #H264 #movie #video #videoCompression #compression #encoding #HandBrake #heif #heic #avif #mp4 #mkv #Wondows
-
So I have hundreds of videos of ~1 minute recorded from my phone ~10 years ago, and they generally don’t have that great compression, nor they are stored in a modern and advanced video format.
For archiving purposes, I want to take advantage of my workstation’s mighty GPU to process them so that the quality is approximately the same, but the file size would be strongly reduced.
Nevertheless, compressing videos is terribly hard, and way more complex than compressing pictures, so I wouldn’t really know how to do this, what format to use, what codec, what bitrate, what parameters to keep an eye on, etc.
I don’t care if the compression takes a lot of time, I just want smaller but good looking videos.
Any tips? (Links to guides and tutorials are ok too)
Also, unfortunately I am forced to use Windows for this (don’t ask me why 🫠), but I know nothing about Windows because I hate it. Practical software suggestions are very much welcome, too!
#ffmpeg #help #askFedi #codec #AVI #H265 #H264 #movie #video #videoCompression #compression #encoding #HandBrake #heif #heic #avif #mp4 #mkv #Wondows
-
So I have hundreds of videos of ~1 minute recorded from my phone ~10 years ago, and they generally don’t have that great compression, nor they are stored in a modern and advanced video format.
For archiving purposes, I want to take advantage of my workstation’s mighty GPU to process them so that the quality is approximately the same, but the file size would be strongly reduced.
Nevertheless, compressing videos is terribly hard, and way more complex than compressing pictures, so I wouldn’t really know how to do this, what format to use, what codec, what bitrate, what parameters to keep an eye on, etc.
I don’t care if the compression takes a lot of time, I just want smaller but good looking videos.
Any tips? (Links to guides and tutorials are ok too)
Also, unfortunately I am forced to use Windows for this (don’t ask me why 🫠), but I know nothing about Windows because I hate it. Practical software suggestions are very much welcome, too!
#ffmpeg #help #askFedi #codec #AVI #H265 #H264 #movie #video #videoCompression #compression #encoding #HandBrake #heif #heic #avif #mp4 #mkv #Wondows
-
So I have hundreds of videos of ~1 minute recorded from my phone ~10 years ago, and they generally don’t have that great compression, nor they are stored in a modern and advanced video format.
For archiving purposes, I want to take advantage of my workstation’s mighty GPU to process them so that the quality is approximately the same, but the file size would be strongly reduced.
Nevertheless, compressing videos is terribly hard, and way more complex than compressing pictures, so I wouldn’t really know how to do this, what format to use, what codec, what bitrate, what parameters to keep an eye on, etc.
I don’t care if the compression takes a lot of time, I just want smaller but good looking videos.
Any tips? (Links to guides and tutorials are ok too)
Also, unfortunately I am forced to use Windows for this (don’t ask me why 🫠), but I know nothing about Windows because I hate it. Practical software suggestions are very much welcome, too!
#ffmpeg #help #askFedi #codec #AVI #H265 #H264 #movie #video #videoCompression #compression #encoding #HandBrake #heif #heic #avif #mp4 #mkv #Wondows
-
So I have hundreds of videos of ~1 minute recorded from my phone ~10 years ago, and they generally don’t have that great compression, nor they are stored in a modern and advanced video format.
For archiving purposes, I want to take advantage of my workstation’s mighty GPU to process them so that the quality is approximately the same, but the file size would be strongly reduced.
Nevertheless, compressing videos is terribly hard, and way more complex than compressing pictures, so I wouldn’t really know how to do this, what format to use, what codec, what bitrate, what parameters to keep an eye on, etc.
I don’t care if the compression takes a lot of time, I just want smaller but good looking videos.
Any tips? (Links to guides and tutorials are ok too)
Also, unfortunately I am forced to use Windows for this (don’t ask me why 🫠), but I know nothing about Windows because I hate it. Practical software suggestions are very much welcome, too!
#ffmpeg #help #askFedi #codec #AVI #H265 #H264 #movie #video #videoCompression #compression #encoding #HandBrake #heif #heic #avif #mp4 #mkv #Wondows
-
I'm trying to figure out the licensing around h264 and HEVC for a Godot plugin.
For h264, there seems to be OpenH264 on the software decode side, for which if using the binaries, Cisco is paying for the license and given the implementation freely to use. Great!
But what about HW decoders? If I'm selling software that is run on commercial software that's run on users computers that have HW decoders... is the onus on the game dev or HW manufacturer?
-
1/3
Just completed a #Transcode of around 30 minutes of .webm vid+aud into h.265 (aka #HEVC).Took 8 hours.
And the computer's fan did a lot of whirring.
Getting a format that the TV wil play without #Transcoding seems necessary.
-
Jetzt musste ich doch tatsächlich #h265 nachinstallieren bei #Fedora 🙈
#Rpmfusion ließ sich aber relativ einfach installieren. Und danach die passenden GStreamer Pakete im Softwarecenter.
-
Fire TV Stick 4K und 4K Max kehren nach Patentstreit nach Deutschland zurück
Nach Monaten der Abwesenheit sind die beliebten Fire TV Stick 4K und Fire TV Stick 4K Max endlich wieder regulär in Deutschland erhältlich. Grund hierfür ist eine Einigung
https://www.apfeltalk.de/magazin/news/fire-tv-stick-4k-und-4k-max-kehren-nach-patentstreit-nach-deutschland-zurueck/
#News #Zubehr #4KStreaming #Amazon #FireTVCube #FireTVStick4K #FireTVStick4KMax #H265 #Nokia #Patentstreit #Videokompression -
🎮** How to easily transcode a video to the desired size: an honest review of simple programs for Windows 10**
🔧** Task**
Sometimes you need to compress a video **up to a strictly defined file size**, For example:
**700 MB** for CD**1.4 GB** for DVD
**100 MB** to upload to messenger
It is important:
**Don't change video length**
**Don't understand complex parameters** codecs and bitratesJust specify the size you need and get the result
🔬** Criteria for selecting programs**
The following criteria were used to find suitable tools:
**Criterion**
**Required?**
Specifying the exact target file size
✅ Yes
Simple interface without unnecessary settings
✅ Yes
Support for modern video formats
✅ Yes
Does not require technical knowledge
✅ Yes
Relevance and absence of hidden restrictions
✅ Yes
Ability to save templates
🔸 Preferable🎯** Final candidates**
After testing various utilities, the list of finalists included: **three programs**, which actually allow you to compress video to a given size **without complicated settings**.
**Program**
**Main purpose**
**Size indication**
**Interface**
**Templates**
**Comment**
**VidCoder**
Universal video converter
✅ Yes
Very simple
✅ Yes
The best balance of simplicity and control
**Simple x264/x265 Launcher**
Compress to size utility
✅ Yes
A minimalist
✅ Yes
Requires separate ffmpeg/x264
**AutoFF**
The simplest FFmpeg shell
✅ Yes
Very simple
❌ No
Minimal functionality, no flexibility🏆** Winner - VidCoder**
✅** Why VidCoder:**
**Direct file size input** (for example, 700 MB - the program will calculate the parameters itself).**Simple and convenient interface**, understandable even to a beginner.
**Support for modern codecs** (x264, x265) without having to download them manually.
**There are profiles and templates** to quickly select settings.
**You can compress multiple videos at once** (working with a file queue).
**Does not require special knowledge**.
🚫** Cons:**
The first acquaintance may seem a little confusing, but after a couple of clicks everything is intuitive.If your computer is weak, encoding may take longer.
📥**Where to download?**
👉 **Official website:** https://vidcoder.net/💪** Alternatives**
🥈** Simple x264/x265 Launcher**
✅ **Pros:**
Minimal interface, nothing extra.Supports setting the file size directly.
Lightweight, not overloaded with functions.
⚠️ **Cons:**
Requires separate download **FFmpeg/x264** and manual path settings.The interface is a bit "technical".
**Verdict:** Suitable for those who are not afraid of minimal manual setup.
🥉** AutoFF**
✅ **Pros:**
Minimum steps: select a file, enter the size, click “Start”.Does not require additional dependencies.
⚠️ **Cons:**
There are no templates, queues, or codec selection.The interface is outdated.
The project is practically abandoned.
**Verdict:** Only for those who need the most primitive conversion method.
📄** Summary**
If needed **the simplest, most understandable and flexible option**, That **VidCoder** is the best choice. It combines **convenience, support for modern formats and the ability to compress video to a given size**.
👉 **Download VidCoder**: https://vidcoder.net/
❓ **Need step-by-step instructions with pictures?** Write and we’ll add it!**Video Compression: Finding the Right Tool for the Job**
**Hashtags**: #VideoCompression #H265 #VideoEditing #ShutterEncoder #VideoEncoding #TechTools #VideoEditingSoftware
**Bibliography & Educational Resources**:
**Video Compression Fundamentals**
This resource provides a comprehensive guide to video compression, including different formats and their applications in video production.
Video Compression Handbook – Wiley Online Library
**Understanding H.265 Codec**
An in-depth look at the H.265 (HEVC) codec, including its advantages, challenges, and applications in modern video editing.
HEVC: High-Efficiency Video Coding
**Shutter Encoder Official Documentation**
A full user guide for Shutter Encoder, detailing how to utilize the tool effectively for video compression and encoding with hardware acceleration.
Shutter Encoder Documentation
**Video Editing Software Comparison**
A comparative analysis of video editing and compression software available on the market, covering pros and cons.
TechRadar: Best Video Editing Software
**Editorial Postscript**:
The quest for the perfect video compression tool was far from simple. In our search, we prioritized **efficiency, simplicity, and speed**, hoping to balance performance with the ease of use for non-experts. After evaluating several tools, we found that **Shutter Encoder** proved to be the most effective for our needs. However, as with all tools, it does come with its own set of challenges. While it delivers impressive results with hardware acceleration, it lacks pre-set templates for exact file sizes, which may be a dealbreaker for some users.
**Upcoming Second Article: Test Results and Practical Insights**
In the upcoming second article, we will dive deeper into the results of our **Shutter Encoder** tests, comparing the output quality and compression efficiency across various formats such as **H.265**. We'll analyze the practicality of the tool, focusing on real-world use cases, performance metrics, and system requirements. Stay tuned as we explore further insights and provide a final recommendation based on practical testing and actual results.🎮 How to easily transcode a video to the desired size | An honest review of simple programs for Windows 10
https://lenovotcore.blogspot.com/2025/03/how-to-easily-transcode-video-to.html -
Have you ever wanted an exhaustive investigation of quality/speed tradeoffs when encoding #H265 with #FFMPEG?
https://scottstuff.net/posts/2025/03/17/benchmarking-ffmpeg-h265/
A few surprising results after running around 1,200 tests:
- 10-bit encoding can produce substantially *smaller* files than 8-bit encoding.
- Chroma subsampling (4:2:2 and 4:2:0) will sometimes be bigger than a 4:4:4 file.
- You should *absolutely* use `-tune uhq` if you're using nVidia's hardware encoder.
- But you probably shouldn't use nVidia's hardware encoder. -
@noondlyt I think it might be a picture format based on H.265 or H.264, but am not sure it is.
#h264 #h265 #PictureFormat #FilesTypes #PictureFiles -
Handling #HECV/ #H265 #video files under #linux is pain in the ass.
Had to convert them to #H264 to be able to handle them appropriatly. That took ages not only because of the fact that this is a lot of encoding but also because the tool (#handbrake gui) I used crashed plenty of time. Using HandBrake-CLI seems to work much better and stable.
-
So, first results. I'm running a CRF of 24 and a general preset for the SVT-AV1 encoder of 4 or 5 (basically using 4 for the tough videos). Right now:
- Simple animated content: 5.6GB source, 313MB for H265 transcode, 212MB for the AV1 transcode.
- More dirty/complex animated content: 4.3GB source, 1.8GB for H265 transcode, 671MB for the AV1 transcode.I'm averaging about 1.2x to 1.3x on preset 4 which means I can go a bit further on the presets which should be fine though I don't imaging I'll go past a preset of 3. However, I'm liking the results so far. #av1 #h265 #encoding
-
Verkaufsstopp für Fire TV Stick 4K in Deutschland
Amazon hat den Verkauf der Fire TV Stick 4K und Fire TV Stick 4K Max in Deutschland eingestellt. Betroffen sind alle Geräte mit H.265-Unterstützung, während die günstigeren Modelle mit Full-HD-Auflösung, wie der Fire TV Stick u
https://www.apfeltalk.de/magazin/news/verkaufsstopp-fuer-fire-tv-stick-4k-in-deutschland/
#News #Tellerrand #Amazon #Deutschland #FireTVStick #H264 #H265 #Nokia #Patentstreit #Streaming #Verkaufsstopp #Videocodecs -
Кстати, вчерашний день потратил на уменьшение своей коллекции онямешек с 50 Гб до 25 Гб. Да ещё некоторые тайтлы перекачал в 1080р.
Видео - первое что ищем - #AV1, если нет, то #H265, можно и #H264, но только если мало весит.
Звук - нахуй все ваши #Flac, #AAC и #TrueHD, конвертируем всё в #Opus 128k. Оставляем только оригинальную дорожку.
Субтитры - оставляем только русские. #Ass, #UTF8.
Аттачменты - убираем всё, что не ломает ваши сабы.
Наслаждаемся тайтлами в отличном качестве при минимальном весе! :blobcatthumbsup: -
gente clavada del #video y del #archivodigital
¿debería estar convirtiendo mis películas a #h265 ?
Veo que ese encoder ofrece significativas ganancias de espacio, pero no sé aun dónde está el truco.
-
I purchased this gpu for video encoding (VP9/AV1) https://www.amazon.com/dp/B0CSFJN835?ref=ppx_yo2ov_dt_b_product_details&th=1 . It's a little encoding powerhouse, and for the low $99 price tag IMO it's a really good value. I'm able to encode a 2hr BluRay movie using VP9/AV1 in about 10 minutes. The only negative about the card is the onboard fan. It's pretty noisy.
#Intel #IntelGPU #GPU #GPUEncoding #VP9 #AV1 #Jellyfin #SelfHosted #ffmpeg #Encoding #Codec #h265 #h264 #Linux
-
The last days i wanted to deliver a video (as a static video file) on my webserver to friends. Personally i mostly use #vp9 / #opus codec in #webm container. This worked everywhere but on #iOS. I do not have an Iphone so i could not test it before.
I tried to get vp9 working (and ask friends to test again), but couldn't get it work, though there are many announcements that Safari will supports it (in 2020). Then i tried #h265 / #hvec in mp4 container because Iphones use this for encoding their recorded videos. So i thought this must work. But also that did not work.
Afterwards i found this guide who tells that #Safari only accepts #h264 static video files. Everything else has to be delivered by #HLS. Does anyone knows why? Is there a technical reason why accepting h265 videos in hls but not in static file? https://developer.apple.com/documentation/webkit/delivering_video_content_for_safari
During my research i found many different arguments why iPhones did not support vp9 (due to missing hardware decoders or because it increases code complexity). I can understand that but i can not tell you if this is the real reason (or just because its a standard of Google). But on the otherside i found information that Apple supports VP9 with HLS. but does not say this official.
PS: I know i could just use standard h264 encoding, but i wanted to have small video size and i thought that ios will accecpt at least any format that is newer than h264.
-
I wrote an article on how to quickly (13x speedup) convert an #H265 video to #VP8 using #FFmpeg and #Vaapi to upload it to #Mastodon respecting its restrictions 🎬
https://www.paulox.net/2023/05/03/quickly_resize-a-video-with-ffmpeg-for-mastodon/
Thanks to Michael Kennedy @mkennedy , Samuel Colvin @samuelcolvin and Sebastián Ramírez Montaño @tiangolo for the interview they did at #PyConUS 2023 🇺🇸
