It looks like AssDB uses a weird SQL syntax? Is it worth upgrading to, I hear it’s great at pulling information out of unstructured and even imaginary data sources?
It looks like AssDB uses a weird SQL syntax? Is it worth upgrading to, I hear it’s great at pulling information out of unstructured and even imaginary data sources?
Ah, memories. That was me on a Spectrum. It’s all fun and games until you forget to save (to tape) and your code hangs the machine, losing everything.
The difficult bit is to keep the fuel fusing. At the temperatures and pressures that are needed to get atoms to fuse together the whole lot wants to blow itself apart. Being able to reliability sustain the reaction for any length of time is a big achievement.
Once we can get it to keep going, then yes, we can use the excess heat for power, although it’ll probably involve turbines rather than an old school steam engine type setup.
Depending on what sort of shirt it is, could you considered sewing an interesting patch over the area? Take a sort of ‘visible mending’ approach? That way it just becomes one more memory associated with the shirt.
For something like that i’d take a parameter like this (repeated as necessary):
--custom-repo=<name>=<synctype>+<url>
for example:
--custom-repo=custom=git+https://github.com/matcha/custom
I’m not sure if you’ll see this, as federation seems to be playing up on lemm.ee, but first I wanted to congratulate you on your attitude to life, it’s an inspiration.
As to your question; I think Obsidian is an excellent tool for you to do this in. As it uses a fairly standard type of markdown for formatting you have plenty of options.
I’d suggest a two pronged approach to make sure your writing is accessible. In the first place, for the more personal stuff, just print it out. Put the printout in an envelope, write instructions on it that it is only to be opened after you pass away and then mail, or give it someone you trust (a friend, family member, solicitor etc). You can update it by jyst giving then a new copy, or just extra pages to add. I’d suggest making a couple of copies to be sure they get to the people who you want to read them.
For the general stuff, as Obsidian uses markdown and so does the wiki function on github, you should be able to just commit the vault to your wiki repository and have it rendered reasonably. That way it’ll reflect your changes with little effort. If you’re worried you might do something to it, ask a friend, or acquaintance to fork the repository and regularly sync it. That way you can’t remove all the copies.
Let me know if you need more detail.
This one I wondered about more because of the effect of atmospheric pressure(?) on melting point, such that I wondered if it would be worth using Fahrenheit’s Weird Brine ice slurry to get ~ -17.778 ° C instead. But that’s ofc also subject to air pressure influencing melting point so I’m unsure if it’d be worthwhile.
Varying air pressure is certainly a concern, but repeating the experiment, as you said, would help to reduce the error, as would being as close to sea level as possible. Interestingly, if you have your meter measure you could use that to measure atmospheric pressure by seeing how far you could raise water in a column by suction. At standard atmospheric pressure you should be able to lift fresh water 10.3m.
Relatively constant 9.81 m/s² gravity is also useful for deriving force as you mention, though it reminds me of learning, to my abject horror, in undergrad physics that gravity does vary quite a bit by geolocation :'D 9.81m/s² is a better starting point than nothing though
Gravity is altogether too unreliable and should be abolished. Failing that, You could measure the local gravity by measuring how far a rock falls in a fixed time, say one second, and calculating back from that. If the rock is heavy enough we can ignore air resistance as the effect will be smaller than our measurement error.
Once you can get a good reference for one unit ypu can start to use it to determine the others. None of these are going to be perfectly accurate, but they should be good enough for day-to-day use.
I’d start with time. We’re going to make a sundial. To do this you need to make a drawing compass and some flat ground with plenty of sun. Find a v-shaped stick, or lash a couple together so you can scribe circles in the ground. Start by making one circle around a well marked centre point, then using the same compass, draw another circle centred on the edge of the first. Draw two more circles where the second crosses the first, and two more where those cross it. You should now have a central circle with the perimeter divided into six segments (this is the same technique for drawing a hexagon inside a circle). Put another stick upright in the centre and you have a sundial with 2 hour segments. You can bisect the lines between each of the points to get 1 hour segments, and if it’s big enough, busect again to get 30 minute segments. We’ll get shorter time measurements later.
The next unit to find is the meter. A one meter pendulum completes a swing from one side to the other every second. In order to minimise the effect of air resistance, find a heavy, but not too large rock and tie it to the end of a rope. Measure out approximately out meter of rope (measured from the centre of the rock) and tie it to a solid branch. Next is the tedious bit. Set it swinging as the sundial hits one of it’s marks and count the number of swings until the sundial hits the next mark. You should get 3600 per hour. If you get too many, lengthen the rope and try again, if you get too few, shorten it. Once you have the right number you have both your meter measure and your one second.
You can get a metric tonne, and thereafter a kilogram, by building a balance weigh beam, and a cube shaped container that is exactly one metre on a side. Attach the container to obe side of the beam, and a second container exactly the same distance away from the pivot on the other side. Add rocks to the second container until it balances with the empty first containor. Now fill the first with cold water. Add more weight to the second until it balances again. The additional weight should be exactly one metric tonne. By careful geometry you could reduce tge size of your first container to make this easier, but keeping it big and then dividing the result minimises measurement errors.
Temperature is harder to measure, but you can build a thermometer with any liquid that changes density with temperature. Even water works, although adding alcohol helps I believe. So, while you’re finding the meter, get some fruit and let it ferment. Use the resulting liquid in your thermometer. If you don’t have a glass tube, and can’t make one, use an opaque one, and float a light reed or similar on the liquid, with the end sticking out of the top. Calibrate it with boiling water for 100c, and, assuming a reasonable climate, wrap it against your body for a goid long while to get 37c. If you have accesd to ice, letting it just melt gives you 0c. Dividing the marks you get like this would involve some careful geometric construction, but should yield a usable thermometer. Converting that to Kelvin, as the SI unit, involves adding 273.16.
The ampere and candela are probably of less use in this situation, and are going to be tricky to measure. By assuming gravity is 9.81m/s^2 and using the kilogram you can derive the Newton. From that you have the Joule, and one Joule per second is one Watt. Assuming you build a generator, you can derive the Ampere from it’s older definition relating to the force, in Newtons, between two parallel wires. From there the volt can be derived.
Beyond that, I think you should just hope for rescue!
Thanks for a thought provoking question.
There are multiple copies of your files; the obvious one is your ‘working copy’, which is just the files on your machine that you work on. The second copy is in your local object store (in the .git directory). Git stores the committed data and it’s metadata there. Then there’s the remote copy on your git server if you push your commits to one.
Git uses the difference between the data in your ‘working copy’ and your object store to work out what you’ve changed and so needs commiting.
Yes, connect lets you block instances, but it still shows that there was a comment there and lets you show it. It’s handy to see how much you’re blocking.
I only use CLI access over SSH to manage servers. Using a GUI is painful, especially working remotely. Even wjen I had to deal with windows servers I’d setup an SSH server on it and use powershell.
Ideally you don’t even access the server manually over that, but use a management system like Ansible or Puppet to configure and manage it.
If you actually want to buy a significant quantity of a product like that from overseas (which I’m assuming because you mention a ship load) you’ll need to find and contact an appropriate supplier and agree terms, which will probably involve them supplying the goods ‘free on board’ meaning they’ll deliver to a port or ship and it’s your responsibility from there. Then you need to contact a shipping company to arrange the actual transport. You’ll also need to liaise with the customs departments of both the source and destination countries to get the paperwork in order. If you can find an importer in your target country, you might be able to agree terms with them and have them handle all of that. Then you’ve judt got to get it from the port to where you need it.
It sounds like you might be referring to communities rather than instances. If you don’t want to mod it yourself you could ask in one of the request communities and soneone might choose to start it. Try doing a search for ‘request’ on whichever instance seems like a good fit, and you’ll find one.
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.