The Watcher

	
# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 108
# self = https://watcher.sour.is/conv/f7rdmuq

prologic

twtxt.net

12 Dec 20 23:54 UTC

Anyone here good with Go and feel like helping me build our a "Direct Messages" feature? I was going to pay someone on Upwork to do this, but I've received very few applicants (_just one!_) and they aren't that good (_stock standard crappy Bootstrap experience and no evidence of any experience with Go_).

prologic

twtxt.net

12 Dec 20 23:54 UTC

Anyone here good with Go and feel like helping me build our a "Direct Messages" feature? I was going to pay someone on Upwork to do this, but I've received very few applicants (_just one!_) and they aren't that good (_stock standard crappy Bootstrap experience and no evidence of any experience with Go_).

adi

f.adi.onl

13 Dec 20 00:31 UTC

@prologic I'm tight on cash and would like to learn some Go, but don't have much experience with it. 😛

adi@twtxt.net

twtxt.net

13 Dec 20 00:31 UTC

@prologic I'm tight on cash and would like to learn some Go, but don't have much experience with it. 😛

adi

twtxt.net

13 Dec 20 00:31 UTC

@prologic I'm tight on cash and would like to learn some Go, but don't have much experience with it. 😛

prologic

twtxt.net

13 Dec 20 00:57 UTC

If _only_ I had a way to privately message you 🤔 I'm willing to fork out a few 💵 for someone to help, my RSI is getting quite bad nowadays 😢 Writing Go isn't all that hard and this is pretty simple stuff really, for a PoC I'm just going to borrow from something like what Lobsters does and worry about e2e crypto later (_Goal: privacy from Pod Owner's prying eyes, not necessarily NSA-proof messaging 😋_) PM me on FreeNode if you like prologic or mail me at james ＠ mills · io_

prologic

twtxt.net

13 Dec 20 00:57 UTC

If _only_ I had a way to privately message you 🤔 I'm willing to fork out a few 💵 for someone to help, my RSI is getting quite bad nowadays 😢 Writing Go isn't all that hard and this is pretty simple stuff really, for a PoC I'm just going to borrow from something like what Lobsters does and worry about e2e crypto later (_Goal: privacy from Pod Owner's prying eyes, not necessarily NSA-proof messaging 😋_) PM me on FreeNode if you like prologic or mail me at james ＠ mills · io_

prologic@twtxt.net

twtxt.net

13 Dec 20 00:57 UTC

If _only_ I had a way to privately message you 🤔 I'm willing to fork out a few 💵 for someone to help, my RSI is getting quite bad nowadays 😢 Writing Go isn't all that hard and this is pretty simple stuff really, for a PoC I'm just going to borrow from something like what Lobsters does and worry about e2e crypto later (_Goal: privacy from Pod Owner's prying eyes, not necessarily NSA-proof messaging 😋_) PM me on FreeNode if you like prologic or mail me at james ＠ mills · io_

prologic

twtxt.net

13 Dec 20 01:01 UTC

This is what I have done so far...\n\n

\n\nAnd:\n\n

prologic@twtxt.net

twtxt.net

13 Dec 20 01:01 UTC

This is what I have done so far...\n\n

\n\nAnd:\n\n

prologic

twtxt.net

13 Dec 20 01:01 UTC

This is what I have done so far...

And:

prologic

twtxt.net

13 Dec 20 01:01 UTC

This is what I have done so far...

And:

xuu@txt.sour.is

txt.sour.is

13 Dec 20 05:03 UTC

@prologic 👋 I can take a stab at it when I am done with the changes I am working on.

xuu@dev.txt.sour.is

dev.txt.sour.is

13 Dec 20 05:03 UTC

@prologic 👋 I can take a stab at it when I am done with the changes I am working on.

xuu

txt.sour.is

13 Dec 20 05:03 UTC

@prologic 👋 I can take a stab at it when I am done with the changes I am working on.

xuu

txt.sour.is

13 Dec 20 05:03 UTC

@prologic 👋 I can take a stab at it when I am done with the changes I am working on.

prologic

twtxt.net

13 Dec 20 05:23 UTC

@xuu Oh that would be nice! I think @adi has volunteered as well. Basically let's get a first version working that _actually works_™ 😀

prologic@twtxt.net

twtxt.net

13 Dec 20 05:23 UTC

@xuu Oh that would be nice! I think @adi has volunteered as well. Basically let's get a first version working that _actually works_™ 😀

prologic

twtxt.net

13 Dec 20 05:23 UTC

@xuu Oh that would be nice! I think @adi has volunteered as well. Basically let's get a first version working that _actually works_™ 😀

xuu

txt.sour.is

13 Dec 20 19:22 UTC

i am guessing you are using some form of webmention to notify the target of the DM? which loads it into a store for the user to read?

xuu

txt.sour.is

13 Dec 20 19:22 UTC

i am guessing you are using some form of webmention to notify the target of the DM? which loads it into a store for the user to read?

xuu@dev.txt.sour.is

dev.txt.sour.is

13 Dec 20 19:22 UTC

i am guessing you are using some form of webmention to notify the target of the DM? which loads it into a store for the user to read?

xuu@txt.sour.is

txt.sour.is

13 Dec 20 19:22 UTC

i am guessing you are using some form of webmention to notify the target of the DM? which loads it into a store for the user to read?

xuu

txt.sour.is

13 Dec 20 20:13 UTC

@prologic for encryption. we can have browser/app generate ec25519 keypair. store the private on device and add pub to list of devices for the user on pod.

xuu@txt.sour.is

txt.sour.is

13 Dec 20 20:13 UTC

@prologic for encryption. we can have browser/app generate ec25519 keypair. store the private on device and add pub to list of devices for the user on pod.

xuu@dev.txt.sour.is

dev.txt.sour.is

13 Dec 20 20:13 UTC

@prologic for encryption. we can have browser/app generate ec25519 keypair. store the private on device and add pub to list of devices for the user on pod.

xuu

txt.sour.is

13 Dec 20 20:13 UTC

@prologic for encryption. we can have browser/app generate ec25519 keypair. store the private on device and add pub to list of devices for the user on pod.

xuu

txt.sour.is

13 Dec 20 20:14 UTC

@prologic sender generates an AES key encrypts message. gets the device list for user and encrypts key for each device. sends the encryptedkeys+cypertext.

xuu@dev.txt.sour.is

dev.txt.sour.is

13 Dec 20 20:14 UTC

@prologic sender generates an AES key encrypts message. gets the device list for user and encrypts key for each device. sends the encryptedkeys+cypertext.

xuu

txt.sour.is

13 Dec 20 20:14 UTC

@prologic sender generates an AES key encrypts message. gets the device list for user and encrypts key for each device. sends the encryptedkeys+cypertext.

xuu@txt.sour.is

txt.sour.is

13 Dec 20 20:14 UTC

@prologic sender generates an AES key encrypts message. gets the device list for user and encrypts key for each device. sends the encryptedkeys+cypertext.

xuu

txt.sour.is

13 Dec 20 20:15 UTC

@prologic device gets the cypertext and uses it's device key to decrypt one of the keys and then decrypts the cypertext.

xuu@dev.txt.sour.is

dev.txt.sour.is

13 Dec 20 20:15 UTC

@prologic device gets the cypertext and uses it's device key to decrypt one of the keys and then decrypts the cypertext.

xuu@txt.sour.is

txt.sour.is

13 Dec 20 20:15 UTC

@prologic device gets the cypertext and uses it's device key to decrypt one of the keys and then decrypts the cypertext.

xuu

txt.sour.is

13 Dec 20 20:15 UTC

@prologic device gets the cypertext and uses it's device key to decrypt one of the keys and then decrypts the cypertext.

xuu

txt.sour.is

13 Dec 20 20:15 UTC

@prologic pod should probably track revocation of device keys and delete the encryptedkeys that are paired with revoked keys

xuu

txt.sour.is

13 Dec 20 20:15 UTC

@prologic pod should probably track revocation of device keys and delete the encryptedkeys that are paired with revoked keys

xuu@dev.txt.sour.is

dev.txt.sour.is

13 Dec 20 20:15 UTC

@prologic pod should probably track revocation of device keys and delete the encryptedkeys that are paired with revoked keys

xuu@txt.sour.is

txt.sour.is

13 Dec 20 20:15 UTC

@prologic pod should probably track revocation of device keys and delete the encryptedkeys that are paired with revoked keys

xuu

txt.sour.is

13 Dec 20 20:15 UTC

@prologic def would be a wider discussion on preventing the pod from adding its own key to a users device list. Or using device keys to authenticate instead of user/pass.

xuu@txt.sour.is

txt.sour.is

13 Dec 20 20:15 UTC

@prologic def would be a wider discussion on preventing the pod from adding its own key to a users device list. Or using device keys to authenticate instead of user/pass.

xuu@dev.txt.sour.is

dev.txt.sour.is

13 Dec 20 20:15 UTC

@prologic def would be a wider discussion on preventing the pod from adding its own key to a users device list. Or using device keys to authenticate instead of user/pass.

xuu

txt.sour.is

13 Dec 20 20:15 UTC

@prologic def would be a wider discussion on preventing the pod from adding its own key to a users device list. Or using device keys to authenticate instead of user/pass.

prologic

twtxt.net

13 Dec 20 21:50 UTC

> i am guessing you are using some form of webmention to notify the target of the DM? which loads it into a store for the user to read?

No webmention(s) are only used to perform an internal event on a pod that causes the @twtxt bot to post about it.

prologic

twtxt.net

13 Dec 20 21:50 UTC

> i am guessing you are using some form of webmention to notify the target of the DM? which loads it into a store for the user to read?

No webmention(s) are only used to perform an internal event on a pod that causes the @twtxt bot to post about it.

prologic

twtxt.net

13 Dec 20 21:50 UTC

> i am guessing you are using some form of webmention to notify the target of the DM? which loads it into a store for the user to read?\n\nNo webmention(s) are only used to perform an internal event on a pod that causes the @twtxt bot to post about it.

prologic@twtxt.net

twtxt.net

13 Dec 20 21:50 UTC

> i am guessing you are using some form of webmention to notify the target of the DM? which loads it into a store for the user to read?\n\nNo webmention(s) are only used to perform an internal event on a pod that causes the @twtxt bot to post about it.

adi

twtxt.net

13 Dec 20 21:55 UTC

@xuu @prologic But if I get a new device, how can I read my old messages?

adi

f.adi.onl

13 Dec 20 21:55 UTC

@xuu @prologic But if I get a new device, how can I read my old messages?

adi@twtxt.net

twtxt.net

13 Dec 20 21:55 UTC

@xuu @prologic But if I get a new device, how can I read my old messages?

prologic@twtxt.net

twtxt.net

13 Dec 20 21:56 UTC

@xuu re encryption, that sounds reasonable actually. But instead of AES, let's use Salt/NaCL. I put together this library and tool which uses ED25519 for your "device key pair" / or "identity key pair" and uses Curve25519, Salsa20, and Poly1305 for the actual encryption (_normal box.Seal()_). The only downside at the moment is single recipient only (_I borrowed most of this code from someone else_). But this lets us use TweetNaCL

prologic

twtxt.net

13 Dec 20 21:56 UTC

@xuu re encryption, that sounds reasonable actually. But instead of AES, let's use Salt/NaCL. I put together this library and tool which uses ED25519 for your "device key pair" / or "identity key pair" and uses Curve25519, Salsa20, and Poly1305 for the actual encryption (_normal box.Seal()_). The only downside at the moment is single recipient only (_I borrowed most of this code from someone else_). But this lets us use TweetNaCL

prologic

twtxt.net

13 Dec 20 21:56 UTC

@xuu re encryption, that sounds reasonable actually. But instead of AES, let's use Salt/NaCL. I put together this library and tool which uses ED25519 for your "device key pair" / or "identity key pair" and uses Curve25519, Salsa20, and Poly1305 for the actual encryption (_normal box.Seal()_). The only downside at the moment is single recipient only (_I borrowed most of this code from someone else_). But this lets us use TweetNaCL

prologic@twtxt.net

twtxt.net

13 Dec 20 22:14 UTC

@adi @xuu I'm not sure this is something we can solve. The same problem exists with Signal, GPG and _ptobabpy_ any other kind of public key crypto protocol/system. If you lose your keys, you can no longer read old messages.

prologic

twtxt.net

13 Dec 20 22:14 UTC

@adi @xuu I'm not sure this is something we can solve. The same problem exists with Signal, GPG and _ptobabpy_ any other kind of public key crypto protocol/system. If you lose your keys, you can no longer read old messages.

prologic

twtxt.net

13 Dec 20 22:14 UTC

@adi @xuu I'm not sure this is something we can solve. The same problem exists with Signal, GPG and _ptobabpy_ any other kind of public key crypto protocol/system. If you lose your keys, you can no longer read old messages.

prologic

twtxt.net

13 Dec 20 22:16 UTC

@xuu

> def would be a wider discussion on preventing the pod from adding its own key to a users device list

Can we not have clients sign their own public keys before listing them on their Pod's account?

prologic

twtxt.net

13 Dec 20 22:16 UTC

@xuu\n\n> def would be a wider discussion on preventing the pod from adding its own key to a users device list\n\nCan we not have clients sign their own public keys before listing them on their Pod's account?

prologic

twtxt.net

13 Dec 20 22:16 UTC

@xuu

> def would be a wider discussion on preventing the pod from adding its own key to a users device list

Can we not have clients sign their own public keys before listing them on their Pod's account?

prologic@twtxt.net

twtxt.net

13 Dec 20 22:16 UTC

@xuu\n\n> def would be a wider discussion on preventing the pod from adding its own key to a users device list\n\nCan we not have clients sign their own public keys before listing them on their Pod's account?

xuu

txt.sour.is

13 Dec 20 22:31 UTC

@prologic
> Can we not have clients sign their own public keys before listing them on their Pod’s account?

Yeah.. we probably could. when they setup an account they create a master key that signs any subsequent keys. or chain of signatures like keybase does.

xuu@txt.sour.is

txt.sour.is

13 Dec 20 22:31 UTC

@prologic \n> Can we not have clients sign their own public keys before listing them on their Pod’s account?\n\nYeah.. we probably could. when they setup an account they create a master key that signs any subsequent keys. or chain of signatures like keybase does.

xuu

txt.sour.is

13 Dec 20 22:31 UTC

@prologic \n> Can we not have clients sign their own public keys before listing them on their Pod’s account?\n\nYeah.. we probably could. when they setup an account they create a master key that signs any subsequent keys. or chain of signatures like keybase does.

xuu@dev.txt.sour.is

dev.txt.sour.is

13 Dec 20 22:31 UTC

@prologic
> Can we not have clients sign their own public keys before listing them on their Pod’s account?

Yeah.. we probably could. when they setup an account they create a master key that signs any subsequent keys. or chain of signatures like keybase does.

xuu

txt.sour.is

13 Dec 20 22:31 UTC

@prologic
> Can we not have clients sign their own public keys before listing them on their Pod’s account?

Yeah.. we probably could. when they setup an account they create a master key that signs any subsequent keys. or chain of signatures like keybase does.

xuu

txt.sour.is

13 Dec 20 22:46 UTC

@prologic Ok.. so using NaCL boxes. yeah its just a combo of using secretbox with a generated key/nonce. and then using the pubkey box to encrypt the key/nonce for each device.

xuu@dev.txt.sour.is

dev.txt.sour.is

13 Dec 20 22:46 UTC

@prologic Ok.. so using NaCL boxes. yeah its just a combo of using secretbox with a generated key/nonce. and then using the pubkey box to encrypt the key/nonce for each device.

xuu@txt.sour.is

txt.sour.is

13 Dec 20 22:46 UTC

@prologic Ok.. so using NaCL boxes. yeah its just a combo of using secretbox with a generated key/nonce. and then using the pubkey box to encrypt the key/nonce for each device.

xuu

txt.sour.is

13 Dec 20 22:46 UTC

@prologic Ok.. so using NaCL boxes. yeah its just a combo of using secretbox with a generated key/nonce. and then using the pubkey box to encrypt the key/nonce for each device.

prologic

twtxt.net

13 Dec 20 22:54 UTC

Yup pretty much. It's all supported in cryptutils and it _should_ be easy to port the same code _verbatim_ using TweetNaCL; which should then work nicely on the Web App (_client-side_) and Mobile App (_using Flutter_)

prologic

twtxt.net

13 Dec 20 22:54 UTC

Yup pretty much. It's all supported in cryptutils and it _should_ be easy to port the same code _verbatim_ using TweetNaCL; which should then work nicely on the Web App (_client-side_) and Mobile App (_using Flutter_)

prologic@twtxt.net

twtxt.net

13 Dec 20 22:54 UTC

Yup pretty much. It's all supported in cryptutils and it _should_ be easy to port the same code _verbatim_ using TweetNaCL; which should then work nicely on the Web App (_client-side_) and Mobile App (_using Flutter_)

prologic

twtxt.net

13 Dec 20 22:56 UTC

@xii Alternatively we can decide that "group messages" are out-of-scope and then we don't have to do any extra work, the salt CLI tool in cryptutils _already_ does all the work we need. We just use the same functions and target multiple device public keys. If you install the CLI we can even do this over Twtxt to see how it plays out? :)

prologic

twtxt.net

13 Dec 20 22:56 UTC

@xii Alternatively we can decide that "group messages" are out-of-scope and then we don't have to do any extra work, the salt CLI tool in cryptutils _already_ does all the work we need. We just use the same functions and target multiple device public keys. If you install the CLI we can even do this over Twtxt to see how it plays out? :)

prologic@twtxt.net

twtxt.net

13 Dec 20 22:56 UTC

@xii Alternatively we can decide that "group messages" are out-of-scope and then we don't have to do any extra work, the salt CLI tool in cryptutils _already_ does all the work we need. We just use the same functions and target multiple device public keys. If you install the CLI we can even do this over Twtxt to see how it plays out? :)

prologic

twtxt.net

13 Dec 20 22:56 UTC

I _would_ need an out-of-band way to verify your public key's fingerprint though 🤣

prologic@twtxt.net

twtxt.net

13 Dec 20 22:56 UTC

I _would_ need an out-of-band way to verify your public key's fingerprint though 🤣

prologic

twtxt.net

13 Dec 20 22:56 UTC

I _would_ need an out-of-band way to verify your public key's fingerprint though 🤣

prologic@twtxt.net

twtxt.net

13 Dec 20 22:59 UTC

For example, this is for @adi :\n\n

\n-----BEGIN CRYPTUTIL SIGNED AND ENCRYPTED MESSAGE-----\nM3QAfkSbutLPe58ALjY+ENO8kbpjne3EjXVu9kIivl0thk2hRqcL/ZhBkQBxivh6\nJXS507BO26UbUDz0vd2xGMl8TN/EcWNVtm4PGyTPh+BOolKTy+UR0d1++ZeXc2P4\n3TvaT9aV5eShx7gMps4TmNkcOGwSwLtBHxKicwkAj9Ox7f5EHdGnDQzAOJAW69c/\ns3iAdSIDdXgcumzy+LSg+QaDWdV4SEGhcpA9Ka+TNXbGzOIJ6oDk6P8wFk6JnwRR\nu+A=\n-----END CRYPTUTIL SIGNED AND ENCRYPTED MESSAGE-----\n

prologic

twtxt.net

13 Dec 20 22:59 UTC

For example, this is for @adi :


-----BEGIN CRYPTUTIL SIGNED AND ENCRYPTED MESSAGE-----
M3QAfkSbutLPe58ALjY+ENO8kbpjne3EjXVu9kIivl0thk2hRqcL/ZhBkQBxivh6
JXS507BO26UbUDz0vd2xGMl8TN/EcWNVtm4PGyTPh+BOolKTy+UR0d1++ZeXc2P4
3TvaT9aV5eShx7gMps4TmNkcOGwSwLtBHxKicwkAj9Ox7f5EHdGnDQzAOJAW69c/
s3iAdSIDdXgcumzy+LSg+QaDWdV4SEGhcpA9Ka+TNXbGzOIJ6oDk6P8wFk6JnwRR
u+A=
-----END CRYPTUTIL SIGNED AND ENCRYPTED MESSAGE-----

prologic

twtxt.net

13 Dec 20 22:59 UTC

For example, this is for @adi :\n\n

\n-----BEGIN CRYPTUTIL SIGNED AND ENCRYPTED MESSAGE-----\nM3QAfkSbutLPe58ALjY+ENO8kbpjne3EjXVu9kIivl0thk2hRqcL/ZhBkQBxivh6\nJXS507BO26UbUDz0vd2xGMl8TN/EcWNVtm4PGyTPh+BOolKTy+UR0d1++ZeXc2P4\n3TvaT9aV5eShx7gMps4TmNkcOGwSwLtBHxKicwkAj9Ox7f5EHdGnDQzAOJAW69c/\ns3iAdSIDdXgcumzy+LSg+QaDWdV4SEGhcpA9Ka+TNXbGzOIJ6oDk6P8wFk6JnwRR\nu+A=\n-----END CRYPTUTIL SIGNED AND ENCRYPTED MESSAGE-----\n

prologic

twtxt.net

13 Dec 20 22:59 UTC

For example, this is for @adi :


-----BEGIN CRYPTUTIL SIGNED AND ENCRYPTED MESSAGE-----
M3QAfkSbutLPe58ALjY+ENO8kbpjne3EjXVu9kIivl0thk2hRqcL/ZhBkQBxivh6
JXS507BO26UbUDz0vd2xGMl8TN/EcWNVtm4PGyTPh+BOolKTy+UR0d1++ZeXc2P4
3TvaT9aV5eShx7gMps4TmNkcOGwSwLtBHxKicwkAj9Ox7f5EHdGnDQzAOJAW69c/
s3iAdSIDdXgcumzy+LSg+QaDWdV4SEGhcpA9Ka+TNXbGzOIJ6oDk6P8wFk6JnwRR
u+A=
-----END CRYPTUTIL SIGNED AND ENCRYPTED MESSAGE-----

xuu

txt.sour.is

13 Dec 20 23:14 UTC

@prologic I use https://key.sour.is/id/me@sour.is

> I would need an out-of-band way to verify your public key’s fingerprint though 🤣

xuu

txt.sour.is

13 Dec 20 23:14 UTC

@prologic I use https://key.sour.is/id/me@sour.is

> I would need an out-of-band way to verify your public key’s fingerprint though 🤣

xuu@txt.sour.is

txt.sour.is

13 Dec 20 23:14 UTC

@prologic I use https://key.sour.is/id/me@sour.is\n\n> I would need an out-of-band way to verify your public key’s fingerprint though 🤣

xuu@dev.txt.sour.is

dev.txt.sour.is

13 Dec 20 23:14 UTC

@prologic I use https://key.sour.is/id/me@sour.is

> I would need an out-of-band way to verify your public key’s fingerprint though 🤣

xuu

txt.sour.is

13 Dec 20 23:14 UTC

@prologic I use https://key.sour.is/id/me@sour.is\n\n> I would need an out-of-band way to verify your public key’s fingerprint though 🤣

adi

f.adi.onl

13 Dec 20 23:21 UTC

@prologic Can't decrypt that. 😛

adi@twtxt.net

twtxt.net

13 Dec 20 23:21 UTC

@prologic Can't decrypt that. 😛

adi

twtxt.net

13 Dec 20 23:21 UTC

@prologic Can't decrypt that. 😛

prologic

twtxt.net

13 Dec 20 23:29 UTC

@adi What about this?


-----BEGIN CRYPTUTIL SIGNED AND ENCRYPTED MESSAGE-----
HNVAUkSQ/sRljsRENHzBW8xF81kKVaZ4xzixRrOfIU3ZzsURSfcik8ObodK8LF3m
4rsdUrL7JpbE0v7wvHm6YmpwPByvAtHGJQO1kQ/TcWHfrBex+yL1VmN8xS7HhfSb
H85D8Ge6CuaXSWerjTz1LHo7dYk1o1Y83f7MGrjDJgghWA6uPMn660GOk73DbUaA
HCQo0w3fiolLL5Y=
-----END CRYPTUTIL SIGNED AND ENCRYPTED MESSAGE-----

prologic

twtxt.net

13 Dec 20 23:29 UTC

@adi What about this?


-----BEGIN CRYPTUTIL SIGNED AND ENCRYPTED MESSAGE-----
HNVAUkSQ/sRljsRENHzBW8xF81kKVaZ4xzixRrOfIU3ZzsURSfcik8ObodK8LF3m
4rsdUrL7JpbE0v7wvHm6YmpwPByvAtHGJQO1kQ/TcWHfrBex+yL1VmN8xS7HhfSb
H85D8Ge6CuaXSWerjTz1LHo7dYk1o1Y83f7MGrjDJgghWA6uPMn660GOk73DbUaA
HCQo0w3fiolLL5Y=
-----END CRYPTUTIL SIGNED AND ENCRYPTED MESSAGE-----

prologic

twtxt.net

13 Dec 20 23:29 UTC

@adi What about this?\n\n

\n-----BEGIN CRYPTUTIL SIGNED AND ENCRYPTED MESSAGE-----\nHNVAUkSQ/sRljsRENHzBW8xF81kKVaZ4xzixRrOfIU3ZzsURSfcik8ObodK8LF3m\n4rsdUrL7JpbE0v7wvHm6YmpwPByvAtHGJQO1kQ/TcWHfrBex+yL1VmN8xS7HhfSb\nH85D8Ge6CuaXSWerjTz1LHo7dYk1o1Y83f7MGrjDJgghWA6uPMn660GOk73DbUaA\nHCQo0w3fiolLL5Y=\n-----END CRYPTUTIL SIGNED AND ENCRYPTED MESSAGE-----\n

prologic@twtxt.net

twtxt.net

13 Dec 20 23:29 UTC

@adi What about this?\n\n

\n-----BEGIN CRYPTUTIL SIGNED AND ENCRYPTED MESSAGE-----\nHNVAUkSQ/sRljsRENHzBW8xF81kKVaZ4xzixRrOfIU3ZzsURSfcik8ObodK8LF3m\n4rsdUrL7JpbE0v7wvHm6YmpwPByvAtHGJQO1kQ/TcWHfrBex+yL1VmN8xS7HhfSb\nH85D8Ge6CuaXSWerjTz1LHo7dYk1o1Y83f7MGrjDJgghWA6uPMn660GOk73DbUaA\nHCQo0w3fiolLL5Y=\n-----END CRYPTUTIL SIGNED AND ENCRYPTED MESSAGE-----\n

adi

f.adi.onl

13 Dec 20 23:32 UTC

@prologic Same, can't decrypt it.

adi@twtxt.net

twtxt.net

13 Dec 20 23:32 UTC

@prologic Same, can't decrypt it.

adi

twtxt.net

13 Dec 20 23:32 UTC

@prologic Same, can't decrypt it.

xuu@dev.txt.sour.is

dev.txt.sour.is

13 Dec 20 23:36 UTC

@xuu @prologic This? Fingerprint: 161c614f08e4ed4d1c8e5410f8c457e6878574dbab7c9ac25d474de67db1bdad

xuu@txt.sour.is

txt.sour.is

13 Dec 20 23:36 UTC

@xuu @prologic This? Fingerprint: 161c614f08e4ed4d1c8e5410f8c457e6878574dbab7c9ac25d474de67db1bdad

xuu

txt.sour.is

13 Dec 20 23:36 UTC

@xuu @prologic This? Fingerprint: 161c614f08e4ed4d1c8e5410f8c457e6878574dbab7c9ac25d474de67db1bdad

xuu

txt.sour.is

13 Dec 20 23:36 UTC

@xuu @prologic This? Fingerprint: 161c614f08e4ed4d1c8e5410f8c457e6878574dbab7c9ac25d474de67db1bdad

prologic

twtxt.net

13 Dec 20 23:41 UTC

@xuu Looks legit :)

prologic@twtxt.net

twtxt.net

13 Dec 20 23:41 UTC

@xuu Looks legit :)

prologic

twtxt.net

13 Dec 20 23:41 UTC

@xuu Looks legit :)

prologic

twtxt.net

14 Dec 20 00:08 UTC

@xuu I _guess _ I need your public key salt -export - 😀

Here's mine:


-----BEGIN CRYPTUTIL VERIFIED KEY-----
MIHMBEBS3sgNEUEhGu8K7pgxT0b4cRpxdlRhteO8ZEsMawvJe7snRFMNThuOKnZo
MEc+VvTOeLYGiw1ZFG6XbY9WyvQcBEBS3sgNEUEhGu8K7pgxT0b4cRpxdlRhteO8
ZEsMawvJe7snRFMNThuOKnZoMEc+VvTOeLYGiw1ZFG6XbY9WyvQcAgRf1h2qBECA
lBBT/KRNLYmcD8YZAkb8DoEA/IdiH+0RmIDNPM87TVYme8rJ/8UGssPL4IX/1s+m
7J6dL0izLNuVaANEDsgF
-----END CRYPTUTIL VERIFIED KEY-----

And emailed you (_out-of-band_) the key's fingerprint for you to confirm/match :D

salt -u -import - to import

prologic

twtxt.net

14 Dec 20 00:08 UTC

@xuu I _guess _ I need your public key salt -export - 😀\n\nHere's mine:\n\n

\n-----BEGIN CRYPTUTIL VERIFIED KEY-----\nMIHMBEBS3sgNEUEhGu8K7pgxT0b4cRpxdlRhteO8ZEsMawvJe7snRFMNThuOKnZo\nMEc+VvTOeLYGiw1ZFG6XbY9WyvQcBEBS3sgNEUEhGu8K7pgxT0b4cRpxdlRhteO8\nZEsMawvJe7snRFMNThuOKnZoMEc+VvTOeLYGiw1ZFG6XbY9WyvQcAgRf1h2qBECA\nlBBT/KRNLYmcD8YZAkb8DoEA/IdiH+0RmIDNPM87TVYme8rJ/8UGssPL4IX/1s+m\n7J6dL0izLNuVaANEDsgF\n-----END CRYPTUTIL VERIFIED KEY-----\n

\n\nAnd emailed you (_out-of-band_) the key's fingerprint for you to confirm/match :D\n\nsalt -u -import - to import

prologic@twtxt.net

twtxt.net

14 Dec 20 00:08 UTC

@xuu I _guess _ I need your public key salt -export - 😀\n\nHere's mine:\n\n

\n-----BEGIN CRYPTUTIL VERIFIED KEY-----\nMIHMBEBS3sgNEUEhGu8K7pgxT0b4cRpxdlRhteO8ZEsMawvJe7snRFMNThuOKnZo\nMEc+VvTOeLYGiw1ZFG6XbY9WyvQcBEBS3sgNEUEhGu8K7pgxT0b4cRpxdlRhteO8\nZEsMawvJe7snRFMNThuOKnZoMEc+VvTOeLYGiw1ZFG6XbY9WyvQcAgRf1h2qBECA\nlBBT/KRNLYmcD8YZAkb8DoEA/IdiH+0RmIDNPM87TVYme8rJ/8UGssPL4IX/1s+m\n7J6dL0izLNuVaANEDsgF\n-----END CRYPTUTIL VERIFIED KEY-----\n

\n\nAnd emailed you (_out-of-band_) the key's fingerprint for you to confirm/match :D\n\nsalt -u -import - to import

prologic

twtxt.net

14 Dec 20 00:08 UTC

@xuu I _guess _ I need your public key salt -export - 😀

Here's mine:


-----BEGIN CRYPTUTIL VERIFIED KEY-----
MIHMBEBS3sgNEUEhGu8K7pgxT0b4cRpxdlRhteO8ZEsMawvJe7snRFMNThuOKnZo
MEc+VvTOeLYGiw1ZFG6XbY9WyvQcBEBS3sgNEUEhGu8K7pgxT0b4cRpxdlRhteO8
ZEsMawvJe7snRFMNThuOKnZoMEc+VvTOeLYGiw1ZFG6XbY9WyvQcAgRf1h2qBECA
lBBT/KRNLYmcD8YZAkb8DoEA/IdiH+0RmIDNPM87TVYme8rJ/8UGssPL4IX/1s+m
7J6dL0izLNuVaANEDsgF
-----END CRYPTUTIL VERIFIED KEY-----

And emailed you (_out-of-band_) the key's fingerprint for you to confirm/match :D

salt -u -import - to import