$ printf "%s\t%s\t%s" "https://example.com/twtxt.txt" "2024-09-29T13:30:00Z" "Hello World!" | sha256sum | awk '{ print $1 }' | xxd -r -p | base64 | head -c 12
UWVFdUXtvoLS
$ printf "%s\t%s\t%s" "https://example.com/twtxt.txt" "2024-09-29T13:30:00Z" "Hello World!" | sha256sum | awk '{ print $1 }' | xxd -r -p | base64 | head -c 12
UWVFdUXtvoLS
sha256sum vs. b2sum. Neither is more complicated than the other.
sha256sum vs. b2sum. Neither is more complicated than the other.
=> https://gist.mills.io/prologic/194993e7db04498fa0e8d00a528f7be6
e.g: (_turns out @xuu is right about Blak2b being easy/simple too!_):
$ printf "%s\\t%s\\t%s" "https://example.com/twtxt.txt" "2024-09-29T13:30:00Z" "Hello World!" | b2sum -l 32 -t | awk '{ print $1 }'
7b8b79dd
=> https://gist.mills.io/prologic/194993e7db04498fa0e8d00a528f7be6
e.g: (_turns out @xuu is right about Blak2b being easy/simple too!_):
$ printf "%s\t%s\t%s" "https://example.com/twtxt.txt" "2024-09-29T13:30:00Z" "Hello World!" | b2sum -l 32 -t | awk '{ print $1 }'
7b8b79dd
=> https://gist.mills.io/prologic/194993e7db04498fa0e8d00a528f7be6
e.g: (_turns out @xuu is right about Blak2b being easy/simple too!_):
$ printf "%s\t%s\t%s" "https://example.com/twtxt.txt" "2024-09-29T13:30:00Z" "Hello World!" | b2sum -l 32 -t | awk '{ print $1 }'
7b8b79dd
> iirc in twtxt v2 it starts prohibited
This is not true. There are no issues supporting fetching feeds via Gemini/Gopher. This is totally fine. What will likely happen is "recommendations" and "drawbacks of using Gemini/Gopher"
> iirc in twtxt v2 it starts prohibited
This is not true. There are no issues supporting fetching feeds via Gemini/Gopher. This is totally fine. What will likely happen is "recommendations" and "drawbacks of using Gemini/Gopher"
> Ah, 16Β°Cβ¦ what dreams are made of! π
I'd like it to be a nice cool 16Β°C here π€£
> Ah, 16Β°Cβ¦ what dreams are made of! π
I'd like it to be a nice cool 16Β°C here π€£
twet and continue to improve it. It's an "okay" Twtxt cli client, but it needs a bit more work π
twet and continue to improve it. It's an "okay" Twtxt cli client, but it needs a bit more work π
twet π€¦ββοΈ
twet π€¦ββοΈ
Now we have a situation where folks participating in a "conversation" (thread) with appropriate clients can automatically detect edits with almost 100% accuracy by mere fact that the next time they fetch a feed that contains an edit, they now see two versions of the Twt with two different hashes, but identical timestamps.
You can use the fetch time to approximate a "version number" and deal with the display (UX) appropriately.
I can't believe I didn't think of this before π€¦ββοΈ
Now we have a situation where folks participating in a "conversation" (thread) with appropriate clients can automatically detect edits with almost 100% accuracy by mere fact that the next time they fetch a feed that contains an edit, they now see two versions of the Twt with two different hashes, but identical timestamps.
You can use the fetch time to approximate a "version number" and deal with the display (UX) appropriately.
I can't believe I didn't think of this before π€¦ββοΈ
=> twtxt.dev
π₯³=