Yeah but why would I make myself dependent on Cloudflare.

To be fair, you can simply selfhost MinIO.

Wait, not the other way round? One tale per 70-min episode?

(With the priest’s tale getting an initial 1.5hrs opening episode? 👀)

Hah… Fair 😄 Hope you’ll get the chance!

Interesting - this is the first time I have seem someone (implicitly) dislike Villeneuve’s version (though to be fair, I have not closely followed the discourse around it). DO you have additional grievances, beyond the actors?

Lol… Same :D

For myself: Dan Simmons’ Hyperion Cantos. I know that I will never be in a situation to do as the question above suggests (nor that I would have the knowledge or skills required), but I am currently re-reading the books (Hyperion, Fall of Hyperion, Endymion, Rise of Endymion), and I can’t stop thinking about a big screen adaptation.

Or rather, Simmons’ writing is so vivid, so vibrant that you can’t help but visualize it in a cinematic way before your inner eye anyways. The alien, but still somewhat familiar environments, the gargantuan forces of nature and expansive backgrounds just as much as the more intimate set pieces, cities, secret meeting rooms, and so on. “Every Frame a Painting” is something I’ve heard said about some movies, and these books are the textual equivalent: “Every page cannot be helped but be turned into a Painting”. The Hyperion Cantos isn’t even my favorite book or anything the like; it’s just something that screams for an adaptation IMO, and a beautiful one at that.

I also think that the story is exceptionally well suited for either a limited series (Hyperion & Fall of Hyperion) or a movie (Endymion, Rise of Endymion). In fact, I am convinced that if this had been made into a series back in the early/mid 2010s, it could have had a genre- and generation-defining impact akin to (the early seasons of…) Game of Thrones. Today… I’m not sure a studio would spend the required amount of money to make this good.

(Also yes I made this post simply because I had nowhere else to put this comment.)

Lol, exact same situation here.

Quick question, did the migration to continuwuity break calls for you as well?

What’s a tomato?

Because a commit should be an “indivisible” unit, in the sense that “should this be a separate commit?” equates to “would I ever want to revert just these changes?”.

IDK about your commit histories, but if I’d leave everything in there, there’d be a ton of fixup commits just fixing spelling, satisfying the linter,…

Also, changes requested by reviewers: those fixups almost always belong to the same commit, it makes no sense for them to be separate.

And finally, I guess you do technically give up some granularity, but you gain an immense amount of readability of your commit history.

Is it really micromanaging? What you described sounds like coaching. With a professor / teacher, they are there to help you with doing things the correct / efficient way; and with a conductor, its them steering the orchestra towards their vision.

No idea about that, but I stopped watching them once I realized that, at least for their speculative topics, they just pull things out of their arse and present it with the same definitivity as the actually well-researched parts. Once you notice, it’s hard to stop noticing.

Same. And even if you were to fuck up, have people never heard of the reflog…?

Every job I’ve worked at it’s been the expectation to regularly rebase your feature branch on main, to squash your commits (and then force push, obv), and for most projects to do rebase-merges of PRs rather than creating merge commits. Even the, uh, less gifted developers never had an issue with this.

I think people just hear the meme about git being hard somewhere and then use that as an excuse to never learn.

Do not

Is this about the straight werewolves author?

Eternity is a loooooong time

TBH, it sounds like you have nothing to worry about then! Open ports aren’t really an issue in-and-on itself, they are problematic because the software listening on them might be vulnerable, and the (standard-) ports can provide knowledge about the nature pf the application, making it easier to target specific software with an exploit.

Since a bot has no way of finding out what services you are running, they could only attack caddy - which I’d put down as a negligible danger.

My ISP blocks incoming data to common ports unless you get a business account.

Oof, sorry, that sucks. I think you could still go the route I described though: For your domain example.com and example service myservice, listen on port :12345 and drop everything that isn’t requesting myservice.example.com:12345. Then forward the matching requests to your service’s actual port, e.g. 23456, which is closed to the internet.

Edit: and just to clarify, for service otherservice, you do not need to open a second port; stick with the one, but in addition to myservice.example.com:12345, also accept requests for otherservice.example.com:12345, but proxy that to the (again, closed-to-the-internet) port :34567.

The advantage here is that bots cannot guess from your ports what software you are running, and since caddy (or any of the mature reverse proxies) can be expected to be reasonably secure, I would not worry about bots being able to exploit the reverse proxy’s port. Bots also no longer have a direct line of communication to your services. In short, the routine of “let’s scan ports; ah, port x is open indicating use of service y; try automated exploit z” gets prevented.

I am scratching my head here: why open up ports at all? It it just to avoid having to pay for a domain? The usual way to go about this is to only proxy 443 traffic to the intended host/vm/port based on the (sub) domain, and just drop everything else, including requests on 443 that do not match your subdomains.

Granted, there are some services actually requiring open ports, but the majority don’t (and you mention a webserver, where we’re definitely back to: why open anything beyond 443?).

Client side, under advanced: