But keeping a good eye on Zen Browser's progress.
Super simple:
Making a reply:
0. If yarn has one use that. (Maybe do collision check?)
1. Make hash of twt raw no truncation.
2. Check local cache for shortest without collision
- in SQL:
select len(subject) where head_full_hash like subject || '%' Threading:
1. Get full hash of head twt
2. Search for twts
- in SQL:
head_full_hash like subject || '%' and created_on > head_timestamp The assumption being replies will be for the most recent head. If replying to an older one it will use a longer hash.
Super simple:
Making a reply:
0. If yarn has one use that. (Maybe do collision check?)
1. Make hash of twt raw no truncation.
2. Check local cache for shortest without collision
- in SQL:
select len(subject) where head_full_hash like subject || '%' Threading:
1. Get full hash of head twt
2. Search for twts
- in SQL:
head_full_hash like subject || '%' and created_on > head_timestamp The assumption being replies will be for the most recent head. If replying to an older one it will use a longer hash.
- Based on Firefox instead of Chromium.
- Got tiling pans when you need them... (just like a tiling window manager).
- I can hide the Tabs and Nav-Bar with a single short-cut!! AKA Compact Mode ...
- Based on Firefox instead of Chromium.
- Got tiling pans when you need them... (just like a tiling window manager).
- I can hide the Tabs and Nav-Bar with a single short-cut!! AKA Compact Mode ...
- Based on Firefox instead of Chromium.
- Got tiling pans when you need them... (just like a tiling window manager).
- I can hide the Tabs and Nav-Bar with a single short-cut!! AKA Compact Mode ...
> /ME slow claps...
> /ME slow claps...
> /ME slow claps...
- Update the Twt Hash extension.
- Increase its truncation from 7 to 12
@xuu is right about quite a few things, and I'd love it if he wrote up the dynamic hash size proposal, but I'm inclined to just increase the length in the first place mostly because my own client
yarnd doesn't even store the full hashes in the first place 🤦♂️ (I thinnk)
- Update the Twt Hash extension.
- Increase its truncation from 7 to 12
@xuu is right about quite a few things, and I'd love it if he wrote up the dynamic hash size proposal, but I'm inclined to just increase the length in the first place mostly because my own client
yarnd doesn't even store the full hashes in the first place 🤦♂️ (I thinnk)
I have the feeling that the hashing part is the most important one that should be sorted first.
Using Mastodon as a---albeit poorly---contrast, they set their road-map, and clients (even other server implementations!) that want to cater/communicate with it using similar APIs will have to adjust. No other way. That doesn't apply to twtxt.
I think the incremental changes that have been made to twtxt happened kind of slowly for that reason.
kept it an easy feel. fun run.
#running
kept it an easy feel. fun run.
#running
kept it an easy feel. fun run.
#running
base64 more desirable than base32? I noticed I get alphanumeric replacing base64 with base32.
Rofi, now I can just play with this one.
Rofi, now I can just play with this one.
Rofi, now I can just play with this one.
$ 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
$ 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.
sha256sum is much less complicated. :-D
printf '%s\\n%s\\n%s' 'https://example.com/twtxt.txt' '2020-12-09T15:38:42Z' 'The twt hash now uses the RFC 3339 timestamp format.' | b2sum -l 256 | awk '{ print $1 }' | xxd -r -p | base32 | sed -E 's/=//g; s/.*(.{7})$/\\1/' | tr '[A-Z]' '[a-z]'
(
xxd is part of Vim.)
printf '%s\n%s\n%s' 'https://example.com/twtxt.txt' '2020-12-09T15:38:42Z' 'The twt hash now uses the RFC 3339 timestamp format.' | b2sum -l 256 | awk '{ print $1 }' | xxd -r -p | base32 | sed -E 's/=//g; s/.*(.{7})$/\1/' | tr '[A-Z]' '[a-z]'
(
xxd is part of Vim.)
printf '%s\n%s\n%s' 'https://example.com/twtxt.txt' '2020-12-09T15:38:42Z' 'The twt hash now uses the RFC 3339 timestamp format.' | b2sum -l 256 | awk '{ print $1 }' | xxd -r -p | base32 | sed -E 's/=//g; s/.*(.{7})$/\1/' | tr '[A-Z]' '[a-z]'
(
xxd is part of Vim.)
printf '%s\n%s\n%s' 'https://example.com/twtxt.txt' '2020-12-09T15:38:42Z' 'The twt hash now uses the RFC 3339 timestamp format.' | b2sum -l 256 | awk '{ print $1 }' | xxd -r -p | base32 | sed -E 's/=//g; s/.*(.{7})$/\1/' | tr '[A-Z]' '[a-z]'
(
xxd is part of Vim.)
printf '%s\\n%s\\n%s' 'https://example.com/twtxt.txt' '2020-12-09T15:38:42Z' 'The twt hash now uses the RFC 3339 timestamp format.' | b2sum -l 256 | awk '{ print $1 }' | xxd -r -p | base32 | sed -E 's/=//g; s/.*(.{7})$/\\1/' | tr '\n' '\n'
(
xxd is part of Vim.)
batcat package under Ubuntu doesn't install one.
MANPATH and man pages install on that location. I found the man page for Ubuntu 24.04, and got it installed now: https://manpages.ubuntu.com/manpages/noble/man1/batcat.1.html