# 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 31
# self = https://watcher.sour.is/conv/6ocmxea
@jmjl Before working on a patch, please explain a little more what you’re planning to do. :) jenny has a very narrow scope and I can’t guarantee that I’ll apply the patch (for example if it’s not useful to me personally).
@jmjl Before working on a patch, please explain a little more what you’re planning to do. :) jenny has a very narrow scope and I can’t guarantee that I’ll apply the patch (for example if it’s not useful to me personally).
@jmjl Before working on a patch, please explain a little more what you’re planning to do. :) jenny has a very narrow scope and I can’t guarantee that I’ll apply the patch (for example if it’s not useful to me personally).
@jmjl @movq To be honest I see no point in supporting the so-called "Registry" APi. A registry implies a piece of "centralisation" that really feels counter to the point of a decentralised Twtxt ecosystem IMO 👌 There is just simply no value.
@jmjl @movq To be honest I see no point in supporting the so-called "Registry" APi. A registry implies a piece of "centralisation" that really feels counter to the point of a decentralised Twtxt ecosystem IMO 👌 There is just simply no value.
@jmjl @movq To be honest I see no point in supporting the so-called "Registry" APi. A registry implies a piece of "centralisation" that really feels counter to the point of a decentralised Twtxt ecosystem IMO 👌 There is just simply no value.
@prologic Yes, I agree – so some extent. 😅 Registries (_or twtxt.net, for that matter_) serve the purpose of being a tool for discovering feeds.
@prologic Yes, I agree – so some extent. 😅 Registries (_or twtxt.net, for that matter_) serve the purpose of being a tool for discovering feeds.
@prologic Yes, I agree – so some extent. 😅 Registries (_or twtxt.net, for that matter_) serve the purpose of being a tool for discovering feeds.
@movq I prefer this to happen using search engines and crawlers
@movq I prefer this to happen using search engines and crawlers
@movq I prefer this to happen using search engines and crawlers
registries are kind of complicated. Which registry do you register your feed to? 🤔
registries are kind of complicated. Which registry do you register your feed to? 🤔
registries are kind of complicated. Which registry do you register your feed to? 🤔
@prologic I guess you could create a registry of your feeds, so that when someone starts following you, it'll be added to the registry. So you can get pings or whatever you want, it doesn't have to be a centralized registry if it's yours.
@jmjl I'm not quite sure I follow your train of thought here? How does this solve what I see as two problems? a) central registries and b) which registry do you register to? and really c) which registry do clients uses to find other feeds?
@jmjl I'm not quite sure I follow your train of thought here? How does this solve what I see as two problems? a) central registries and b) which registry do you register to? and really c) which registry do clients uses to find other feeds?
@jmjl I'm not quite sure I follow your train of thought here? How does this solve what I see as two problems? a) central registries and b) which registry do you register to? and really c) which registry do clients uses to find other feeds?
@prologic I am saying that you could create your own registry for yourself, your own use, so only you would use, but yeah.
a) Yeah, there could still be registries related to communities, so
making a follow new users from registry feature might be nice, but I
don't know really.
b) You can register to as many registers as you'd like
c) That's the same problem as right now technically, we could create
registries that are related to specific fields, like tech (many tech
registries), housing and all that, but I don't really know.
@jmjl Maybe let's think of it this way...
> What problems does a registry solve?
@jmjl Maybe let's think of it this way...
> What problems does a registry solve?
@jmjl Maybe let's think of it this way...
> What problems does a registry solve?
@prologic It solves the issue of finding users from inside twtxt, but you'll have to find registries which is in itself a chicken-egg problem.
It also makes it easier to implment web twtxt clients, as they won't have to make that many requests, just one to the registry, instead of having each web-client make a request, but then you lose part of the features, as the registry would have to implment things outside the spec to be able to allow follows, and you seeing them...
@jmjl Yup I understand 😆 I still believe a search engine solves this better 🤔
@jmjl Yup I understand 😆 I still believe a search engine solves this better 🤔
@jmjl Yup I understand 😆 I still believe a search engine solves this better 🤔