This command only print readable string opposed to hex edit. Could use tool like sed or perl to replace, but might corrupt file (for example if metadata part of checksum for some data). Note sed and perl need escape some special character because use regex.
strings file.mkv
sed 's/badstring//' file.mkv
hex dump is all raw data from file as hexadecimal number, not much readable. Except for raw string, which strings is better tool for.
Metadata define as all data that is not file data (in this case video), so you talking about metadata. Again, can infer some metadata from video data, but not enough to identify pc. Metadata like encoder version, timestamp when was recorded, recording device/software. Ffmpeg strip all except encoder.
I think you worried about metadata mostly. Can maybe infer gpu/os/software from encode pattern, but probably not problem for you.
For image metadata usually called exif data, exiftool on linux work well for me. For video, ffmpeg has ffprobe tool to extract metadata using some option. Ffmpeg also have some option to clear metadata (but not all), complicated a bit to set up right.
If not available for windows, search for alternative. Or graphical wrapper if not like commandline.
First verify you have good method to see metadata, then try what method remove what.
If really paranoid, dump windows (has lot of spyware), use tool like gnu strings to see printable string in binary file might be metadata.
For torrent:
See if already exist by someone (public index search, dht search engine)
Throw out handbrake, always upload original quality. Reencode fine if from raw source material, but no dvd/bluray has raw quality. Or if really want to offer small file, upload both.
Create torrent with dht/pex enable to allow dht search engine and other peer to find.
Use no-log vpn or i2p to seed.
More info probably in megathread or wiki.
Edit: 5. over vpn or i2p make account on public index and upload torrent as new post. Or share torrent with friend. Or on other forum.
A hardware circuit can't be changed; that's its nature. If it's acceptable for a device to be implemented with internal circuitry that no one can alter, then an internal program that no one can alter is no worse.
Treat ROM firmware as circuit.
The equivalence falls apart, however, when the software implementation is not totally internal and some company can modify that code. For example, when firmware needs to be copied into the device to make the device function, or included in the system distribution that you install, that is no internal software implementation; rather, it is a piece of installed nonfree software. It is unjust because some manufacturer can change it but you can't.
Here, for your reference, ROM is fair for anyone, non-ROM that is non-free not fair.
But not think this imply "ROM better", but rather "make free software or no software at all". He want absolute freedom, you want usability. Which absolutely not what libre about.
The position of the FSF is that a device whose closed source firmware cannot be upgraded is superior to one that can be upgraded but for which only closed firmware exists.
Where they say that? They say if ROM firmware, no freedom possible. So outside scope of FSF.
gun