# 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 987
# self = https://watcher.sour.is?uri=http://darch.dk/twtxt.txt&offset=379
# next = https://watcher.sour.is?uri=http://darch.dk/twtxt.txt&offset=479
# prev = https://watcher.sour.is?uri=http://darch.dk/twtxt.txt&offset=279
double posting?
double posting?
@movq For syncing notes between computers and phones I've been very happy with Simple Text - w Dropbox sync for some year, but transitioned to Joplin around new year. Both sync via Dropbox and for Joplin there are also more free options. I guess you could even use something like Syncthing
@movq For syncing notes between computers and phones I've been very happy with Simple Text - w Dropbox sync for some year, but transitioned to Joplin around new year. Both sync via Dropbox and for Joplin there are also more free options. I guess you could even use something like Syncthing
@movq For syncing notes between computers and phones I've been very happy with Simple Text - w Dropbox sync for some year, but transitioned to Joplin around new year. Both sync via Dropbox and for Joplin there are also more free options. I guess you could even use something like Syncthing2024-03-16T16:40:21Z\tstill okay?
@movq For syncing notes between computers and phones I've been very happy with Simple Text - w Dropbox sync for some year, but transitioned to Joplin around new year. Both sync via Dropbox and for Joplin there are also more free options. I guess you could even use something like Syncthing
@movq For syncing notes between computers and phones I've been very happy with Simple Text - w Dropbox sync for some year, but transitioned to Joplin around new year. Both sync via Dropbox and for Joplin there are also more free options. I guess you could even use something like Syncthing
@movq For syncing notes between computers and phones I've been very happy with Simple Text - w Dropbox sync for some year, but transitioned to Joplin around new year. Both sync via Dropbox and for Joplin there are also more free options. I guess you could even use something like Syncthing
@movq For syncing notes between computers and phones I've been very happy with Simple Text - w Dropbox sync for some year, but transitioned to Joplin around new year. Both sync via Dropbox and for Joplin there are also more free options. I guess you could even use something like Syncthing
Also made a webfinger lookup resolver that works with my own webfinger endpoint as well as yarnd servers:
http://darch.dk/wf-lookup.php
Also made a webfinger lookup resolver that works with my own webfinger endpoint as well as yarnd servers:
http://darch.dk/wf-lookup.php
Also made a webfinger lookup resolver that works with my own webfinger endpoint as well as yarnd servers:
http://darch.dk/wf-lookup.php
Also made a webfinger lookup resolver that works with my own webfinger endpoint as well as yarnd servers: http://darch.dk/wf-loopup.php
Also made a webfinger lookup resolver that works with my own webfinger endpoint as well as yarnd servers:
http://darch.dk/wf-lookup.php
Just hacked together this small webfinger endpoint to be used as a companion with timeline: .well-known/webfinger/index.php at main · sorenpeter/timeline
Just hacked together this small webfinger endpoint to be used as a companion with timeline: .well-known/webfinger/index.php at main · sorenpeter/timeline
Just hacked together this small webfinger endpoint to be used as a companion with timeline: .well-known/webfinger/index.php at main · sorenpeter/timeline
Just hacked together this small webfinger endpoint to be used as a companion with timeline: .well-known/webfinger/index.php at main · sorenpeter/timeline
Did another write up on #webfinger and DIDs for twtxt/yarn that you can read and edit/comment in: [User lookup for twtxt/yarn - Webfinger or Decentralized Identifiers (DIDs) - HedgeDoc](https://docs.mills.io/rRpmdWHRT7Kg7nTYnXleSg?view)
Did another write up on #webfinger and DIDs for twtxt/yarn that you can read and edit/comment in: [User lookup for twtxt/yarn - Webfinger or Decentralized Identifiers (DIDs) - HedgeDoc](https://docs.mills.io/rRpmdWHRT7Kg7nTYnXleSg?view)
Did another write up on #webfinger and DIDs for twtxt/yarn that you can read and edit/comment in: [User lookup for twtxt/yarn - Webfinger or Decentralized Identifiers (DIDs) - HedgeDoc](https://docs.mills.io/rRpmdWHRT7Kg7nTYnXleSg?view)
Did another write up on #webfinger and DIDs for twtxt/yarn that you can read and edit/comment in: [User lookup for twtxt/yarn - Webfinger or Decentralized Identifiers (DIDs) - HedgeDoc](https://docs.mills.io/rRpmdWHRT7Kg7nTYnXleSg?view)
Did another write up on #webfinger and DIDs for twtxt/yarn that you can read and edit/comment in: [User lookup for twtxt/yarn - Webfinger or Decentralized Identifiers (DIDs) - HedgeDoc](https://docs.mills.io/rRpmdWHRT7Kg7nTYnXleSg?view)
I've gathers my ideas about mentions for twtxt/yarn here: Webmentions vs. custom mentions spec for twtxt/yarn - HedgeDoc
You are welcome to edit and comment in the doc, so our ideas are not fragment into a bunch of treads
I've gathers my ideas about mentions for twtxt/yarn here: Webmentions vs. custom mentions spec for twtxt/yarn - HedgeDoc
You are welcome to edit and comment in the doc, so our ideas are not fragment into a bunch of treads
I've gathers my ideas about mentions for twtxt/yarn here: Webmentions vs. custom mentions spec for twtxt/yarn - HedgeDoc
You are welcome to edit and comment in the doc, so our ideas are not fragment into a bunch of treads
I've gathers my ideas about mentions for twtxt/yarn here: Webmentions vs. custom mentions spec for twtxt/yarn - HedgeDoc
You are welcome to edit and comment in the doc, so our ideas are not fragment into a bunch of treads
I've gathers my ideas about mentions for twtxt/yarn here: Webmentions vs. custom mentions spec for twtxt/yarn - HedgeDoc
You are welcome to edit and comment in the doc, so our ideas are not fragment into a bunch of treads
So where do we start wring down the specs/protocol for twtxt2/yarn?
So where do we start wring down the specs/protocol for twtxt2/yarn?
So where do we start wring down the specs/protocol for twtxt2/yarn?
So where do we start wring down the specs/protocol for twtxt2/yarn?
So where do we start wring down the specs/protocol for twtxt2/yarn?


@shreyan What do you mean when you say federation protocol?

- Either use webfinger for identity like mastodon etc. or use ATproto from Bluesky (or both?)

- We can use webmentions or create our own twt-mentions for notifying someones feed (WIP code at: https://github.com/sorenpeter/timeline/tree/webmention/views)

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


@shreyan What do you mean when you say federation protocol?

- Either use webfinger for identity like mastodon etc. or use ATproto from Bluesky (or both?)

- We can use webmentions or create our own twt-mentions for notifying someones feed (WIP code at: https://github.com/sorenpeter/timeline/tree/webmention/views)

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


@shreyan What do you mean when you say federation protocol?

- Either use webfinger for identity like mastodon etc. or use ATproto from Bluesky (or both?)

- We can use webmentions or create our own twt-mentions for notifying someones feed (WIP code at: https://github.com/sorenpeter/timeline/tree/webmention/views)

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


@shreyan What do you mean when you say federation protocol?

- Either use webfinger for identity like mastodon etc. or use ATproto from Bluesky (or both?)

- We can use webmentions or create our own twt-mentions for notifying someones feed (WIP code at: https://github.com/sorenpeter/timeline/tree/webmention/views)

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
yeah, where and how can we sign up?
yeah, where and how can we sign up?
yeah, where and how can we sign up?
yeah, where and how can we sign up?
Cool news from: https://signal.org/blog/phone-number-privacy-usernames/
Cool news from: https://signal.org/blog/phone-number-privacy-usernames/
Cool news from: https://signal.org/blog/phone-number-privacy-usernames/
Cool news from: https://signal.org/blog/phone-number-privacy-usernames/
It already works: https://webfinger.net/lookup/?resource=xuu%40txt.sour.is
but it not very well described afak
It already works: https://webfinger.net/lookup/?resource=xuu%40txt.sour.is
but it not very well described afak
It already works: https://webfinger.net/lookup/?resource=xuu%40txt.sour.is
but it not very well described afak
It already works: https://webfinger.net/lookup/?resource=xuu%40txt.sour.is
but it not very well described afak
It already works: https://webfinger.net/lookup/?resource=xuu%40txt.sour.is
but it not very well described afak
I like this one the most
I like this one the most
I like this one the most
I like this one the most
I'm also more in favor of #reposts being human readable and writable. A client might implement a bottom that posts something simple like: #repost Look at this cool stuff, because bla bla [alt](url)

This will then make it possible to also "repost" stuff from other platforms/protocols.

The reader part of a client, can then render a preview of the link, which we talked about would be a nice (optional) feature to have in yarnd.
I'm also more in favor of #reposts being human readable and writable. A client might implement a bottom that posts something simple like: #repost Look at this cool stuff, because bla bla [alt](url)

This will then make it possible to also "repost" stuff from other platforms/protocols.

The reader part of a client, can then render a preview of the link, which we talked about would be a nice (optional) feature to have in yarnd.
I'm also more in favor of #reposts being human readable and writable. A client might implement a bottom that posts something simple like: #repost Look at this cool stuff, because bla bla [alt](url)

This will then make it possible to also "repost" stuff from other platforms/protocols.

The reader part of a client, can then render a preview of the link, which we talked about would be a nice (optional) feature to have in yarnd.
I'm also more in favor of #reposts being human readable and writable. A client might implement a bottom that posts something simple like: #repost Look at this cool stuff, because bla bla [alt](url)

This will then make it possible to also "repost" stuff from other platforms/protocols.

The reader part of a client, can then render a preview of the link, which we talked about would be a nice (optional) feature to have in yarnd.
What about using the blockquote format with > ?

> Snippet from someone else's post
> by: @eapl.me

Would it not also make sense to have the repost be a reply to the original post using the (#twthash), and maybe using a tag like #repost so it eaier to filter them out?
What about using the blockquote format with > ?

> Snippet from someone else's post
> by: @eapl.me

Would it not also make sense to have the repost be a reply to the original post using the (#twthash), and maybe using a tag like #repost so it eaier to filter them out?
What about using the blockquote format with > ?

> Snippet from someone else's post
> by: @eapl.me

Would it not also make sense to have the repost be a reply to the original post using the (#twthash), and maybe using a tag like #repost so it eaier to filter them out?
What about using the blockquote format with > ?

> Snippet from someone else's post
> by: @eapl.me

Would it not also make sense to have the repost be a reply to the original post using the (#twthash), and maybe using a tag like #repost so it eaier to filter them out?
What about using the blockquote format?

> Snippet from someone else's post
> by: https://eapl.me/twtxt.txt>

Would it not also make sense to have the repost be a reply to the original post using the (#twthash) ?
danke schøn, yes the idea was that it should work for all feeds
danke schøn, yes the idea was that it should work for all feeds
danke schøn, yes the idea was that it should work for all feeds
danke schøn, yes the idea was that it should work for all feeds
danke schøn, yes the idea was that it should work for all feeds
@johanbove Sounds interesting. It is only for reading or also posting?
@johanbove Sounds interesting. It is only for reading or also posting?
@johanbove Sounds interesting. It is only for reading or also posting?
@johanbove Sounds interesting. It is only for reading or also posting?
I think is part of the code by @eapl.me that I have based my project on. So try to ask him.
I think is part of the code by @eapl.me that I have based my project on. So try to ask him.
I think is part of the code by @eapl.me that I have based my project on. So try to ask him.
I think is part of the code by @eapl.me that I have based my project on. So try to ask him.
one more try
does it need to be a big P?
testing if Y-m-d\\TH:i:sp will give me a Z-sufix
Gracias. Also the git repo now contain code that should actually work
Gracias. Also the git repo now contain code that should actually work
Gracias. Also the git repo now contain code that should actually work
Gracias. Also the git repo now contain code that should actually work
Thanks, but i'm not sure what you mean with _cookies to "verify" my request_ - I don't have Cloudflare on darch.dk
Thanks, but i'm not sure what you mean with _cookies to "verify" my request_ - I don't have Cloudflare on darch.dk
Thanks, but i'm not sure what you mean with "cookies to "verify" my request" - I don't have Cloudflare on darch.dk
Thanks, but i'm not sure what you mean with _cookies to "verify" my request_ - I don't have Cloudflare on darch.dk
Thanks, but i'm not sure what you mean with _cookies to "verify" my request - I don't have Cloudflare on darch.dk_
oh so it did work, just need to make twtxt-php append to the end of file to not confuse myself
oh so it did work, just need to make twtxt-php append to the end of file to not confuse myself
oh so it did work, just need to make twtxt-php append to the end of file to not confuse myself
Testing posting for my new http://darch.dk/timeline/
Testing posting for my new http://darch.dk/timeline/
Testing posting for my new http://darch.dk/timeline/
Testing posting for my new http://darch.dk/timeline/
Preparing visuals for #Kune2023 by coding some new #shaders in #GLSL grid
Preparing visuals for #Kune2023 by coding some new #shaders in #GLSL grid
Preparing visuals for #Kune2023 by coding some new #shaders in #GLSL grid
Preparing visuals for #Kune2023 by coding some new #shaders in #GLSL grid
Preparing visuals for #Kune2023 by coding some new #shaders in #GLSL grid