A dinosaur skeleton in a spacesuit.
A dinosaur skeleton in a spacesuit.
I enjoy reading dead tree books as much as anyone, and whilest the publisher/distributor can’t take it away, there are plenty of ways you can lose access to them. Fire and flood being the two obvious ones, whereas digital books can be backed up offsite. It’s also easier to carry many books when they’re digital compared to physical.
For books I care about I try to get both a physical and a (drm free) digital copy for the best of both world.
Nah, don’t blame it on the sunshine, don’t blame it on the moonlight. Blame it on the boogie.
Several models of helicopters have ejectable blades, this article mentions a few, and has a diagram of the blade severing system.
It’s a non-starter for me because I sync my notes, and sometimes a subset of my notes, to multiple devices and multiple programs. For instance, I might use Obsidian, Vim and tasks.md to access the same repository, with all the documents synced between my desktop and server, and a subset synced to my phone. I also have various scripts to capture data from other sources and write it out as markdown files. Trying to sync all of this to a database that is then further synced around seems overly complicated to say the least, and would basically just be using Trillium as a file store, which I’ve already got.
I’ve also be burnt by various export/import systems either losing information or storing it in a incompatible way.
H.A.R.M - High-speed Anti Radiation Missile.
Basically, rather than having it’s own radar to track a target, or using IR sensors, it locks on to a target emitting lots of radio noise such as an enemy radar or jammer.
I like it, this is clearly very enterprisey and solution focused, but I would like to suggest a couple of amendments if I may?
Namespaces
We should make full use of namespaces. Make the structural tags be in a language specific namespace (to be referenced in every function spec, obviously) but change the in an out params to use the parameter name as the tag, namespaced to the function they’re for, with a type
attribute.
In memory message queues Have all function invocations be marshaled as xml documents posted to an in memory message queue. Said documents should use a schema that validates the structure and a function specific schema to validate the types of arguments being passed. Namespace everything.
I reckon we could power a medium sided country if we could generate energy from the programmers despair.
I guess you could, although the gripper would add a bit of mass to the drone. You still lose some energy from the round into the yeeted barrel, but not as much as having an open breech. Depending on the mass of the projectile vs the mass of the barrel that could be a worthwhile trade-off.
I don’t think that’ll do it. The propellant deflagration is so quick that the momentum of the drone means it can’t be accelerated backwards enough to significantly reduce the force on the airframe. Even if it did, that would just end up applying the acceleration to the internals such as the batteries and motors/engine instead. I think you would need a spring damper that would allow the weapon to recoil quickly and dissipate the energy more slowly, and I’m not sure you could make obe effective on something the size of a drone.
I was thinking about those, but I understand they tend to suffer from inaccuracy due to even slight imperfections in the manufacturing of the jet openings.
I think something more like a conventional round, with a heavier casing and more propellant might work. The casing gets ejected backwards and the projectile forwards, without imparting momentum to the barrel. You do need more propellant to get the same muzzle velocity though.
I’d imagine the shock loading into the drone’s structure would soon damage it if it was powerful enough to flip it. You’d need a significant damper to spread the shock out over a longer period. Alternatives are either recoilless rifles as suggested or something more akin to rockets, basically a tube that’s open at both ends, with a round that has enough propellant to fire without the need for a breech, and electronic ignition.
Putting a simple preseed file on a debian install image is probably going to be your best bet. Assuming you can run a VM on your current machine it shouldn’t be too difficult to test it until you’re happy with it.
It’s going to be a balance between your time getting an automated approach to work and the cost/effort of getting a monitor. Getting preseed working can be a bit fiddly, but it does mean you’ve learnt a new skill, getting a monitor sounds like it’ll be a pain, and you might only need it once.
Yes, that’ll work too, it does involve adding the disk to your machine temporarily though, so just be carefully which disk you format to do it. Please don’t ask why I say that, it brings back painful memories…
While I agree with most people here that finding a keyboard and screen would be the easiest option, you do have a couple of other options:
Use a preseed file A preseed lets the installer run completely automatically, without user intervention. Get it to install a basic system with SSH and take it from there. You’ll want to test the install in a VM, where you can see what’s going on before letting it run on the real server. More information here: https://wiki.debian.org/DebianInstaller/Preseed
Boot from a live image with SSH Take a look at https://wiki.debian.org/LiveCD in particular ‘Debian Live’. It looks like ssh is included, but you’d want to check the service comes up on boot. You can then SSH to the machine and install to the harddrive that way. Again, test on a VM until you know you have the image working, and know how to run the install, then write it to a USB key and boot the tsrget server from that.
This all assumes the target server has USB or CD at the top of its boot order. If it doesn’t you’ll have to change that first, either with a keyboard and screen, or via a remote management interface sych as IPMI.
See, I knew it, lipo batteries batteries are really unsafe, just tap them against something and they burst into flames!
…what do you mean, that’s not what you mean? It’s what you said!
If you don’t need external calling you don’t need a trunk, it’s just for connecting to the outside world. I found [[https://www.asterisk.org/|Asterisk]] was a good place to start. The config is rather involved though, so there are various front ends for it.
You can, but I found it a bit laggy. It basically wraps your tcp stream over https, so I think the extra overhead was what was slowing it down.
Clearly what you need to do to avoid the recoil is mount the guns on a solid metal hoop like structure around your chest, and have a matching set in the back to balance the forces. One pull of the trigger and you ruin everybody’s day.