# 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/2id47na
I've been thinking in the back of my mind for a while now, that the Yarn.social / twtxt + ActivityPub integration was a mistake and a. bad idea. I'm starting to consider it a complete failure.
I've been thinking in the back of my mind for a while now, that the Yarn.social / twtxt + ActivityPub integration was a mistake and a. bad idea. I'm starting to consider it a complete failure.
I've been thinking in the back of my mind for a while now, that the Yarn.social / twtxt + ActivityPub integration was a mistake and a. bad idea. I'm starting to consider it a complete failure.
@prologic As an outsider, I donβt really have an opinion on this (other than: twtxt.net is quite confusing with all the Mastodon posts π
), so: Why do you think that? π€
@prologic As an outsider, I donβt really have an opinion on this (other than: twtxt.net is quite confusing with all the Mastodon posts π
), so: Why do you think that? π€
@prologic As an outsider, I donβt really have an opinion on this (other than: twtxt.net is quite confusing with all the Mastodon posts π
), so: Why do you think that? π€
@movq For several reasons; I think the pull based model is honestly better in every regard, the deliberate slow nature of Twtxt/Yarn is _actually_ beneficial and discovery/connections made through "people you know" is more genuine (_rather then pushing crap to randos you don't really know or have never known_)
@movq For several reasons; I think the pull based model is honestly better in every regard, the deliberate slow nature of Twtxt/Yarn is _actually_ beneficial and discovery/connections made through "people you know" is more genuine (_rather then pushing crap to randos you don't really know or have never known_)
@movq For several reasons; I think the pull based model is honestly better in every regard, the deliberate slow nature of Twtxt/Yarn is _actually_ beneficial and discovery/connections made through "people you know" is more genuine (_rather then pushing crap to randos you don't really know or have never known_)
Not to mention, actually implementing Activity Pub is just so hard to get right π€¦ββοΈ
Not to mention, actually implementing Activity Pub is just so hard to get right π€¦ββοΈ
Not to mention, actually implementing Activity Pub is just so hard to get right π€¦ββοΈ
I understand your thoughts on this, but I would not call it a failure - because you learned a lot from it, and lots of things worked as well.
And there are alternatives for those who needs\wants activitypub, so I think also yarn\twtxt benefits from you focusing on that instead of dealing with the frustrations of activitypub integration. And maybe it'll feel a bit better to put that on the backburner? :)
I understand your thoughts on this, but I would not call it a failure - because you learned a lot from it, and lots of things worked as well.
And there are alternatives for those who needs\\wants activitypub, so I think also yarn\\twtxt benefits from you focusing on that instead of dealing with the frustrations of activitypub integration. And maybe it'll feel a bit better to put that on the backburner? :)