# 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 33
# self = https://watcher.sour.is/conv/w76zd4q
How's this @darch ? πŸ€”
How's this @darch ? πŸ€”
@prologic A really good start :)
@darch Good because that’s the best I can do with my skillz 😁
@darch Good because that’s the best I can do with my skillz 😁
@prologic I would use small over em, but i will try to style it in my copenhagen-theme sometime this week hopefully. Can you provide the avatar and date-time or time-ago as well? And maybe also render the markdown, not just show the plaintext:
@darch That all sounds _really_ hard UI/UX wise, so rather than trying to do that myself, I did this:


* bfab60e 2021-11-15 | Add getRootTwt template function (HEAD -> master) [James Mills]


Hopefully this gives you everything you need at the template level πŸ€—
@darch That all sounds _really_ hard UI/UX wise, so rather than trying to do that myself, I did this:


* bfab60e 2021-11-15 | Add getRootTwt template function (HEAD -> master) [James Mills]


Hopefully this gives you everything you need at the template level πŸ€—
But I did at least implement one of your suggestions:


* 1b9c8fe 2021-11-15 | Use <small> instead of <em> as per @darch's feedback re show_twt_context feature (HEAD -> master) [James Mills]


πŸ€—
But I did at least implement one of your suggestions:


* 1b9c8fe 2021-11-15 | Use <small> instead of <em> as per @darch's feedback re show_twt_context feature (HEAD -> master) [James Mills]


πŸ€—
@prologic What part sounds really hard?
@darch Rendering the Avatar and getting the UX right for "Markdown" rendered content. What if it has an image? πŸ˜…
@darch Rendering the Avatar and getting the UX right for "Markdown" rendered content. What if it has an image? πŸ˜…
hmm good questing if it's an image-only post, maybe just show the image icon like for non-whitelisted images links. or maybe we don't deal with these issues just yetπŸ˜…
@darch That's what I was thinking too. I _can_ probably do that fairly easily by duplciating a bunch of the FormatTwt() code that does the Markdown -> HTML rendering and just make all links to Image display as 🏞 I'll try this later, but the whole Avatar thing I _very likely_ won't be good enough to do myself πŸ˜‚
@darch That's what I was thinking too. I _can_ probably do that fairly easily by duplciating a bunch of the FormatTwt() code that does the Markdown -> HTML rendering and just make all links to Image display as 🏞 I'll try this later, but the whole Avatar thing I _very likely_ won't be good enough to do myself πŸ˜‚
@prologic if the <img> is somewhere in the template I will take care of making it look right with my rad CSSkillzβ„’ it could be hidden in a <!-- --> for a start
Also there is no need to render the twt-context in conversation view ;)
Okay I _tried_ and so far the result isn't great. it needs some work.

Branch => full_twt_context

Example from dev instance =>

Maybe you can help me fix the markup and css on the default theme?
Okay I _tried_ and so far the result isn't great. it needs some work.

Branch => full_twt_context

Example from dev instance =>

Maybe you can help me fix the markup and css on the default theme?
@darch Good point πŸ‘Œ
@darch Good point πŸ‘Œ
@prologic yes i can look at the default theme as well:)
@darch
> Also there is no need to render the twt-context in conversation view ;)

Actually, I would say *we need to only show the content in conversation view*.
but I see it doesn't really go to the *twt* you are replying to, but the conversation top. Hmm...
@fastidious Sorry don't really get your reasoning here...
@prologic How do I activate the new twt-context on my own pod?
@darch
> How do I activate the new twt-context on my own pod?

Use show_twt_context under "Enabled Optional Features" on "Manage Pod".
@fastidious Gracias!
@darch
> Sorry don’t really get your reasoning here…

It would be amazing if when I hit reply to a twt in a conversation (like I did on this one for #rp47m4q, your twt), the *twt-context* link would go straight to the twt I replied (like this) to within a conversation, not to the conversation top, as it does now.
It took a long time to do such a simple thing: https://git.mills.io/yarnsocial/yarn/commit/242785c9eb8e2af5da4cfb17a1aa6b4c5f0fcb2f
I really wanted to place the in-reply on the same line as post-time-ago+bookmark, but pico.css or some other omen would not let me (at least not tonight)
(BONUS: I "fixed" the badge to not scream LOOOK AT ME! I'M A NOTIFICATION! ;)
@darch I love it! 😍 I look forward to merging this πŸ‘Œ
@darch I love it! 😍 I look forward to merging this πŸ‘Œ