Yes @prologic@twtxt.net, I will be cross-posting to twtxt.net, following the POSSE principle https://indieweb.org/POSSE . #vjdyupq

Yes @prologic@twtxt.net, I will be cross-posting to twtxt.net, following the POSSE principle https://indieweb.org/POSSE . #vjdyupq

that’s it. I’m finding another twtxt client.

Atelophobia by @hecanjog@hecanjog.com [[https://hecanjog.bandcamp.com/album/atelophobia]] #links #bandcamp

@prologic@twtxt.net when its ready.. this is still in beta.

@prologic@twtxt.net It did, posting from txtnish, nice to know. #utwnv7q

@prologic@twtxt.net It did, posting from txtnish, nice to know. #utwnv7q

@prologic@twtxt.net Testing if this will be added to the thread just adding the hashtag. #utwnv7q

@prologic@twtxt.net Testing if this will be added to the thread just adding the hashtag. #utwnv7q

@prologic@twtxt.net Txtnish adds a 28 character timestamp to the message, so in Bash: tweet=tail -1 the current twtxt.txt file and then pipe echo body=${tweet:28} to twt.

@prologic@twtxt.net Txtnish adds a 28 character timestamp to the message, so in Bash: tweet=tail -1 the current twtxt.txt file and then pipe echo body=${tweet:28} to twt.

Using twt as a post_tweet_hook for txtnish to re-post to a twtxt “pod” https://github.com/jointwt/twtxt

Using twt as a post_tweet_hook for txtnish to re-post to a twtxt “pod” https://github.com/jointwt/twtxt

Seems like twtxt-el does not retrieve a timeline. #emacs

Seems like twtxt-el does not retrieve a timeline. #emacs

Testing twtxt-el by posting this status message.

Testing twtxt-el by posting this status message.

@prologic@twtxt.net yeah it would replace rice. best part is that it’s in the go build step so you don’t need to do any prep work with make.

@prologic@twtxt.net after stewing on it. I really like the idea of a wiki. throw it on the roadmap after DMs 😆

@prologic@twtxt.net (#keh22ka) maybe a custom linking method on a pod level? like can pass a template that gets translated. ex https://{domain}/wiki/{nick}/{tag} + !somepage -> https://sour.is/wiki/xuu/somepage

@prologic@twtxt.net found it!

2020-07-25T00:52:27.000000Z a new twtxt/weewiki feature: any word starting with ‘!’ will translate to an internal weewiki reference in my HTML renderer. Example: here is my !wiki_index

@prologic@twtxt.net https://txt.sour.is/twt/cwqmygq

@prologic@twtxt.net I see them is why I ask. like here #cwqmygq they use both hashtag and bangtag?

@prologic@twtxt.net 😁 that is me testing locally. does it notify you somehow when I follow?

@prologic@twtxt.net do you have any info on how the ‘!’ tags are supposed to work? are they just a different kind of hash tag?

Setting up txtnish on the Linux side of one of my computers that runs CloudReady. #twtxt #txtnish #chromeos

Setting up txtnish on the Linux side of one of my computers that runs CloudReady. #twtxt #txtnish #chromeos

@prologic@twtxt.net one.. kinda sorta option would be to tailor a workflow for each of the archs.. see https://github.com/JonLundy/twtxt/runs/1568071072?check_suite_focus=true

WEBMENTION: @xuu@txt.sour.is on https://twtxt.net/twt/rxjzdwa

@xuu@txt.sour.is @prologic@twtxt.net oh.. you are.. maybe i don’t understand the issue with building?

@prologic@twtxt.net have you tried using the macos github build environment? looks like they have a windows one too.

@prologic@twtxt.net you think its time the version to get bumped? :)

WEBMENTION: @xuu@txt.sour.is on https://twtxt.net/twt/wyoav2q

@xuu@txt.sour.is @prologic@twtxt.net had to up my twt size a bit.

@prologic@twtxt.net

-----BEGIN CRYPTUTIL ENCRYPTED MESSAGE-----
l0GwFAQpx3ed+bZlcQ+pexbynFzZOm8EI/FivGbWQ16whyTkToVv8S2GSAjrsJoT
37MdaBDpoitli/f/aP130b6O6SnK/LdHHJ1DTvWgxB14sq9b4mRtk7HvYzA=
-----END CRYPTUTIL ENCRYPTED MESSAGE-----

@xuu@txt.sour.is @prologic@twtxt.net This? Fingerprint: 161c614f08e4ed4d1c8e5410f8c457e6878574dbab7c9ac25d474de67db1bdad

@prologic@twtxt.net 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 🤣

@prologic@twtxt.net 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

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.

WEBMENTION: @xuu@txt.sour.is on https://twtxt.net/twt/raylsra

@pbatch@pbat.ch I had that happen to me too a couple times! I kept thinking it was my isp or something. i had to run the command a couple times to see everything

@lucidiot@tilde.town BEST SATURDAY

@prologic@twtxt.net 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 pod should probably track revocation of device keys and delete the encryptedkeys that are paired with revoked keys

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

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

@prologic@twtxt.net 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.

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

@prologic@twtxt.net my bad.. my next one is more fun.

WEBMENTION: @xuu@txt.sour.is on https://twtxt.net/twt/xkpbn6a