# 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 1000
# self = https://watcher.sour.is?uri=http://darch.dk/twtxt.txt&offset=600
# next = https://watcher.sour.is?uri=http://darch.dk/twtxt.txt&offset=700
# prev = https://watcher.sour.is?uri=http://darch.dk/twtxt.txt&offset=500
Thank you @aelaraji, I'm glad you like it. I use PHP because it's everywhere on cheap hosting and no need for the user to log into a terminal to setup it up. Timeline is not mean to be use locally. For that I think something like twtxt2html is a better fit. (and happy to see you using simple.css on you new log page;)
Thank you @aelaraji, I'm glad you like it. I use PHP because it's everywhere on cheap hosting and no need for the user to log into a terminal to setup it up. Timeline is not mean to be use locally. For that I think something like twtxt2html is a better fit. (and happy to see you using simple.css on you new log page;)
Thank you @aelaraji, I'm glad you like it. I use PHP because it's everywhere on cheap hosting and no need for the user to log into a terminal to setup it up. Timeline is not mean to be use locally. For that I think something like twtxt2html is a better fit. (and happy to see you using simple.css on you new log page;)
Thank you @aelaraji, I'm glad you like it. I use PHP because it's everywhere on cheap hosting and no need for the user to log into a terminal to setup it up. Timeline is not mean to be use locally. For that I think something like twtxt2html is a better fit. (and happy to see you using simple.css on you new log page;)
I was not suggesting to that everyone need to setup a working webfinger endpoint, but that we take the format of nick+(sub)domain as base for generating the hashed together with the message date and content.

If we omit the protocol prefix from the way we do things now will that not solve most of the problems? In the case of gemini://gemini.ctrl-c.club/~nristen/twtxt.txt they also have a working twtxt.txt at https://ctrl-c.club/~nristen/twtxt.txt ... damn I just notice the gemini. subdomain.

Okay what about defining a prefers protocol as part of the hash schema? so 1: https , 2: http 3: gemini 4: gopher ?
I was not suggesting to that everyone need to setup a working webfinger endpoint, but that we take the format of nick+(sub)domain as base for generating the hashed together with the message date and content.

If we omit the protocol prefix from the way we do things now will that not solve most of the problems? In the case of gemini://gemini.ctrl-c.club/~nristen/twtxt.txt they also have a working twtxt.txt at https://ctrl-c.club/~nristen/twtxt.txt ... damn I just notice the gemini. subdomain.

Okay what about defining a prefers protocol as part of the hash schema? so 1: https , 2: http 3: gemini 4: gopher ?
I was not suggesting to that everyone need to setup a working webfinger endpoint, but that we take the format of nick+(sub)domain as base for generating the hashed together with the message date and content.

If we omit the protocol prefix from the way we do things now will that not solve most of the problems? In the case of gemini://gemini.ctrl-c.club/~nristen/twtxt.txt they also have a working twtxt.txt at https://ctrl-c.club/~nristen/twtxt.txt ... damn I just notice the gemini. subdomain.

Okay what about defining a prefers protocol as part of the hash schema? so 1: https , 2: http 3: gemini 4: gopher ?
I was not suggesting to that everyone need to setup a working webfinger endpoint, but that we take the format of nick+(sub)domain as base for generating the hashed together with the message date and content.

If we omit the protocol prefix from the way we do things now will that not solve most of the problems? In the case of gemini://gemini.ctrl-c.club/~nristen/twtxt.txt they also have a working twtxt.txt at https://ctrl-c.club/~nristen/twtxt.txt ... damn I just notice the gemini. subdomain.

Okay what about defining a prefers protocol as part of the hash schema? so 1: https , 2: http 3: gemini 4: gopher ?
@prologic do that mean that for every new post (not replies) the client will have to generate a UUID or similar when posting and add that to to the twt?
@prologic do that mean that every new post (not replies) will have to generate their own UUID or similar when posting?
@prologic do that mean that for every new post (not replies) the client will have to generate a UUID or similar when posting and add that to to the twt?
@prologic do that mean that for every new post (not replies) the client will have to generate a UUID or similar when posting and add that to to the twt?
@prologic do that mean that for every new post (not replies) the client will have to generate a UUID or similar when posting and add that to to the twt?
how little data is needed for generating the hashes? Instead of the full URL, can we makedo with just the domain (example.net) so we avoid the conflicts with gemini://, https:// and only http:// (like in my own twtxt.txt) or construct something like like a webfinger id nick@domain (also used by mastodon etc.) from the domain and nick if there, else use domain as nick as well
how little data is needed for generating the hashes? Instead of the full URL, can we makedo with just the domain (example.net) so we avoid the conflicts with gemini://, https:// and only http:// (like in my own twtxt.txt) or construct something like like a webfinger id nick@domain (also used by mastodon etc.) from the domain and nick if there, else use domain as nick as well
how little data is needed for generating the hashes? Instead of the full URL, can we makedo with just the domain (example.net) so we avoid the conflicts with gemini://, https:// and only http:// (like in my own twtxt.txt) or construct something like like a webfinger id nick@domain (also used by mastodon etc.) from the domain and nick if there, else use domain as nick as well
how little data is needed for generating the hashes? Instead of the full URL, can we makedo with just the domain (example.net) so we avoid the conflicts with gemini://, https:// and only http:// (like in my own twtxt.txt) or construct something like like a webfinger id nick@domain (also used by mastodon etc.) from the domain and nick if there, else use domain as nick as well
For following notifications I would say use webmetion refering to the the line in your twtxt.txt as per: https://darch.dk/mentions-twtxt
Or send them an email, so it would be an idea to add a # contact = mailto:me@domain.net to ones twtxt.txt
For following notifications I would say use webmetion refering to the the line in your twtxt.txt as per: https://darch.dk/mentions-twtxt
Or send them an email, so it would be an idea to add a # contact = mailto:me@domain.net to ones twtxt.txt
For following notifications I would say use webmetion refering to the the line in your twtxt.txt as per: https://darch.dk/mentions-twtxt
Or send them an email, so it would be an idea to add a # contact = mailto:me@domain.net to ones twtxt.txt
For following notifications I would say use webmetion refering to the the line in your twtxt.txt as per: https://darch.dk/mentions-twtxt
Or send them an email, so it would be an idea to add a # contact = mailto:me@domain.net to ones twtxt.txt
This reminds me of this video: The Biggest Gap in Science: Complexity
However you might end up with more questions (complexity?) than answers (simplicity?)
This reminds me of this video: The Biggest Gap in Science: Complexity
However you might end up with more questions (complexity?) than answers (simplicity?)
This reminds me of this video: The Biggest Gap in Science: Complexity
However you might end up with more questions (complexity?) than answers (simplicity?)
This reminds me of this video: The Biggest Gap in Science: Complexity
However you might end up with more questions (complexity?) than answers (simplicity?)
Have not tried any of them, but some of these seem to fit the bill:
- https://chromewebstore.google.com/search/Redirector
- https://libredirect.github.io/
- https://requestly.com/products/web-debugger/
Have not tried any of them, but some of these seem to fit the bill:
- https://chromewebstore.google.com/search/Redirector
- https://libredirect.github.io/
- https://requestly.com/products/web-debugger/
Have not tried any of them, but some of these seem to fit the bill:
- https://chromewebstore.google.com/search/Redirector
- https://libredirect.github.io/
- https://requestly.com/products/web-debugger/
Have not tried any of them, but some of these seem to fit the bill:
- https://chromewebstore.google.com/search/Redirector
- https://libredirect.github.io/
- https://requestly.com/products/web-debugger/
ok != perfect
ok != perfect
ok != perfect
ok != perfect
It looks okay on my timeline: http://darch.dk/timeline/conv/omu7e4q
It looks okay on my timeline: http://darch.dk/timeline/conv/omu7e4q
It looks okay on my timeline: http://darch.dk/timeline/conv/omu7e4q
It looks okay on my timeline: http://darch.dk/timeline/conv/omu7e4q
@prologic The old options are still valid, so "Show latest post per feed" should just be added as a 3th.
@prologic The old options are still valid, so "Show latest post per feed" should just be added as a 3th.
@prologic The old options are still valid, so "Show latest post per feed" should just be added as a 3th.
@prologic The old options are still valid, so "Show latest post per feed" should just be added as a 3th.
I think it is a good addition. Similar to how the Fraidycat RSS reader works. Fraidyc.at also support twtxt, but have not seen any updates since 2021...
I think it is a good addition. Similar to how the Fraidycat RSS reader works. Fraidyc.at also support twtxt, but have not seen any updates since 2021...
I think it is a good addition. Similar to how the Fraidycat RSS reader works. Fraidyc.at also support twtxt, but have not seen any updates since 2021...
I think it is a good addition. Similar to how the Fraidycat RSS reader works. Fraidyc.at also support twtxt, but have not seen any updates since 2021...
Here now too
Here now too
Here now too
Here now too
echo chambers?
echo chambers?
echo chambers?
echo chambers?
I fixed it by adding (?<!\S) to the regex filter. But what is going on with the ?nick=dbucklin anyhow?
I fixed it by adding (?<!\S) to the regex filter. But what is going on with the ?nick=dbucklin anyhow?
I fixed it by adding (?<!\S) to the regex filter. But what is going on with the ?nick=dbucklin anyhow?
I fixed it by adding (?<!\\S) to the regex filter. But what is going on with the ?nick=dbucklin anyhow?
I fixed it by adding (?<!\S) to the regex filter. But what is going on with the ?nick=dbucklin anyhow?
@Prologic can you pleas fix this line in your twtxt.txt:
# follow = dbucklin@www.davebucklin.com https://www.davebucklin.com/twtxt.txt?nick=dbucklin


It is cause this weird effect on my timeline, where you are now called dbucklin
http://darch.dk/timeline/?profile=https://twtxt.net/user/prologic/twtxt.txt
@Prologic can you pleas fix this line in your twtxt.txt:
# follow = dbucklin@www.davebucklin.com https://www.davebucklin.com/twtxt.txt?nick=dbucklin


It is cause this weird effect on my timeline, where you are now called dbucklin
http://darch.dk/timeline/?profile=https://twtxt.net/user/prologic/twtxt.txt
@Prologic can you pleas fix this line in your twtxt.txt:
# follow = dbucklin@www.davebucklin.com https://www.davebucklin.com/twtxt.txt?nick=dbucklin


It is cause this weird effect on my timeline, where you are now called dbucklin
http://darch.dk/timeline/?profile=https://twtxt.net/user/prologic/twtxt.txt
@Prologic can you pleas fix this line in your twtxt.txt:
# follow = dbucklin@www.davebucklin.com https://www.davebucklin.com/twtxt.txt?nick=dbucklin


It is cause this weird effect on my timeline, where you are now called dbucklin
http://darch.dk/timeline/?profile=https://twtxt.net/user/prologic/twtxt.txt
@movq Maybe something for you: 7.css - A CSS framework for recreating Windows 7 UI
@movq Maybe something for you: 7.css - A CSS framework for recreating Windows 7 UI
@movq Maybe something for you: 7.css - A CSS framework for recreating Windows 7 UI
@movq Maybe something for you: 7.css - A CSS framework for recreating Windows 7 UI
@prologic Haha, that sh@t is pure (net)art!
@prologic Haha, that sh@t is pure (net)art!
@prologic Haha, that sh@t is pure (net)art!
@prologic Haha, that sh@t is pure (net)art!
@dfaria the difference is that these other servers does not post several times a day with content that are not informative/interesting to people outside your academic context, which can be perceived as noise.

What @prologic have done is what I would call curation of the service he offers to the world for free (as in beer). It's no one right to have their posts syndicated to the frontpage of twtxt.net, it's simply a gift he gives to the world and he is free (as in speak) to wrap is anyway he sees fit.

@dfaria.eu I hope you stay around 🌞
@dfaria the difference is that these other servers does not post several times a day with content that are not informative/interesting to people outside your academic context, which can be perceived as noise.

What @prologic have done is what I would call curation of the service he offers to the world for free (as in beer). It's no one right to have their posts syndicated to the frontpage of twtxt.net, it's simply a gift he gives to the world and he is free (as in speak) to wrap is anyway he sees fit.

@dfaria.eu I hope you stay around 🌞
@dfaria the difference is that these other servers does not post several times a day with content that are not informative/interesting to people outside your academic context, which can be perceived as noise.

What @prologic have done is what I would call curation of the service he offers to the world for free (as in beer). It's no one right to have their posts syndicated to the frontpage of twtxt.net, it's simply a gift he gives to the world and he is free (as in speak) to wrap is anyway he sees fit.

@dfaria.eu I hope you stay around 🌞
@dfaria the difference is that these other servers does not post several times a day with content that are not informative/interesting to people outside your academic context, which can be perceived as noise.

What @prologic have done is what I would call curation of the service he offers to the world for free (as in beer). It's no one right to have their posts syndicated to the frontpage of twtxt.net, it's simply a gift he gives to the world and he is free (as in speak) to wrap is anyway he sees fit.

@dfaria.eu I hope you stay around 🌞
@prologic and @bender for a start a single user twtxt/yarn pod could look like this 😉
@prologic and @bender for a start a single user twtxt/yarn pod could look like this 😉
@prologic and @bender for a start a single user twtxt/yarn pod could look like this 😉
@prologic and @bender for a start a single user twtxt/yarn pod could look like this 😉
I just "published" a #draft on my blog about "How I've implemented #webmentions for twtxt" (http://darch.dk/mentions-twtxt), so I wanted to know from you guys if you see yourself doing a similar thing with yarnd @prologic or others with custom setups?
I just "published" a #draft on my blog about "How I've implemented #webmentions for twtxt" (http://darch.dk/mentions-twtxt), so I wanted to know for you guys if you see yourself doing a similar thing with yarnd @prologic or others with custom setups?
I just "published" a #draft on my blog about "How I've implemented #webmentions for twtxt" (http://darch.dk/mentions-twtxt), so I wanted to know from you guys if you see yourself doing a similar thing with yarnd @prologic or others with custom setups?
I just "published" a #draft on my blog about "How I've implemented #webmentions for twtxt" (http://darch.dk/mentions-twtxt), so I wanted to know from you guys if you see yourself doing a similar thing with yarnd @prologic or others with custom setups?
I just "published" a #draft on my blog about "How I've implemented #webmentions for twtxt" (http://darch.dk/mentions-twtxt), so I wanted to know from you guys if you see yourself doing a similar thing with yarnd @prologic or others with custom setups?
The wording can be more subtle like "This feed have not seen much activity within the last year" and maybe adding a UI like I did in timeline showing time ago for all feeds

I agree that it good to clean up the Mastodon re-feeds, but it should also be okay for anyone to spin up a twtxt.txt just for syndicating they stuff from blog or what ever.

The "not receiving replies" could partly be fixed by implementing a working webmentions for twtxt.txt
The wording can be more subtle like "This feed have not seen much activity within the last year" and maybe adding a UI like I did in timeline showing time ago for all feeds

I agree that it good to clean up the Mastodon re-feeds, but it should also be okay for anyone to spin up a twtxt.txt just for syndicating they stuff from blog or what ever.

The "not receiving replies" could partly be fixed by implementing a working webmentions for twtxt.txt
The wording can be more subtle like "This feed have not seen much activity within the last year" and maybe adding a UI like I did in timeline showing time ago for all feeds

I agree that it good to clean up the Mastodon re-feeds, but it should also be okay for anyone to spin up a twtxt.txt just for syndicating they stuff from blog or what ever.

The "not receiving replies" could partly be fixed by implementing a working webmentions for twtxt.txt
The wording can be more subtle like "This feed have not seen much activity within the last year" and maybe adding a UI like I did in timeline showing time ago for all feeds

I agree that it good to clean up the Mastodon re-feeds, but it should also be okay for anyone to spin up a twtxt.txt just for syndicating they stuff from blog or what ever.

The "not receiving replies" could partly be fixed by implementing a working webmentions for twtxt.txt
Just fleshed out the README for timeline at https://github.com/sorenpeter/timeline - Comments/corrections and PRs are welcome:)
Just fleshed out the README for timeline at https://github.com/sorenpeter/timeline - Comments/corrections and PRs are welcome:)
Just fleshed out the README for timeline at https://github.com/sorenpeter/timeline - Comments/corrections and PRs are welcome:)
Just fleshed out the README for timeline at https://github.com/sorenpeter/timeline - Comments/corrections and PRs are welcome:)
@hecanjog You need to include the full URL for the audio file for this to work across servers/pods ;)
@hecanjog You need to include the full URL for the audio file for this to work across servers/pods ;)
@hecanjog You need to include the full URL for the audio file for this to work across servers/pods ;)
@hecanjog You need to include the full URL for the audio file for this to work across servers/pods ;)
yes i know @bender, it's on my to-do
yes i know @bender, it's on my to-do
yes i know @bender, it's on my to-do
yes i know @bender, it's on my to-do
yes i know @bender, it's on my to-do