# 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 9
# self = https://watcher.sour.is/conv/g52ndpq
Twtxt spec enhancement proposal thread ๐งต
Adding attributes to individual twts similar to adding feed attributes in the heading comments.
https://git.mills.io/yarnsocial/go-lextwt/pulls/17
The basic use case would be for multilingual feeds where there is a default language and some twts will be written a different language.
As seen in the wild: https://eapl.mx/twtxt.txt
The attributes are formatted as [key=value]
They can show up in the twt anywhere it is not enclosed by another element such as codeblock
or part of a markdown link.
@xuu It's growing on me for sure ๐ Let's see what others think. What other use-cases can we use these for? I'm not all that convinced that reposts/boosts work all that well based on what I've seen, but happy to be proven wrong ๐
@xuu It's growing on me for sure ๐ Let's see what others think. What other use-cases can we use these for? I'm not all that convinced that reposts/boosts work all that well based on what I've seen, but happy to be proven wrong ๐
@xuu It's growing on me for sure ๐ Let's see what others think. What other use-cases can we use these for? I'm not all that convinced that reposts/boosts work all that well based on what I've seen, but happy to be proven wrong ๐
@xuu seems like a good idea
@xuu @prologic All I can tell you is I won't have a use for key value pairs. If I write a German message every now and then, I'm too lazy to annotate the language. I also never missed formal reposts. The simplicity works well for me.
@lyse I _think_ it's fine if this is an optional opt-in feature. I'd only be worried that it _might_ clutter up the content you care about reading hmm ๐ง
@lyse I _think_ it's fine if this is an optional opt-in feature. I'd only be worried that it _might_ clutter up the content you care about reading hmm ๐ง
@lyse I _think_ it's fine if this is an optional opt-in feature. I'd only be worried that it _might_ clutter up the content you care about reading hmm ๐ง