# 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 11
# self = https://watcher.sour.is/conv/jcjmqkq
@lyse @prologic Sorry, I have hardly slept last night. 😅 I probably didn’t chose the best words to describe this. 🥴
> Yes, I'm all for dedicated message IDs. That would be a whole new format then. *But I would be fine with it.*
Honestly, me too. When Yarn originally showed up, I was concerned that it would extend twtxt in dramatically incompatible ways or, worse, change it in a way so that you needed *server software*. 😅 The latter would have ruined it for me. A *major* reason why I still use twtxt/Yarn is that it’s still just a file you put somewhere. If there was the need to *run a daemon*, I’d give up and just use some ActivityPub thingy instead.
What I did not expect, however, was that the original twtxt itself would just … die. There has been no development in the original software anymore and virtually all the original feeds are dead. Some feeds are left, but they’re just used as an alternative to Atom/RSS for some blogs. I don’t know what happened behind the scenes that killed off twtxt (I have a few guesses, though), but the sad truth is that it’s gone.
So, yeah, maybe this gives us the freedom now to *break* with the original twtxt spec (if needed) and come up with a format that *fixes* the issues we’re seeing.
(Oh god. Are we re-inventing Usenet then? Again? 😂)
@lyse @prologic Sorry, I have hardly slept last night. 😅 I probably didn’t chose the best words to describe this. 🥴
> Yes, I'm all for dedicated message IDs. That would be a whole new format then. *But I would be fine with it.*
Honestly, me too. When Yarn originally showed up, I was concerned that it would extend twtxt in dramatically incompatible ways or, worse, change it in a way so that you needed *server software*. 😅 The latter would have ruined it for me. A *major* reason why I still use twtxt/Yarn is that it’s still just a file you put somewhere. If there was the need to *run a daemon*, I’d give up and just use some ActivityPub thingy instead.
What I did not expect, however, was that the original twtxt itself would just … die. There has been no development in the original software anymore and virtually all the original feeds are dead. Some feeds are left, but they’re just used as an alternative to Atom/RSS for some blogs. I don’t know what happened behind the scenes that killed off twtxt (I have a few guesses, though), but the sad truth is that it’s gone.
So, yeah, maybe this gives us the freedom now to *break* with the original twtxt spec (if needed) and come up with a format that *fixes* the issues we’re seeing.
(Oh god. Are we re-inventing Usenet then? Again? 😂)
@lyse @prologic Sorry, I have hardly slept last night. 😅 I probably didn’t chose the best words to describe this. 🥴
> Yes, I'm all for dedicated message IDs. That would be a whole new format then. *But I would be fine with it.*
Honestly, me too. When Yarn originally showed up, I was concerned that it would extend twtxt in dramatically incompatible ways or, worse, change it in a way so that you needed *server software*. 😅 The latter would have ruined it for me. A *major* reason why I still use twtxt/Yarn is that it’s still just a file you put somewhere. If there was the need to *run a daemon*, I’d give up and just use some ActivityPub thingy instead.
What I did not expect, however, was that the original twtxt itself would just … die. There has been no development in the original software anymore and virtually all the original feeds are dead. Some feeds are left, but they’re just used as an alternative to Atom/RSS for some blogs. I don’t know what happened behind the scenes that killed off twtxt (I have a few guesses, though), but the sad truth is that it’s gone.
So, yeah, maybe this gives us the freedom now to *break* with the original twtxt spec (if needed) and come up with a format that *fixes* the issues we’re seeing.
(Oh god. Are we re-inventing Usenet then? Again? 😂)
@lyse @prologic Sorry, I have hardly slept last night. 😅 I probably didn’t chose the best words to describe this. 🥴
> Yes, I'm all for dedicated message IDs. That would be a whole new format then. *But I would be fine with it.*
Honestly, me too. When Yarn originally showed up, I was concerned that it would extend twtxt in dramatically incompatible ways or, worse, change it in a way so that you needed *server software*. 😅 The latter would have ruined it for me. A *major* reason why I still use twtxt/Yarn is that it’s still just a file you put somewhere. If there was the need to *run a daemon*, I’d give up and just use some ActivityPub thingy instead.
What I did not expect, however, was that the original twtxt itself would just … die. There has been no development in the original software anymore and virtually all the original feeds are dead. Some feeds are left, but they’re just used as an alternative to Atom/RSS for some blogs. I don’t know what happened behind the scenes that killed off twtxt (I have a few guesses, though), but the sad truth is that it’s gone.
So, yeah, maybe this gives us the freedom now to *break* with the original twtxt spec (if needed) and come up with a format that *fixes* the issues we’re seeing.
(Oh god. Are we re-inventing Usenet then? Again? 😂)
(Let’s not rush things, obviously. Such a change would have to be well thought through and actually be worth it. It’s not like the current state of Yarn/twtxt is completely unusable.)
(Let’s not rush things, obviously. Such a change would have to be well thought through and actually be worth it. It’s not like the current state of Yarn/twtxt is completely unusable.)
(Let’s not rush things, obviously. Such a change would have to be well thought through and actually be worth it. It’s not like the current state of Yarn/twtxt is completely unusable.)
(Let’s not rush things, obviously. Such a change would have to be well thought through and actually be worth it. It’s not like the current state of Yarn/twtxt is completely unusable.)
@movq @prologic Oh yeah, we have to take our time with that and craft it very carefully.
My theory about the descent of the original twtxt universe is that a) people just move on to other things and b) it was just not practical enough.