# 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 39
# self = https://watcher.sour.is/conv/7ef2sea
@bendwr and I discussing something along the lines of: 
I.e: How to deal with or reduce noise from legacy feeds.
@bendwr and I discussing something along the lines of: I.e: How to deal with or reduce noise from legacy feeds.
@bendwr and I discussing something along the lines of: I.e: How to deal with or reduce noise from legacy feeds.
Err I meant @bender and I (Mobile app doesn't have auto-complete for -mentions 🤦♂️🥲😢)
Err I meant @bender and I (Mobile app doesn't have auto-complete for -mentions 🤦♂️🥲😢)
Err I meant @bender and I (Mobile app doesn't have auto-complete for -mentions 🤦♂️🥲😢)
@prologic it makes absolute sense for a Yarn.social user. I propose the following formatting change:
> **WARNING:**
>
> You are about to follow a legacy feed, which may not have any kind of engagement. Do you want to continue?
@prologic This seems like it would drive a wedge between Yarn.social and the people on regular old twtxt.
@mckinley Do you have an alternate proposal? What we _want_ to avoid really (if possible) is the idea of "1-ay posting" or "posting to the void". As an obvious example, the idea of syncing your Mastoon toots to Twtxt twts that you never see replies to is well umm just silly 🤣 and thus creates unwanted noise as it's just like talking to a "brick wall" 😥
@mckinley Do you have an alternate proposal? What we _want_ to avoid really (if possible) is the idea of "1-ay posting" or "posting to the void". As an obvious example, the idea of syncing your Mastoon toots to Twtxt twts that you never see replies to is well umm just silly 🤣 and thus creates unwanted noise as it's just like talking to a "brick wall" 😥
@mckinley Do you have an alternate proposal? What we _want_ to avoid really (if possible) is the idea of "1-ay posting" or "posting to the void". As an obvious example, the idea of syncing your Mastoon toots to Twtxt twts that you never see replies to is well umm just silly 🤣 and thus creates unwanted noise as it's just like talking to a "brick wall" 😥
The wording can be more subtle like "This feed have not seen much activity within the last year" and maybe adding a UI like I did in timeline showing time ago for all feeds 
I agree that it good to clean up the Mastodon re-feeds, but it should also be okay for anyone to spin up a twtxt.txt just for syndicating they stuff from blog or what ever.
The "not receiving replies" could partly be fixed by implementing a working webmentions for twtxt.txt
The wording can be more subtle like "This feed have not seen much activity within the last year" and maybe adding a UI like I did in timeline showing time ago for all feeds
I agree that it good to clean up the Mastodon re-feeds, but it should also be okay for anyone to spin up a twtxt.txt just for syndicating they stuff from blog or what ever.
The "not receiving replies" could partly be fixed by implementing a working webmentions for twtxt.txt
The wording can be more subtle like "This feed have not seen much activity within the last year" and maybe adding a UI like I did in timeline showing time ago for all feeds
I agree that it good to clean up the Mastodon re-feeds, but it should also be okay for anyone to spin up a twtxt.txt just for syndicating they stuff from blog or what ever.
The "not receiving replies" could partly be fixed by implementing a working webmentions for twtxt.txt
The wording can be more subtle like "This feed have not seen much activity within the last year" and maybe adding a UI like I did in timeline showing time ago for all feeds
I agree that it good to clean up the Mastodon re-feeds, but it should also be okay for anyone to spin up a twtxt.txt just for syndicating they stuff from blog or what ever.
The "not receiving replies" could partly be fixed by implementing a working webmentions for twtxt.txt
@prologic Why do we need to avoid posting to the void? That's pretty much what twtxt was made for. I don't like the "Legacy feed" terminology, either. I support the delisting of ciberlandia.pt but I think this change is heading in a bad direction.
I like @sorenpeter 's suggestion. It gives the users the information and lets them make their own decision instead of putting a big scary warning in their face. That's what Microsoft does, and we shouldn't be Microsoft.
@mckinley I think "posting to the void" was/is a poor choice of words hete.
@mckinley I think "posting to the void" was/is a poor choice of words hete.
@mckinley I think "posting to the void" was/is a poor choice of words hete.
@prologic I think one-way feeds are okay and we shouldn't discourage them so strongly. On the other hand, I think it's the duty of a poderator to filter out feeds that are just noise from the Discover feed. I definitely consider a truckload of one-way posts mostly in another language to be noise. Did you get rid of Gopher Chat too? I'd call that noise, too.
@prologic I think one-way feeds are okay and we shouldn't discourage them so strongly. On the other hand, I think it's the duty of a poderator to filter out feeds that are just noise from the Discover feed. I definitely consider a truckload of one-way posts mostly in another language to be noise. Did you get rid of Gopher Chat too? I'd call that noise, for sure.
@mckinley I think we just need a way of surfacing this information better for both users and operators? 🤔
@mckinley I think we just need a way of surfacing this information better for both users and operators? 🤔
@mckinley I think we just need a way of surfacing this information better for both users and operators? 🤔
This also just reminds me of the other problems that exist:
- bad mentions.
- knowing whether someone will you've -mentioned will even see your reply at all.
This also just reminds me of the other problems that exist:
- bad mentions.
- knowing whether someone will you've -mentioned will even see your reply at all.
This also just reminds me of the other problems that exist:
- bad mentions.
- knowing whether someone will you've -mentioned will even see your reply at all.
For example I noticed in this thread, someone, me, and you, and now it's just a bad -mention mentioned Soren Peter with a bad link :/
For example I noticed in this thread, someone, me, and you, and now it's just a bad -mention mentioned Soren Peter with a bad link :/
For example I noticed in this thread, someone, me, and you, and now it's just a bad -mention mentioned Soren Peter with a bad link :/