Maybe we shouldn’t add time sensitive metadata. Maybe # following = https://domgoergen.com/twtxt/mdom.txt https://enotty.dk/twtxt.txt …
@kas@enotty.dk, @benaiah@benaiah.me Should metadata always be at the start of the file or can it be interspersed with tweets?
@mdom@domgoergen.com, @kas@enotty.dk re: metadata, I’m (obviously) in favor of my suggestion for metadata-in-comments, but I don’t think we should have comments in comments.
@kas@enotty.dk The amount of whitespace around the equal sign shouldn’t matter. Wouldn’t be a comment above the line not enough? <# nick = mdom # my nick> looks weird.
I would love to add metadata to the spec, but someone would have to hack it into twtxt #issue48 @buckket@buckket.org? :)
metadata is actually the most useful surveillance data per bit, it’s what you store/query first when you lack the resources to use it all
#txtnix and #roster now support the new metadata syntax ts#metadata. Now time will tell if somebody will use it.
This would be a good use case for metadata. @kas@enotty.dk could ask clients to refetch less, eg with /refetch 10m
#txtnix new subcommand will dump all available metadata for a feed. Until a decision is made it uses my // suggestion.
How should metadata about a twtxt feed be stored? Weigh in @ https://github.com/buckket/twtxt/issues/48
Nix 0.12 released
Nix\
 0.12 has been released. The most important change is that
Nix no longer needs Berkeley DB to store metadata, but there are
many other improvements. See the release\
 notes for details. ⌘ Read more