Yes, needing to RTFM is much more manual work. Better to deploy bugs.
1,124 karma · joined April 23, 2013
Yes, needing to RTFM is much more manual work. Better to deploy bugs.
How's it up there in that tower? Citation needed.
This is no longer true.
Suppose you find a habitable planet, land there and start colonizing. Would we have to bring our bacteria / viruses with us to survive? Like, the idea that it would not be possible to get the flu again; but is therea trade-off? Would other bacteria eventually mutate sufficently to become infectious, and perhaps, would be even worse.
Our immune system would be tested. Assuming there is bacteria on the habital planet, it's not clear what would happen.
I guess the core of my question is: how homogenous is life?
Really? Who says?
all complete bullshit; they arbitrraly occasionally block to protect their moat raping privacy. e-mail is the most rewarding self-hosting capability. like anything, there is a learning curve but at the end of the day: it's easy, stable, a pleasure to host. there are solutions that ease the learning curve. after a while, all the e-mail do make it through.
i'm so happy that my communications are not indexed by these hyperscalers.
stop listening to these pussies claiming how difficult it is. they're projecting their limitations.
A man who carries a cat by the tail learns something he can learn in no other way - Mark Twain
Fine, shutdown the weather and stock ticker apps.
Plenty of people would lose money, break even, or God willing, make a tiny profit, diving into this problem. Regardless, it would make society a happier place.
Not quite done right.
For this edge case, the issue is not with DNS; it's that the router is not configured to allow internal clients to access the network through the public IP, vis-à-vis hairpin routing.
This made me consider my haproxy architecture. I use haproxy acl rules and the use_backend directive to enforce security policy and routing. It denies http requests based on source ip address per service (host header)
I think a good middle-ground is to use a single haproxy but two frontends; one binds to the public interface and one for private. haproxy is now no longer responsible for routing, the router is.
Won't be your last.
It's an incredible journey to take--whether you stick with it or not. Migrating to FreeBSD gives you new eyes into what Linux was, is, and the awesomeness of FreeBSD that is so hard to articulate; like describing the color blue. It must be taken as a whole to appreciate it; and I'm not just saying the OS, it's commands, kernel features, but, the end-to-end compute experience, over time.
If I could draw an equivelent, it would be like when Djistrka savagely destroyed the GOTO statement with a single, short, paper. It took a brilliant mind to articulate that and there has yet to be such a mind to describe the beauty of FreeBSD. So, the best I can do, is just to challenge you to try it.