Added a twtxt status for @crickybo@rjp.is at https://rjp.is/crickybo.txt - just the latest status to avoid flooding timelines.

@zimpenfish@twt.rjp.is Hey! 👋 Just wondering if this Cricket status thing is basically what you would consider a Bot? The reason I’m asking is that typically yarnd filters out Bots and Automated Feeds out of the “Discover” view. We should try to do something here for new bots and automated feeds and find a way to generalize this? 🤔

@zimpenfish@twt.rjp.is Well before you do, we should discuss this openly and come up with a robust way to do this. We have a bunch of Spec Extensions – So we should start there. The probllem I see at the moment is “how do we prove it’s a bot or automated feed”, “do we care?” cc @lyse@lyse.isobeef.org and @movq@www.uninformativ.de for comment.

Also as an aside (and it doesn’t matter so much because the network and ecosystem is quite small still), feeds do tend to find their way across pods as yarnd is both distributed and decentralised. All it takes is one other person interested in Cricket to follow you (very nice) feed and boom 😅

@zimpenfish@twt.rjp.is That’s what I tend to think too. An author (such as yourself) “declares” that this feed is automated in some way. For examples all of the feeds at feeds.twtxt.net which aggregates and converts RSS/Atom to Twtxt could be doing this too 👌

I’m in favour of something like:

# automated = true

Something as simple as this might work?

@zimpenfish@twt.rjp.is I guess the thing is we have to define what behaviours we would derive from this property.

For example the only one yarnd currently uses is as a mechanism to filter bots and automated feeds out of the “Discover” view of pods, making it basically (as much as one can make possible) other folks you can “discover” (from other user follows on the same pod).

Exactly, I have to explicitly follow a feed in order for it to show up. So, I don’t care either. :-)