# 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 22
# self = https://watcher.sour.is/conv/ojybh3a
prologic
twtxt.net
View Thread
@adi @darch Fork only shows up in conversation view anyway
prologic
twtxt.net
View Thread
@adi @darch Fork only shows up in conversation view anyway
darch
twtxt.net
View Thread
chould the for feature inclode both the old and new hash so as to be viewed in the original conversation as well?\nEDIT: using the fork button does not automatically metion the person who's post you are replying to... @prologic (Bug or feature;)
darch
twtxt.net
View Thread
chould the fork feature include both the old and new hash so that it would be viewed in the original conversation as well?

EDIT: using the fork button does not automatically metion the person who's post you are replying to... @prologic (Bug or feature;)
darch
twtxt.net
View Thread
chould the fork feature include both the old and new hash so that it would be viewed in the original conversation as well?\n\nEDIT: using the fork button does not automatically metion the person who's post you are replying to... @prologic (Bug or feature;)
prologic
twtxt.net
View Thread
@darch Not a bug. But _could_ be added.\n\nIn terms of mentioning the original conversation I'm pretty sure it already does. There's nothing to do here except improve the UX
prologic
twtxt.net
View Thread
@darch Not a bug. But _could_ be added.

In terms of mentioning the original conversation I'm pretty sure it already does. There's nothing to do here except improve the UX
prologic
twtxt.net
View Thread
@darch Not a bug. But _could_ be added.

In terms of mentioning the original conversation I'm pretty sure it already does. There's nothing to do here except improve the UX
prologic
twtxt.net
View Thread
@darch For example:\n\n- This conversation: https://twtxt.net/conv/xic44sa\n - Got forked into: https://twtxt.net/conv/4hbckpq\n\nIf you follow the permalink for the root of the conversation that got forked 4hbckpq:\n\n- https://twtxt.net/twt/4hbckpq\n - You discover that it was originally: https://twtxt.net/conv/xic44sa\n\n> @prologic @lin (#xic44sa) Could my instance of LibreTranslate help with building a prototype?
prologic
twtxt.net
View Thread
@darch For example:

- This conversation: https://twtxt.net/conv/xic44sa
- Got forked into: https://twtxt.net/conv/4hbckpq

If you follow the permalink for the root of the conversation that got forked 4hbckpq:

- https://twtxt.net/twt/4hbckpq
- You discover that it was originally: https://twtxt.net/conv/xic44sa

> @prologic @lin (#xic44sa) Could my instance of LibreTranslate help with building a prototype?
prologic
twtxt.net
View Thread
@darch For example:

- This conversation: https://twtxt.net/conv/xic44sa
- Got forked into: https://twtxt.net/conv/4hbckpq

If you follow the permalink for the root of the conversation that got forked 4hbckpq:

- https://twtxt.net/twt/4hbckpq
- You discover that it was originally: https://twtxt.net/conv/xic44sa

> @prologic @lin (#xic44sa) Could my instance of LibreTranslate help with building a prototype?
prologic
twtxt.net
View Thread
@darch What two pieces of context do you need in the templates to make what you've envisioned work?

- InReplyTo -- A short string of what current post was "in reply" to?
- ForkedFrom -- A short string of what a conversation was "forked from"?

Is this all you need? If so can you give some guidance on what they should ideally look like content-wise. For the API (REST+JSON) I would just supply the hashes and nothing more.
prologic
twtxt.net
View Thread
@darch What two pieces of context do you need in the templates to make what you've envisioned work?

- InReplyTo -- A short string of what current post was "in reply" to?
- ForkedFrom -- A short string of what a conversation was "forked from"?

Is this all you need? If so can you give some guidance on what they should ideally look like content-wise. For the API (REST+JSON) I would just supply the hashes and nothing more.
prologic
twtxt.net
View Thread
@darch What two pieces of context do you need in the templates to make what you've envisioned work?\n\n- InReplyTo -- A short string of what current post was "in reply" to?\n- ForkedFrom -- A short string of what a conversation was "forked from"?\n\nIs this all you need? If so can you give some guidance on what they should ideally look like content-wise. For the API (REST+JSON) I would just supply the hashes and nothing more.
darch
twtxt.net
View Thread
@prologic Yes something like that :)

1. InReplyTo – A short string of what current post was “in reply” to?: Something that will output what you see here: http://darch.dk/yarn-hack/Mockup_to_Code/ and maybe strip out mentions. I think we had a discussion with more option on github where i made some other variation on the mockup. It should truncate the text so it will not be too long.

2. ForkedFrom – A short string of what a conversation was “forked from”? I'm not sure how this should look just yet, but it could be maybe use the same way of getting the info
darch
twtxt.net
View Thread
@prologic Yes something like that :)\n\n1. InReplyTo – A short string of what current post was “in reply” to?: Something that will output what you see here: http://darch.dk/yarn-hack/Mockup_to_Code/ and maybe strip out mentions. I think we had a discussion with more option on github where i made some other variation on the mockup. It should truncate the text so it will not be too long.\n\n2. ForkedFrom – A short string of what a conversation was “forked from”? I'm not sure how this should look just yet, but it could be maybe use the same way of getting the info
darch
twtxt.net
View Thread
@prologic \n3 . Bookmarks could maybe be generated using the same feature instead of just being a list of twt-hashes:\n
darch
twtxt.net
View Thread
@prologic \n3. *Bookmarks* could maybe be generated using the same feature instead of just being a list of twt-hashes:\n
darch
twtxt.net
View Thread
@prologic
3 . Bookmarks could maybe be generated using the same feature instead of just being a list of twt-hashes:
prologic
twtxt.net
View Thread
@darch

> Bookmarks could maybe be generated using the same feature instead of just being a list of twt-hashes:

Yup 👌
prologic
twtxt.net
View Thread
@darch

> Bookmarks could maybe be generated using the same feature instead of just being a list of twt-hashes:

Yup 👌
prologic
twtxt.net
View Thread
@darch \n\n> Bookmarks could maybe be generated using the same feature instead of just being a list of twt-hashes:\n\nYup 👌