# 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 196325
# self = https://watcher.sour.is?offset=157799
# next = https://watcher.sour.is?offset=157899
# prev = https://watcher.sour.is?offset=157699
@xuu You're right, it doesn't at the moment, it was primarily used in combination with the activitypub feature. But this is pretty easy to use, as the webfinger part (_at least_) is pretty rock solid (_ActivityPub not so much :/_)
@xuu You're right, it doesn't at the moment, it was primarily used in combination with the activitypub feature. But this is pretty easy to use, as the webfinger part (_at least_) is pretty rock solid (_ActivityPub not so much :/_)
@xuu You're right, it doesn't at the moment, it was primarily used in combination with the activitypub feature. But this is pretty easy to use, as the webfinger part (_at least_) is pretty rock solid (_ActivityPub not so much :/_)
yarnd does not do auto discovery via webfinger though.. i cant put @username and have it fetch the feed url from webfinger. to fully make feeds portable. would also need to be able to use that for hashing.
yarnd does not do auto discovery via webfinger though.. i cant put @username and have it fetch the feed url from webfinger. to fully make feeds portable. would also need to be able to use that for hashing.
@mckinley Also agree, and yarnd already employes the use of WebMentions, WebSub and WebFinger. So maybe this thread can just be about a) documenting/designing the protocol b) building a new Yarn backend and c) Building a new reference frontend?
@mckinley Also agree, and yarnd already employes the use of WebMentions, WebSub and WebFinger. So maybe this thread can just be about a) documenting/designing the protocol b) building a new Yarn backend and c) Building a new reference frontend?
@mckinley Also agree, and yarnd already employes the use of WebMentions, WebSub and WebFinger. So maybe this thread can just be about a) documenting/designing the protocol b) building a new Yarn backend and c) Building a new reference frontend?
Somewhere I read that changing location, like entering a room, can rejigger neural pathways so that some things are associated with the space. It happens to me when picking up a laptop, too. In the moments where I'm drawing a total blank, and then suddenly the thoughts come easily again -- maybe that's my brain looking for the room it was in before.
Somewhere I read that changing location, like entering a room, can rejigger neural pathways so that some thoughts and memories are somehow associated with the space. It's the same for me when picking up a laptop. My purpose feels clear until I open a blank web browser window and my mind goes blank, too. In all the moments where I'm drawing a total blank, and then suddenly the thoughts come easily again: maybe that's my brain looking for the room it was in before.
Somewhere I read that changing location, like entering a room, can rejigger neural pathways so that some thoughts and memories are somehow associated with the space. It's the same for me when picking up a laptop. My purpose feels clear until I open a blank web browser window and my mind goes blank, too. In all the moments where I'm drawing a total blank, and then suddenly the thoughts come easily again: maybe that's my brain looking for the room it was in before.
I'm not sure we need much else. I would not even bother with encryption since other platforms does that better, and for me twtxt/yarn/timeline is for making things public
I'm not sure we need much else. I would not even bother with encryption since other platforms does that better, and for me twtxt/yarn/timeline is for making things public
I'm not sure we need much else. I would not even bother with encryption since other platforms does that better, and for me twtxt/yarn/timeline is for making things public
I'm not sure we need much else. I would not even bother with encryption since other platforms does that better, and for me twtxt/yarn/timeline is for making things public
We can start this thread off by listing some ofd the problems that exist today:
- There is no identity of a feed per se. This makes moving feeds to another location hard(er). - There is no way to notify a feed in any way (e.g: -mention someone) -- It's a 1-way street. - _what else?__
We can start this thread off by listing some ofd the problems that exist today:
- There is no identity of a feed per se. This makes moving feeds to another location hard(er). - There is no way to notify a feed in any way (e.g: -mention someone) -- It's a 1-way street. - _what else?__
We can start this thread off by listing some ofd the problems that exist today:
- There is no identity of a feed per se. This makes moving feeds to another location hard(er). - There is no way to notify a feed in any way (e.g: -mention someone) -- It's a 1-way street. - _what else?__
@shreyan This is a brilliant idea! 💡I've got ideas too! I'd like to even share/borrow some ideas from some of the work we did in Salty IM too 👌 -- What have you got in mind? -- As an aside, it _might_ also be worth (finally?) just re-imagining Twtxt? (_perhaps we can still support the old legacy twtxt though but keep it completely a separate thing design/software wise?_)_
@shreyan This is a brilliant idea! 💡I've got ideas too! I'd like to even share/borrow some ideas from some of the work we did in Salty IM too 👌 -- What have you got in mind? -- As an aside, it _might_ also be worth (finally?) just re-imagining Twtxt? (_perhaps we can still support the old legacy twtxt though but keep it completely a separate thing design/software wise?_)_
@shreyan This is a brilliant idea! 💡I've got ideas too! I'd like to even share/borrow some ideas from some of the work we did in Salty IM too 👌 -- What have you got in mind? -- As an aside, it _might_ also be worth (finally?) just re-imagining Twtxt? (_perhaps we can still support the old legacy twtxt though but keep it completely a separate thing design/software wise?_)_
@mckinley Woah, how cool is that!? :-D Thank you! <3 I'm sure gron will come in very handy some day, now that I have it in my tool bag. My jq skills are pretty much non-existent, though. I don't use it often enough.
Pinellas County Running: 3.02 miles, 00:09:02 average pace, 00:27:18 duration testing out the left knee again, but in the real world. it was fine, took it easy but not super easy so it was a good test. #running
Moderate: 3.02 miles, 00:09:02 average pace, 00:27:18 duration testing out the left knee again, but in the real world. it was fine. took it easy but not super easy so it was a good test. #running
Moderate: 3.02 miles, 00:09:02 average pace, 00:27:18 duration testing out the left knee again, but in the real world. it was fine. took it easy but not super easy so it was a good test. #running
Moderate: 3.02 miles, 00:09:02 average pace, 00:27:18 duration testing out the left knee again, but in the real world. it was fine. took it easy but not super easy so it was a good test. #running
@xuu Cool! I particularly like the idea of converting it into a grep-able version, that's very neat. Interesting choice of aligning the colons at the values and not the keys, I think I never came across this.
@movq completely agree. Also, love the ability Thunderbird used to have (don't know if still does, don't use it) to allow searching for message-id, which we could use to edit emails to fix threats. I used to do it in Mutt too.
@mckinley I hear you, that's why I prefer * as the bullet point wherever possible, e.g. markdown and RST. Not sure if YAML has it, too. I just know at work we use - for lists as well. But then use blank lines to separate list items that are spanning multiple lines. That helps a bit.
Not making THREADING the default view of e-mail clients and thus teaching users that e-mail is “chaotic” (if you get a lot of mail, it becomes unusable without threading) and “needs” full quoting all the time was one of the worst mistakes ever.
Not making THREADING the default view of e-mail clients and thus teaching users that e-mail is “chaotic” (if you get a lot of mail, it becomes unusable without threading) and “needs” full quoting all the time was one of the worst mistakes ever.
Not making THREADING the default view of e-mail clients and thus teaching users that e-mail is “chaotic” (if you get a lot of mail, it becomes unusable without threading) and “needs” full quoting all the time was one of the worst mistakes ever.
['Esperando a la siguiente vacuna 💉\nEsta canción es perfecta para acompañar la foto: ', {'type': 'link', 'text': 'https://youtu.be/iYYRH4apXDo?si=T12gygiPlpJqpGh_'}, ''] #catsoftwtxt
#catsoftwtxt
/https://duque-terron.cat/media/photos/photo_8929-02-2024_23-18-39.jpg) #catsoftwtxt
#catsoftwtxt
/https://duque-terron.cat/media/photos/photo_8829-02-2024_10-58-27.jpg) #catsoftwtxt