• 0 Posts
  • 14 Comments
Joined 1 year ago
cake
Cake day: August 26th, 2025

help-circle



  • Using nix to maintain my fleet with automated updates so I didn’t really need to worry about it thankfully; just checking that I had relevant/patched versions. All my services are nice and up to date so didn’t even have to take anything down (yay)

    What I’m excited for today is to progress personal slop project (be gentle) I started yesterday. Hoping it’ll just be one or two weekends.

    I’ve been hallucinating a transcoding suite/workbench. Includes experimental sampling matrix of ffmpeg settings with a composable / layer-based project configuration; rust egui+mpv desktop client. Then the hosted orchestration server can distribute ffmpeg jobs across my worker machines (via my local headscale tailnet). Output produces a project+metadata bundle that includes hand-picked source:result JXL frame comparisons alongside both human readable reports and client readable configuration that makes the projects (more or less) reproducible (with worker tool env versioning via nix flake.lock) and logs provenance.

    I intend for this to be a replacement to the piles of crappy python scripts I’ve been using for the last decade; my current workflow is to move files into host-labeled ingest folders with an argument string in a text file, then ssh to the host to run the job.

    But what I’m most excited for is the experimentation matrix. I hope that it will reduce my electricity usage and disk thrashing; it will let me sample settings for ~1minute of footage around the sample frame and let me iterate my tuning much faster. Currently, it’s faster (in terms of hands-on time) to just transcode whole episodes or even entire seasons multiple times with different settings and then just discard the ones that underperform. Extremely wasteful; testing a settings matrix is something I’ve always wanted, but never had the time to build (and still don’t, hence slop).


  • A meaningful distinction to me at least is that when I’m vibecoding a one-off personal project I don’t care about, I don’t even look at the code.

    When I’m using LLMs on a serious project that matters, I never blanketly give it a task to write code. Debugging and investigation work is more “go do the thing” vibecody, but when it comes to actually implementing fixes or features: I’d only ever use an LLM when I already know what the code should look like. And most of the time, when I’m writing in a language that I’m not perfectly familiar with, it’s writing as good as me if not better. Its a flat win case. In something like C++, I have a particular style and am very pedantic, and I know the standard very well, and so I tend to need to handhold and fix or rewrite a lot more. The vast majority of programmers who write C++ don’t write like I do, and I’m willing to bet that my “like me or better” statement about languages I’m only intermediate in applies to most casual or junior C++ devs.

    With that said, his diff seems to have a hell of a lot of additions. I’d be willing to bet if he’s using Frontier LLMs that the vast majority of that is testing (and comments if they use claude…)

    I think if someone has a hard no-AI stance, then it’s probably just safe to avoid the project. Whether or not it’s “vibecoding” depends a lot on their workflow and their standards.

    If I need to write 10,000 lines, and I know what it should look like, and the AI produces that: I see no reason why I should waste my time typing it all out by hand. With that said, “Bot, go implement XYZ” isn’t how I or most experienced devs work with AI, and that’s where a lot of problems come from.

    The good news is that it’s mostly a self-solving problem, because those codebases become completely impossible to work in over time.




  • Same almost. I have an ~800gb main library of mostly lossless files that I squash to around 150gb by transcoding to 196k or something opus that i put locally on my phone. I also strip embedded cover art which can save a stupid amount of space sometimes; relying on folder hierarchy with cover.jpg/png files. (Bitrate is pretty overkill for me so I may drop it to 128-160…)

    I haven’t had the time to manage the tags properly on my reference library*, but my folder hierarchy encodes artist/album/title with optional years and track numbers. I wrote a linter script to check the structure, that every folder has a cover art image, and to warn about lossy formats not in directories suffixed with [lossy] (purely for documentation purposes; not used in script logic).

    My transcode script generates tags from the folder and filenames, only copying genre tags if they exist and stripping everything else. Lossless files are transcoded while structure, art, and lossy files are copied. Then that result is synced to my mobile devices. So whenever I add music my workflow is to just name file folders properly and download or extract art then I just lint, transcode, and then resync.

    *(Tags of my reference library don’t matter so much to me, but the squashed lib needs consistent tags for mobile apps for behave as I intend)


  • When port forwarding, you want that internal IP to be the internal address of the server on your LAN. That way, all port 443 traffic sent to your external ipv4 (as received by your router) is sent to whatever machine is hosting the web server or reverse proxy.

    Regarding the www sub domain cname, idk what your registrar is doing but it’s common practice to redirected www to your base domain, or vise versa; so web visitors get a consistent experience whether they type www or not. It would probably be best to start fresh though




  • A DAS is more like an external drive where as a NAS is a service reachable on your LAN. Of course, you could use a NAS and plug it straight into your PC for a more DAC-like experience to keep it off your network… It really depends on what you’re after.

    It ultimately breaks down to these choice dimensions, and there’s often overlap which may inform one another (in no particular order):

    • platform hardware
    • storage medium(s) (ssd, hdd, layout, caches,…)
    • filesystem(s)
    • operating system
    • shares protocol (Samba, NFS, WebDAV,…)
    • topology (direct attach or where in your network it’s located, vlans and firewalls etc.)

    I interpreted ‘server’ to mean you had platform already which you want to turn into a NAS. If you want storage exclusively for your server, then DAS is fine. If you want to have the storage accessible my multiple devices, then you want a NAS.

    It depends on your usecase and what features you’re after.




  • I’ve been been deepdiving the cryptcom privacy space over the last week, refreshing my knowledge that was last updated about a decade ago. Signal spooks me because of the number requirement and centralization, but the tech is fine. Matrix is the new hotness but the clients kind of suck. I wonder if there are any i2p based apps? But Signal (or in my case, Molly-FOSS) seems to be fine for most purposes. Unless you’re the secretary of defense… There’s always Tox if you don’t mind the fact that it’s in dev and unaudited.