>Humanity together

Together? It would be, 1. AI programmers, 2. AI techbros and a distant 3. AI fiction/history/literature. Foo who never used the internet: not responsible. Bar who posted pictures on Facebook: not responsible. Baz who wrote machine learning, limited dataset algorithms (webmd): not responsible. Etc.

Whose keys are these keys? ;)

You can use Dynamic DNS[0]. Your server contacts a remote server and if the IP address has changed the DNS is automatically updated. You can use a free subdomain[1] and CNAME/ANAME/ALIAS[2] your domain's DNS to point to it.

Edit: Njalla supports dynamic DNS records natively[3].

[0] https://en.wikipedia.org/wiki/Dynamic_DNS

[1] https://freedns.afraid.org/

[2] https://en.wikipedia.org/wiki/CNAME_record

[3] https://njal.la/docs/ddns/

They install their own firmware. See 1001 firmware, for example.

Also, it's unlikely front line internet is capable of streaming the video back to DJI.

The website is nauseating.

And that logo ... Ugh!

Why would you embed some shit codepen iframes instead of the unicode character??

> Update: At some point, WordPress started automatically converting emoji in this blog post to <img>s. I’ve replaced some of the examples with CodePens to make it clearer what’s going on. Of course, the fact that WordPress feels compelled to use <img>s instead of native emoji kind of proves my point

My bad. My frustration with the iframes stopped me reading.

Edit: Can't you downvote your own comments??

How can I use the same ed25519 key pair for minisign and age?

You can't. Age is X25519, not Ed25519.

Edit: (Apologies). Thank you!

Even with "ssh-ed25519" [1]?

I looked at a ssh-ed25519 example [2] but i don't see how it can be extracted from the minisign secret key format [3], for example:

ssh-ed25519:

  ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIK0wmN/Cr3JXqmLW7u+g9pTh+wyqDHpSQEIQczXkVx9q gleb@reys.net

minisign secret key format:

  untrusted comment: minisign encrypted secret key
  RWRTY0IyNKMZZ+uqJdb8VtvSTo9EwylBlcsnitMtEyQzVLq/7tUAAAACAAAAAAAAAEAAAAAANLUi4xncsLbGKL+8y/n692Imrb9iURwzfnVfRqxqU5kAnVVrs98xMBqtIOiS63HZ3BQIGU6jpBWbX3ELCALfL/Le6UL3DunYfWqNPvhAKhlY4gQEjMzrL6ytxTFCXLGJpBSZHkK3DIQ=

[1] https://github.com/FiloSottile/age#user-content-ssh-keys

[2] https://www.unixtutorial.org/how-to-generate-ed25519-ssh-key...

[3] https://jedisct1.github.io/minisign/#secret-key-format

It looks like age with SSH keys uses a birationally equivalent keypair.

https://github.com/FiloSottile/age/blob/176e245b3cb3ada322c2...

If you're using, for example, libsodium, you'd want the Ed25519 to X25519 functions to convert the two. (Note that you need to operate over raw bytes to do this.)

In practice, you shouldn't do this. Use different keys for different purposes!