Tailscale is probably what you want, but if you care about privacy you'll have to be sure to disable the telemetry/logging/spying option on each of your nodes.
By default it will leak your so-called “private” network behavior to Tailscale (connections on what port, from what node, to what node, opened when, closed when): https://tailscale.com/docs/features/logging
>More often than not, liminal aesthetics are human-made spaces, sans humanity.
>suggests a humanity at the brink of becoming digital objects themselves.
>But one can imagine a different version of this scene: a future humanity similarly excavating remains of corporate hallways that have since crumbled, wondering what life could have been like at the turn of the 20th century.
Relevant, and as spoiler-free as I can make it: I cannot give a stronger recommendation to play NieR and NieR:Automata.
I think Andreessen sucks, but I think body-shaming him is lame too, especially in the opening sentence (yes I read the whole article and agree with it to the point that I have nothing to say about the rest)
Not defending the body-shaming, but I imagine the reference to his large head is meant to be a double entendre. Figuratively, a massive ego. Literally, a big head.
HandBrake is the best if you want to ruin all of your DVD encodes.
e: downvote if you want but I'm right and you're wrong lmfao
For anyone in the peanut gallery who wants a good deinterlacer, try QTGMC. It's originally an Avisynth script, but I use a VapourSynth port: http://avisynth.nl/index.php/QTGMC
It all comes down to the fact that DVD is more of an analog format than a digital one. I feel like people get “CD ripping brain” which causes them to think that the most desirable thing is making the most-accurate copy of what's on the disc. For CD that's true because PCM is PCM, but for DVD the thing we really want is the program material, which is three layers deep on a DVD: inside an NTSC video signal, which is digitized following the Rec.601 standard, which is then shoved into an MPEG2 transport.
Four major things that can be done to DVD to make them look great on modern displays:
- Deinterlacing is the hardest to get right. Progressive-scan 24-frames-per-second DVDs exist but are mostly confined to movies where there will be a better BD release anyway. Interlaced DVDs where the program material is intended to be seen in 24FPS get “inverse telecine” (IVTC) instead of straight deinterlaced, but again I don't do a lot of those for the same reason. Almost any NTSC DVD that I care to encode is thus going to be 60000/1001 fields per second, which needs to be turned into 60000/1001 frames per second to avoid throwing away half of the available motion detail. If you do nothing at encode-time and produce an interlaced output, then the display or player software will end up doing it and will do a bad job. HandBrake's deinterlacing options just don't look good in my experience. I like QTGMC for this because it predicts the motion of the infill fields instead of just copying the previous field verbatim. It's very noticeable any time there's a lot of horizontal movement in the program material.
- Resolution and ratio. Most people hear “anamorphic” DVD and think of 16:9 crammed into a 4:3 image, but the truth is that all NTSC DVDs are anamorphic. They're 720x480 which if you calculate it is actually a 3:2 aspect ratio. Very clever because it ends up being about the same amount of scaling for 4:3 or for 16:9 material. They rely on PAR/DAR flags to tell the player or display how to scale it, but modern displays have terrible terrible scalers because it's purely a box-checking thing for them and not a feature they spend money or effort on. When I encode a DVD I stretch it myself at encode-time to 720x540 or 960x540. There's obviously some artifacting inherent in that vertical stretch, but it avoids throwing horizontal resolution detail away by scaling 4:3 programs down to 640x480 like most encoders do. Then the 540 pixel-doubles cleanly into 1080, 2160, etc.
- SD colorspace (Rec.601 again) is a similar issue where modern displays are just fucking terrible at it because there's no economic reason for them not to be. The chroma is already subsampled, so greens especially end up looking washed out and terrible. When I encode a DVD I convert them into HD colorspace which doesn't restore subsampled chroma but at least avoids letting the display make it worse.
- Cropping. The program-area resolution is actually 702 or 704x480 for anything transferred from tape (look up SONY D-1). If you have any "DVDrips" sitting around of an '80s or '90s TV show, does it have 8 pixels of black pillarbars on the left and right? If so then the person who encoded it didn't know what they were doing. It subtly throws off the aspect ratio for the entire program, especially noticeable in animation where they tended to use exact-circle tools. Look at the characters' eyes in The Simpsons for a great example. I crop those off before my one-time scaling so the program ratio comes out perfect.
This all applies similarly to PAL DVDs except I'm usually shrinking them down to 540px because the loss of some vertical resolution is still better than trying to get a modern display to scale 576px to panel-native res, and deinterlacing PAL is a straight 50-fields-to-50-frames without the wacky 1001 division notation that is a legacy of the backwards-compatible way that color was introduced to NTSC.
As with any lossy encoding process, I also always keep my originals so I can do it over in the future if need be :)
Not necessarily the physical disc but at least an ISO. I tend to rip DVD ISOs with the encryption intact in the name of making an untouched copy, since CSS is so thoroughly broken and since I have seen some very bad “backup” tooling that corrupts the VOBs when decrypting. I use DVDfab Passkey which is free for DVD usage; “Rip to Image” → “Keep Protection”.
I just remembered that I have a non-infringing example encode I can share: PBS's “Code Rush — A Year in the Life of a Silicon Valley Supernova: Netscape” (2000)
A copy of this was released as an MPEG-4 Part 2 (not AAC/H.264!) MOV back in 2008 to commemorate the Firefox 3.0 release: https://waxy.org/2008/06/code_rush/
This seems like a bit of a microoptimization if you're just interested in getting a streaming-service-quality level of DVD rip (which is fine by me).
I have no problem with someone wanting the highest quality possible, but for me, I mostly stream videos to a TV or to an iPhone, and unless it's a 4K UHD video (which I still compress to H.265 currently), I'm not too worried about pixel peeping at the quality.
I still watch VHS dubs too, and those have all kinds of crazy artifacts/color issues :)
There's no reason this can't by automated! I have a StaxRip workflow that takes care of everything I mentioned below except for the cropping which tends to be more fiddly — some times larger on the left or the right, or some times including the top and bottom too for e.g. Academy-ratio material that's hard-matted to the DVD res.
I'm on vacation right now (shouldn't be on HN or my phone at all but what're ya gonna do) but can upload it somewhere when I get home next week and can access that machine.
Even this cannot adjust volume levels independently for multiple tabs in the same browser, which I have always been able to do on linux with pulseaudio/pipewire. People on windows use browser extensions for this, with full access to all tabs/sites...
Every time I try to build a castle in my swamp, it gets to a certain height and then it just sinks?
STOP telling me about civil engineering, we fucking invented that shit. And NO, we have to build it in the swamp, it feeds us and keeps us safe, and I'm darned proud to say we invented that too.
I right click the volume icon in Windows, select "Volume Mixer", and it gives me per-app mixing. Which I guess is an extra click, as with eartrumpet you can access the mixer with a single left click on the icon.
I like a lot of things about Windows and would consider myself technically literate. I also like Linux and especially FreeBSD, but Windows has Good Bones. Shame about all the spyware and the shitty modern UI though.
By default it will leak your so-called “private” network behavior to Tailscale (connections on what port, from what node, to what node, opened when, closed when): https://tailscale.com/docs/features/logging
reply