# 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 20
# self = https://watcher.sour.is/conv/xnmwvqa
@tamer I'm sorry you feel that Yarn.social is a cheap copy of Mastoon. I don't share that opinion obviously and I do not share the same "beliefs" in federation as being necessary.
I _hope_ you've read About Yarn.social before making this critique...
You are welcome to chose a different platform, in fact you are absolutely free to Host your own Twtxt -- In fact it's pretty damn clear mate that you can do that if you wish. The Specs are freely published and open.
@tamer I'm sorry you feel that Yarn.social is a cheap copy of Mastoon. I don't share that opinion obviously and I do not share the same "beliefs" in federation as being necessary.
I _hope_ you've read About Yarn.social before making this critique...
You are welcome to chose a different platform, in fact you are absolutely free to Host your own Twtxt -- In fact it's pretty damn clear mate that you can do that if you wish. The Specs are freely published and open.
Your specific comment:
> I was hoping development would have gone in the direction to help people to publish to a personnel held public facing folder via FTP, Dropbox, Sia Skynet, IPFS etc
Is counter productive to the project's goal. We aim to make things as simple as possible for end-users, whilst at the same time publishing open specs that improve the overall experience and utility. My old man for example would never in his life do what you're suggesting.
Try to remember there are all kinds of people in the world, some without any technical expertise.
Your specific comment:
> I was hoping development would have gone in the direction to help people to publish to a personnel held public facing folder via FTP, Dropbox, Sia Skynet, IPFS etc
Is counter productive to the project's goal. We aim to make things as simple as possible for end-users, whilst at the same time publishing open specs that improve the overall experience and utility. My old man for example would never in his life do what you're suggesting.
Try to remember there are all kinds of people in the world, some without any technical expertise.
@tamer I don't think you really understand 😁 If you have time we can jump on a video call and discuss more face to face 🤗
@tamer I don't think you really understand 😁 If you have time we can jump on a video call and discuss more face to face 🤗
@tamer Feel free to build on mate 👌
@tamer Feel free to build on mate 👌
@tamer I still look at it like this: Yarn.social is *one way* to participate with the twtxt world. It’s presumably a very convenient way (users can just register in a web app), but nothing forces you to use it. I don’t, some others don’t. I host my twtxt file as a simple text file on my web server.
The extensions made by Yarn.social are listed under https://dev.twtxt.net/ and they are backwards-compatible and also not very complex, which makes it still very much possible to implement your own Yarn.social-compatible twtxt client. This is a huge plus. And, frankly, I wouldn’t be active in this community anymore if that wasn’t the case. 🙃
@tamer I still look at it like this: Yarn.social is *one way* to participate with the twtxt world. It’s presumably a very convenient way (users can just register in a web app), but nothing forces you to use it. I don’t, some others don’t. I host my twtxt file as a simple text file on my web server.
The extensions made by Yarn.social are listed under https://dev.twtxt.net/ and they are backwards-compatible and also not very complex, which makes it still very much possible to implement your own Yarn.social-compatible twtxt client. This is a huge plus. And, frankly, I wouldn’t be active in this community anymore if that wasn’t the case. 🙃
@tamer I still look at it like this: Yarn.social is *one way* to participate with the twtxt world. It’s presumably a very convenient way (users can just register in a web app), but nothing forces you to use it. I don’t, some others don’t. I host my twtxt file as a simple text file on my web server.
The extensions made by Yarn.social are listed under https://dev.twtxt.net/ and they are backwards-compatible and also not very complex, which makes it still very much possible to implement your own Yarn.social-compatible twtxt client. This is a huge plus. And, frankly, I wouldn’t be active in this community anymore if that wasn’t the case. 🙃
@movq Thank you for your support! 🙇♂️ It is very much graciously appreciated! 🤗
@movq Thank you for your support! 🙇♂️ It is very much graciously appreciated! 🤗
It reminds me of when I was complaining about Facebook on Facebook 🤔
@tamer It's completely different. It's just funny to me saying "Facebook is bad, don't use it". Here you are listened to by the designers and influence the product/system, I love that!
From the thread, maybe saying 'cheap copy' was harsh for an open product. I, being harsh sometimes, get it's difficult to be open and polite at the same time.
@eaplmx spot on! It's one thing to be heard, it's another to be listened to, and another to have ideas!
My offer for an open video call is still on the table btw...
I will be holding one this Saturday at around 12pm (midday) UTC -- I usually do every week
My offer for an open video call is still on the table btw...
I will be holding one this Saturday at around 12pm (midday) UTC -- I usually do every week