# 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 406
# self = https://watcher.sour.is?uri=https://twtxt.andros.dev&offset=66
# next = https://watcher.sour.is?uri=https://twtxt.andros.dev&offset=166
@prologic@lyse First, please leave me your comments on the repository! Even if it's just to give your opinion on what shouldn't be included. The more variety, the better.
Second, I'm going to try to do tests with Elliptic keys and base64. Thanks for the advice @eapl
Finally, I'd like to give my opinion. Secure direct messages are a feature that ActivityPub and Mastodon don't have, to give an example. By including it as an extension, we're already taking a significant leap forward from the competition. Does it make sense to include it in a public feed? In fact, we're already doing that. When we reply to a user, mentioning them at the beginning of the message, it's already a direct message. The message is within a thread, perhaps breaking the conversation. Direct messages would help isolate conversations between 2 users, as well as keeping a thread cleaner and maintaining privacy. I insist, it's optional, it doesn't break compatibility with any client and implementing it isn't complex. If you don't like it, you're free to not use it. If you don't have a public key, no one can send you direct messages.
@prologic@lyse First, please leave me your comments on the repository! Even if it's just to give your opinion on what shouldn't be included. The more variety, the better.
Second, I'm going to try to do tests with Elliptic keys and base64. Thanks for the advice @eapl
Finally, I'd like to give my opinion. Secure direct messages are a feature that ActivityPub and Mastodon don't have, to give an example. By including it as an extension, we're already taking a significant leap forward from the competition. Does it make sense to include it in a public feed? In fact, we're already doing that. When we reply to a user, mentioning them at the beginning of the message, it's already a direct message. The message is within a thread, perhaps breaking the conversation. Direct messages would help isolate conversations between 2 users, as well as keeping a thread cleaner and maintaining privacy. I insist, it's optional, it doesn't break compatibility with any client and implementing it isn't complex. If you don't like it, you're free to not use it. If you don't have a public key, no one can send you direct messages.
@prologic I can't register with GitHub, nor make Pull Requests. Would it be possible to enable this? Maybe this repository could be on GitHub to promote it and increase collaboration.
@prologic I can't register with GitHub, nor make Pull Requests. Would it be possible to enable this? Maybe this repository could be on GitHub to promote it and increase collaboration.
@prologic I can't register with GitHub, nor make Pull Requests. Would it be possible to enable this? Maybe this repository could be on GitHub to promote it and increase collaboration.
This is the first screenshot, a simple timeline I'm using to check the fields. Now I'm working on some details: avatar cache, relative dates, simple thread, etc. #emacs #twtxt
This is the first screenshot, a simple timeline I'm using to check the fields. Now I'm working on some details: avatar cache, relative dates, simple thread, etc. #emacs #twtxt
This is the first screenshot, a simple timeline I'm using to check the fields. Now I'm working on some details: avatar cache, relative dates, simple thread, etc. #emacs #twtxt
Thanks 😀! @aelaraji I am working on a fork now because the new version will break the current code. Therefore, I will upgrade the current repository (https://codeberg.org/deadblackclover/twtxt-el). The original author is helping me with reviews. I am sorry for my long development, I am working in my free time and it is scarce. I will report back to you all. 😋
Thanks 😀! @aelaraji I am working on a fork now because the new version will break the current code. Therefore, I will upgrade the current repository (https://codeberg.org/deadblackclover/twtxt-el). The original author is helping me with reviews. I am sorry for my long development, I am working in my free time and it is scarce. I will report back to you all. 😋
Thanks 😀! @aelaraji I am working on a fork now because the new version will break the current code. Therefore, I will upgrade the current repository (https://codeberg.org/deadblackclover/twtxt-el). The original author is helping me with reviews. I am sorry for my long development, I am working in my free time and it is scarce. I will report back to you all. 😋
I'm still making progress with the Emacs client. I'm proud to say that the code that is responsible for reading the feeds is almost finished, including: Twt Hash Extension, Twt Subject Extension, Multiline Extension and Metadata Extension. I'm fine-tuning some tests and will soon do the first buffer that displays the twts.
I'm still making progress with the Emacs client. I'm proud to say that the code that is responsible for reading the feeds is almost finished, including: Twt Hash Extension, Twt Subject Extension, Multiline Extension and Metadata Extension. I'm fine-tuning some tests and will soon do the first buffer that displays the twts.
I'm still making progress with the Emacs client. I'm proud to say that the code that is responsible for reading the feeds is almost finished, including: Twt Hash Extension, Twt Subject Extension, Multiline Extension and Metadata Extension. I'm fine-tuning some tests and will soon do the first buffer that displays the twts.
@bender Sorry if I don't reply to you. I don't have any mention notification system... at the moment... Thanks for the suggestion and for fix the error 😄
@bender Sorry if I don't reply to you. I don't have any mention notification system... at the moment... Thanks for the suggestion and for fix the error 😄
@bender Sorry if I don't reply to you. I don't have any mention notification system... at the moment... Thanks for the suggestion and for fix the error 😄
I found 2 active Registries: tilde.instite and twtxt.envs.net . I think that is missing a repository or system for them to find each other. It is easy to share registry users. Your work is awesome! Maybe you are supporting twtxt with the pod and software around them. I am very busy with the Emacs client, but I like to work creating my own version of Registry using Django.
I found 2 active Registries: tilde.instite and twtxt.envs.net . I think that is missing a repository or system for them to find each other. It is easy to share registry users. Your work is awesome! Maybe you are supporting twtxt with the pod and software around them. I am very busy with the Emacs client, but I like to work creating my own version of Registry using Django.
I found 2 active Registries: tilde.instite and twtxt.envs.net . I think that is missing a repository or system for them to find each other. It is easy to share registry users. Your work is awesome! Maybe you are supporting twtxt with the pod and software around them. I am very busy with the Emacs client, but I like to work creating my own version of Registry using Django.
Thanks @bender for the feedback. I fixed and expanded the article. I'm sorry for my poor interaction. Furthermore, I'm reading and writing while programming a client in Emacs.
Thanks @bender for the feedback. I fixed and expanded the article. I'm sorry for my poor interaction. Furthermore, I'm reading and writing while programming a client in Emacs.
#emacs #twtxt