# 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 23
# self = https://watcher.sour.is/conv/vbhvpda
Experimenting with “replace all newlines by U+2028 when writing twts”.
Foo!
Bar!
- This is a list.
- This is another item on the list.
And then she said:
> Look, a tree!
It’s not that bad. 🤔 I just have to set my Vim to not do hard line-wrapping in jenny postings (which it does by default for all plain text files). So I now have this in my ~/.vimrc:
au BufRead,BufNewFile jenny-posting.eml call SetForumWrapping()
Experimenting with “replace all newlines by U+2028 when writing twts”.
Foo!
Bar!
- This is a list.
- This is another item on the list.
And then she said:
> Look, a tree!
It’s not that bad. 🤔 I just have to set my Vim to not do hard line-wrapping in jenny postings (which it does by default for all plain text files). So I now have this in my ~/.vimrc:
au BufRead,BufNewFile jenny-posting.eml call SetForumWrapping()
Experimenting with “replace all newlines by U+2028 when writing twts”.
Foo!
Bar!
- This is a list.
- This is another item on the list.
And then she said:
> Look, a tree!
It’s not that bad. 🤔 I just have to set my Vim to not do hard line-wrapping in jenny postings (which it does by default for all plain text files). So I now have this in my ~/.vimrc:
au BufRead,BufNewFile jenny-posting.eml call SetForumWrapping()
Speaking of Vim: It might be a good idea to write a twtxt syntax highlighting file, which extends the markdown one. 🤔 But then again, the currently used “mail” syntax highlighting is not that bad either, *and* it get’s nested quoting right:
\n\nSpeaking of Vim: It might be a good idea to write a twtxt syntax highlighting file, which extends the markdown one. 🤔 But then again, the currently used “mail” syntax highlighting is not that bad either, *and* it get’s nested quoting right:\n\n
Speaking of Vim: It might be a good idea to write a twtxt syntax highlighting file, which extends the markdown one. 🤔 But then again, the currently used “mail” syntax highlighting is not that bad either, *and* it get’s nested quoting right:
Speaking of Vim: It might be a good idea to write a twtxt syntax highlighting file, which extends the markdown one. 🤔 But then again, the currently used “mail” syntax highlighting is not that bad either, *and* it get’s nested quoting right:
Works well 👌
Works well 👌\n\n
Works well 👌
\n\nAlright, I think I like it. I pushed the changes. FYI @quark\n\nThat’s enough changes for now. I’ll let things settle for a while, fix bugs (if we’re finding any), maybe add some more tests, and then go for a new release. 🥳
Alright, I think I like it. I pushed the changes. FYI @quark
That’s enough changes for now. I’ll let things settle for a while, fix bugs (if we’re finding any), maybe add some more tests, and then go for a new release. 🥳
Alright, I think I like it. I pushed the changes. FYI @quark
That’s enough changes for now. I’ll let things settle for a while, fix bugs (if we’re finding any), maybe add some more tests, and then go for a new release. 🥳
Alright, I think I like it. I pushed the changes. FYI @quark
That’s enough changes for now. I’ll let things settle for a while, fix bugs (if we’re finding any), maybe add some more tests, and then go for a new release. 🥳
@movq Awesome! About to git pull, and check it out. Thanks!
It work like a bliss, and it is exactly what I wanted. I don't often see the need to use new lines but having the ability to do so add richness to the whole experience. Thank you very much, again, for listening and implementing this!
\nIt work like a bliss, and it is exactly what I wanted. I don't often see the need to use new lines but having the ability to do so add richness to the whole experience. Thank you very much, again, for listening and implementing this!
@quark You’re welcome! 😊 Yeah, I’m convinced myself that it’s better this way. 👌
@quark You’re welcome! 😊 Yeah, I’m convinced myself that it’s better this way. 👌
@quark You’re welcome! 😊 Yeah, I’m convinced myself that it’s better this way. 👌