# 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 17
# self = https://watcher.sour.is/conv/c6fqgna
π‘ Feature idea: What do we _think_ about the idea of "Pinned Twts" that one can pin to their Profile page? π€ Sort of like Bookmarks, but a bit different.
π‘ Feature idea: What do we _think_ about the idea of "Pinned Twts" that one can pin to their Profile page? π€ Sort of like Bookmarks, but a bit different.
@prologic I like it. I believe it was asked for before. If implemented, please no more than one pinned at a time. Otherwise it becomes a pinned fest pretty fast!
@david Should it be "no more than 1 pinned Twt" or "no more than X pinned Twts" where X is configurable at the Pod level (with a sensible default). For example Github Profiles allow you to pin 4 repos?
@david Should it be "no more than 1 pinned Twt" or "no more than X pinned Twts" where X is configurable at the Pod level (with a sensible default). For example Github Profiles allow you to pin 4 repos?
@prologic configurable at podβs level, sure, and perfect. Configurable at userβs level? Please, donβt. π
@david This is one piece of configuration that makes no sense to put in the hands of "users".
To be clear, there is a difference we make between "Configuration" and "Preference" The code even makes this distinction as well π
@david This is one piece of configuration that makes no sense to put in the hands of "users".
To be clear, there is a difference we make between "Configuration" and "Preference" The code even makes this distinction as well π
Why not just add multiline markdown support for the description field and let peopl use that instead?!
@darch I _think_ you're thinking of something different there mate π
We've discussed this before, opening that can of worms is not worth it IHMO. As I've stated before, unless you can restrict the Markdown syntax to quite a restricted subset here, I don't think that's a good idea to add support for, for the # description = Metadata field.
@darch I _think_ you're thinking of something different there mate π
We've discussed this before, opening that can of worms is not worth it IHMO. As I've stated before, unless you can restrict the Markdown syntax to quite a restricted subset here, I don't think that's a good idea to add support for, for the # description = Metadata field.
Also we're talking about "Pinned Twts" here, not the description field π
Also we're talking about "Pinned Twts" here, not the description field π
@prologic fair enough. I guess I just don't really see the need for this feature for where we are right now. I rather have search, filters and lists that pinned posts (but I have also expressed that before ;)
@prologic I know what you are talking aboutπ but the idea with pinned posts is to have some info at the top of you timeline/profile page and that can just as well be done with the description field. Also how would a pinned post look in the twtxt.txt file or will it be pod-only feature?
@darch I also understand what you're saying π But I see these two as very different ideas π
And yes, pinned Twts would be a UX feature only specific to Yarn profile pages for users in the network. I can't see any way to do this in a feed per se.
@darch I also understand what you're saying π But I see these two as very different ideas π
And yes, pinned Twts would be a UX feature only specific to Yarn profile pages for users in the network. I can't see any way to do this in a feed per se.