notabot

The general process would look something like:

1. Find all of the SSH keys you want to replace.
2. For each of thise keys, identify everywhere you use it to authenticate, and write this down! This list will form the basis of the rest of the plan. Make sure you list all of the accounts/servers you log in to, and don’t forget things like github or other external systems if you use them.

You’ll need to perform the following steps for each SSH key you are replacing:

1. Rename the public and private keys to something like old_id_rsa and old_id_rsa.pub (obviously use the same type name as your key, just prefix old_)
2. In your ~/.ssh/config, add a line telling SSH to use the old key as well as the new ones: IdentityFile ~/.ssh/old_id_rsa (change the key filename as aporopriate)
3. Check you can still log in to the servers you could log in to before. It should still be using the old key, just with a different filename, so it should still work.
4. Generate your new SSH keys ssh-keygen -t ed25519
5. Log in to each server and ADD the new ~/.ssh/id_ed25519.pub key to the authorized_keys file or equivalent mechanism. Do not remove the old public key yet.
6. Remove the IdentityFile line from your ~/.ssh/config
7. Check you can log in to all your systems. This will validate that your new key is working.
8. Remove your old public key from the authorized_keys file on each server you log in to.

Depending on your threat model you’re going to want to do this more or less often, and so you may want to consider automating it with sonething like ansible if it’ll be a regular job.

Why do you think siblings would hate each other? Giving them the mental and emotional tools to interact kindly and calmly with others will also ensure their reltionship is positive.

You can definitely run it on those sorts of machines. You’ll want plenty of storage, but apart from thst it’s not too demanding if you don’t load it up with very high res videos.

It wouldn’t be quite so bad if the previous gold rush ended first, but they seem to just be stacking up.

This is so very important. Snapshots are very helpful tools, and most if the time they’re exactly what you need to recover. Unfortunately they don’t help when the drive fails, or the machine is destroyed by flooding, or myriad other failure modes (human error nit being the least of them). Remote backups are vital if you want your data to survive those events.

Remote copies of the snapshots are a start, but leave you at the mercy of and bugs in the snapshot system, and usually more critically, you have to transfer the whole snapshot or delta, and can’t exclude data without first rearanging your mountpoints.

Lical snapshots and remote file backups give you the best of both worlds, making it easy to recover your data from pretty much any event.

You can’t use anything but maximum super strength, all the time.

I like what you’ve done so far. It’s quick and simple to use. The one bugbear I’ve come across so far is it converting tables to html, rather than storing them as proper markdown.

I read the reasoning in the documentation, and certainly for my usecases, maintaining it as markdown is more important than trying to perfectly preserve the visual formating, especially as I use multiple devices with different sized screens, so I need different fornatting on each! That’s one of markdowns main strengths, it doesn’t preserve formatting so you don’t need to think about it and it’ll be displayed in a reasonable manner anywhere.

Is there any reasonable chance that there could be an option, at the server level rather than per page, to store tables as markdown?

I get the sentiment behind this post, and it’s almost always funny when LLM are such dumbass. But this is not a good argument against the technology.

It’s a pretty good argument against the technology, at least as it currently stands. This was a trivial question where anybody with a basic reading ability can see it’s just completely wrong, the problem comes when you ask it a question you don’t already know the answer to and can’t easily check and it give equally wrong answers.

Nevermind spears, they’ll be able to operate tin openers!

Only the admin of your instance can see your IP address, it doesn’t get federated to other instances.

Thanks for the analogy, that really helps to put it in perspective. I was trying to work out the number of molecules per metre that would leave you with, but either my sense of scales is off kilter or I’ve got it wrong.

From what I can find, there are approximately 2.5e25 molecules per m³ at 1atm. Given an 11km cube has a volume of 1.3e12 m³, that gives around 2e13 molecules per m³ per m³ released. That sounds high, have I got the figures wrong somewhere?

This is excellent article on enshitification, some of the factors that can lead to it, and ways founders could think about it to hopefully avoid it. What it doesn’t seem to talk about is how Tailscale intends to avoid it, now and in the future.