# 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 26
# self = https://watcher.sour.is/conv/aimrtoa
Keep the discussion going all! 🤗 I _hope_ you all find this a good read and help better understand how things were designed and built up to this point. Let's figure this out 🙇♂️ cc @jlj @mckinley @lyse
Keep the discussion going all! 🤗 I _hope_ you all find this a good read and help better understand how things were designed and built up to this point. Let's figure this out 🙇♂️ cc @jlj @mckinley @lyse
@prologic Nice writeup! In an ideal world the following disclosure via User-Agent HTTP header would be configurable per feed, not only globally for the user. That's what I'm thinking about implementing in tt, once tt itself fetches the feeds and doesn't delegate this to the twtxt reference implementation. And yes, I'm fully aware that public social media and privacy are contradicting each other. As stated earlier, I think the list of ones followers must be given a TTL, which resets on each GET request. Once the TTL is reached, the follower gets removed from that list. That way, it's like analyzing ones access log, you're not getting dead followers in your list. Not sure, what such a TTL ideally would be. Maybe a week. Maybe two, maybe a month. Probably not more than that.
All this talk about twtxt and privacy … Maybe it won’t be *that* long until I add some privacy features to jenny. 🥴
All this talk about twtxt and privacy … Maybe it won’t be *that* long until I add some privacy features to jenny. 🥴
All this talk about twtxt and privacy … Maybe it won’t be *that* long until I add some privacy features to jenny. 🥴
@movq It's going to be great. ;-)
@lyse I generally like the idea of having a TTL around the "Followers" list. I _think_ that could be great.\n\nIn terms of the per-feed "show me as following" or not, hmm, yeah we _could_ do this but that's probably a bit more work that I had anticipated. I'll have a think about what needs to change to support this...
@lyse I generally like the idea of having a TTL around the "Followers" list. I _think_ that could be great.
In terms of the per-feed "show me as following" or not, hmm, yeah we _could_ do this but that's probably a bit more work that I had anticipated. I'll have a think about what needs to change to support this...
@lyse I generally like the idea of having a TTL around the "Followers" list. I _think_ that could be great.
In terms of the per-feed "show me as following" or not, hmm, yeah we _could_ do this but that's probably a bit more work that I had anticipated. I'll have a think about what needs to change to support this...
Any other ideas folks? @jlj ? How do we feel about removing the @twtxt bot in favor of a per-user "event" feed that you implicitly follow? And maybe a special admin feed that the admin user of a pod implicitly follows (_for new users that join_).
Any other ideas folks? @jlj ? How do we feel about removing the @twtxt bot in favor of a per-user "event" feed that you implicitly follow? And maybe a special admin feed that the admin user of a pod implicitly follows (_for new users that join_).
@prologic I reckon it would be better, if these were feeds that users/admins can explicitly follow or not. Following them by default sounds great, but I imagine some folks just don't want this "spam" in their timelines, so unfollowing should be an offered option.
It seems like this per-event feed thing would be a lot of work. Personally, I think it's fine the way it is now. Publicly broadcasting unfollows went a little too far in my opinion but that was removed, right?
It seems like this per-event feed thing would be a lot of work. Personally, I think it's fine the way it is now. Publicly broadcasting unfollows went a little too far in my opinion but that was removed, right?
@lazarus
> anyway to prevent someone from following another user’s per-event feed?
It _would_ be very specific to the implementation of Yarn.social pods yarnd; so it would not be hard to do. Don't expose it, keep it internal, have access controls around them, etc.
@lazarus \n\n> anyway to prevent someone from following another user’s per-event feed?\n\nIt _would_ be very specific to the implementation of Yarn.social pods yarnd; so it would not be hard to do. Don't expose it, keep it internal, have access controls around them, etc.
@lazarus
> anyway to prevent someone from following another user’s per-event feed?
It _would_ be very specific to the implementation of Yarn.social pods yarnd; so it would not be hard to do. Don't expose it, keep it internal, have access controls around them, etc.
@mckinley \n\n> It seems like this per-event feed thing would be a lot of work.\n\nYeah but not too much work, I'd be up for it 🤗\n\n> Personally, I think it’s fine the way it is now. Publicly broadcasting unfollows went a little too far in my opinion but that was removed, right?\n\nI agree, it went a little to far for little to no "utility" and Yes they were removed in 5f8838fadf -- Which this pod (twtxt.net) is running.
@mckinley
> It seems like this per-event feed thing would be a lot of work.
Yeah but not too much work, I'd be up for it 🤗
> Personally, I think it’s fine the way it is now. Publicly broadcasting unfollows went a little too far in my opinion but that was removed, right?
I agree, it went a little to far for little to no "utility" and Yes they were removed in 5f8838fadf -- Which this pod (twtxt.net) is running.
@mckinley
> It seems like this per-event feed thing would be a lot of work.
Yeah but not too much work, I'd be up for it 🤗
> Personally, I think it’s fine the way it is now. Publicly broadcasting unfollows went a little too far in my opinion but that was removed, right?
I agree, it went a little to far for little to no "utility" and Yes they were removed in 5f8838fadf -- Which this pod (twtxt.net) is running.