Discover gists
1. Photoscissors 6.1 : UAAA-UAYO-AKBA-LAAA-WULP-MAKA-IFHA-CLAF | |
2. Batch Inpaint 2.2: ZUKA-BACE-GTRD-UCNR-LYDK-TVZG-ORNZ-HUTY | |
3. DupHunter 2.0: QRRD-ODNY-DJEI-CABC-AIVN-EPTP-DGAT-JSWB | |
4. FolderIco 6.2.x: FKAA-HAWO-MBRY-FHEV-UKAJ-DYHV-XWWA-PAFP | |
5. Inpaint 8.0: HWTU-QACW-ELMN-SVGP-AAAI-ITGP-EYPH-CFAP | |
6. Intelligent Resizer 3.0: EHSP-XUTD-UANB-XBBX-FUAQ-IPAP-UBNK-FFZR | |
7. NetLimiter 3 | |
Registration name: Peter Raheli | |
Registration code: C99A2-QSSUD-2CSBG-TSRPN-A2BEB |
Preamble:
In this post I will explore how to stream a video and audio capture from one computer to another using ffmpeg and netcat, with a latency below 100ms, which is good enough for presentations and general purpose remote display tasks on a local network.
The problem:
Streaming low-latency live content is quite hard, because most software-based video codecs are designed to achieve the best compression and not best latency. This makes sense, because most movies are encoded once and decoded often, so it is a good trade-off to use more time for the encoding than the decoding.
Systems Engineering (also known as Infrastructure Engineering, Operations Engineering, or DevOps) is a challenging but rewarding career path. Because Systems Engineering draws from a wide variety of smaller topics, it can be hard to know where to start and in what order to begin. This resource is intended to give you a sketch of some of the learning-paths that that can lead you to a career in Systems Engineering.
To start, let's examine a high-level list of topics that established systems engineers should have knowledge of. In each of these topics, the level of depth required to get started as a systems engineer may vary, but it's good to have a general breadth of knowledge on all of these topics.
These lists are not exhaustive, rather a good starting point to gain general knowledge.
#!/usr/bin/python3 | |
import sys | |
""" | |
This script assumes redundant part after the real ending is less than 8KiB | |
and since real size has to be x*16KiB+y*8KiB, by doing integer division by 8KiB | |
we get max number of CHR ROM pages (max y), excluding PRG ROM. Note that the redundancy | |
after the real ending is not deleted. | |
From there it subtracts 2 from y, and increases x by 1 and generates NES files named "bin{y}.nes". | |
Header flags are set so that |
import { parse } from 'parse5' | |
import { adapter } from 'parse5-htmlparser2-tree-adapter' | |
import xpath from 'xpath' | |
const html = '...' | |
const selector = '...' | |
const doc = parse(html, { treeAdapter: adapter }) | |
const htmlEl = doc.childNodes.find(c => c.name === 'html') |
Table of Contents
Originally posted at https://www.nccgroup.trust/us/about-us/newsroom-and-events/blog/2011/august/javascript-cryptography-considered-harmful/
We mean attempts to implement security features in browsers using cryptographic algoritms implemented in whole or in part in Javascript.
You may now be asking yourself, "What about Node.js? What about non-browser Javascript?". Non-browser Javascript cryptography is perilous, but not doomed. For the rest of this document, we're referring to browser Javascript when we discuss Javascript cryptography.