Perfect, he gets to make a big fuss for the racists, but doesn’t actually have to change anything. That way there’s less risk of breaking anything, and he’s probably looking for a win right now.

It’s a bit like decreeing that all English week day names must henceforth end in the letter ‘y’. It’s low risk, makes certain people think you’re busy taking action, and leaves everyone else wondering what you’re up to with this, taking some of the heat off of other issues.

This is an interesting prompt. Critically it seems like you definitely aren’t omnipotent, so whilst you can try to influence and teach the new inhabitants, there’s nothing stopping them simply ignoring you and doing something else.

Rather than some wanting to just not contribute, I’d be more concerned by a group deciding to focus their efforts on building weapons and simply taking what they want from others.

Fully automated luxury gay space communism is certainly an ideal, but it is extremely vulnerable to hostile forces until it gets large enough and willing enough to excert eqivalent force in return. Hostile forces can be military, ideological, or resource limit based. Responding to all of those, is a massive challenge.

I knew there was such a thing as slicing your shot in golf, I didn’t know it meant that!

It’s not for him, it’s for everyone who had to survive.

One might hope he’s giving out free samples, but these things are rarely as convenient as that.

Steady on Satan, they’re only a credit card company! They’re bad, but not that bad!

Rather than a platform, I’ve been wondering if you could rig it so opening the box opens some holes on the bottom, so they think they dodged the worst of it, pick it up to dispose of it and get a desk full from underneath.

That’s a fair observation, but I assume they’re trained to deal with suspicious packages safely, and that stuff will get transfered throughout the whole building and make everyone’s lives that bit more ‘special’. It’ll still hit the bottom line too.

Don’t use a rock, use 10lb of glitter.

Possesive spirit, 5 minutes later: “Let me out! Let me go back to hell!”

Me: “Nope, you pushed in, now you gotta drive.”

Spirit: “Please? At least it’s warm there.”

Thanks, this is a really handy tool. Kniwing the information was being withheld ‘just because’ was really rankling me. Now, could you just add a quick feature to read their minds and tell me why they down voted me? ;)

I’m sure you’ve already considered it, but from that description it sounds very much like make. That compares the input files’ timestamps to the output files’ timestamps, so it might be different to your plan though.

DUCK FOR COVER DUCK FOR COVER

Quack! *BOOM*

You can securely run IIS on Vista, you just have to unplug the network and power cables.

You… you don’t? Surely there’s some mistake, have you checked down the back of your cupboard? Sometimes they fall down there. Where else do you keep your internet?

Appologies, I’m tired and that made more sense in my head.

On the other hand, the enemy of my enemy is my friend

Maxim 29: The enemy of my enemy is my enemy’s enemy. No more. No less.

That doesn’t mean you can’t work with them on a common cause, and maybe even show them the benefits of your way if thinking, but don’t get caught out when they turn on you.

Before you can decide on how to do this, you’re going to have to make a few choices:

Authentication and Access

Theres two main ways to expose a git repo, HTTPS or SSH, and they both have pros and cons here:

• HTTPS A standard sort of protocol to proxy, but you’ll need to make sure you set up authentication on the proxy properly so that only only thise who should have access can get it. The git client will need to store a username and password to talk to the server or you’ll have to enter them on every request. gitweb is a CGI that provides a basic, but useful, web interface.

• SSH Simpler to set up, and authentication is a solved problem. Proxying it isn’t hard, just forward the port to any of the backend servers, which avoids decrypting on the proxy. You will want to use the same hostkey on all the servers though, or SSH will refuse to connect. Doesn’t require any special setup.

Replication

Git is a distributed version control system, so you could replicate it at that level, alternatively you could use a replicated file system, or a simple file based replication. Each has it’s own trade-offs.

• Git replication Using git pull to replicate between repositories is probably going to be your most reliable option, as it’s the job git was built for, and doesn’t rely on messing with it’s underlying files directly. The one caveat is that, if you push to different servers in quick suscession you may cause a merge confict, which would break your replication. The cleanest way to deal with that is to have the load balancer send all requests to server1 if it’s up, and only switch to the next server if all the prior ones are down. That way writes will alk be going to the same place. Then set up replication in loop, with server2 pulling from server1, server3 pulling from server2, and so on up to server1 pulling from server5. With frequent pulls changes that are commited to server1 will quickly replicate to all the other servers. This would effectively be a shared nothing solution as none of the servers are sharing resources, which would make it easier to geigraphically separate them. The load balancer could be replaced by a CNAME record in DNS, with a daemon that updates it to point to the correct server.

• Replicated filesystem Git stores its data in a fairly simple file structure, so placing that on a replicated filesystem such as GlusterFS or Ceph would mean multiple servers could use the same data. From experience, this sort of thing is great when it’s working, but can be fragile and break in unexpected ways. You don’t want to be up at 2am trying to fix a file replication issue if you can avoid it.

• File replication. This is similar to the git replication option, in that you have to be very aware of the risk of conflicts. A similar strategy would probably work, but I’m not sure it brings you any advantages.

I think my prefered solution would be to have SSH access to the git servers and to set up pull based replication on a fairly fast schedule (where fast is relative to how frequently you push changes). You mention having a VPS as obe of the servers, so you might want to push changes to that rather than have be able to connect to your internal network.

A useful property of git is that, if the server is missing changesets you can just push them again. So if a server goes down before your last push gets replicated, you can just push again once the system has switched to the new server. Once the first server comes back online it’ll naturally get any changesets it’s missing and effectively ‘heal’.

Parks are great, but unless they’re directly outside the houses where I can keep an eye on what’s happening they’re not as safe or convenient. Being able to send the kids into the garden to run off some energy whilst I’m in the house doing something, and being reasonably confident that they’re safe is a huge benefit.

That’s certainly not impossible with a bit of sensible planning around how housing is laid out, putting clusters of housing directly around a shared green space, but it is rather challenging to retrofit in existing conurbations, and impossible in more spread out communities. The American style of huge featureless lawns surrounding the house right up to the property boundary are pretty awful, but the more European style of a bit of lawn surrounded by flower beds and maybe trees is rather better.

If you have kids It’s helpful to have an open, flat area for them to run around on. It doesn’t need to be (just) grass, but that’s probably the most robust, and least likely to have sharp surprises, option.

You get a full eye roll and groan for that.

I manage all my homelab infra stuff via ansible and run services via kubenetes. All the ansible playbooks are in git, so I can roll back if I screw something up, and I test it on a sacrificial VM first when I can. Running services in kubenetes means I can spin up new instances and test them before putting them live.

Working like that makes it all a lot more relaxing as I can be confident in my changes, and back them out if I still get it wrong.