# 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 61080
# self = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=42691
# next = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=42791
# prev = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=42591
@carsten Nice! πŸ‘Œ
@carsten Nice! πŸ‘Œ
@carsten Nice! πŸ‘Œ
@carsten Nice! πŸ‘Œ
@abucci Do you want this in the logs? Info maybe? Warn? πŸ€”
@abucci Do you want this in the logs? Info maybe? Warn? πŸ€”
@abucci Do you want this in the logs? Info maybe? Warn? πŸ€”
@abucci Do you want this in the logs? Info maybe? Warn? πŸ€”
Hmmm nothing wrong with the code:


DEBU[0005] not refreshing feed https://kolesnikov.se/twtxt.txt with refresh=7200s (1h47m38.99999925s before next refresh)
Hmmm nothing wrong with the code:


DEBU[0005] not refreshing feed https://kolesnikov.se/twtxt.txt with refresh=7200s (1h47m38.99999925s before next refresh)
Hmmm nothing wrong with the code:


DEBU[0005] not refreshing feed https://kolesnikov.se/twtxt.txt with refresh=7200s (1h47m38.99999925s before next refresh)
Hmmm nothing wrong with the code:


DEBU[0005] not refreshing feed https://kolesnikov.se/twtxt.txt with refresh=7200s (1h47m38.99999925s before next refresh)
Oh I know that person πŸ‘Œ Lemme confirm something locally real quick πŸ‘Œ
Oh I know that person πŸ‘Œ Lemme confirm something locally real quick πŸ‘Œ
Oh I know that person πŸ‘Œ Lemme confirm something locally real quick πŸ‘Œ
Oh I know that person πŸ‘Œ Lemme confirm something locally real quick πŸ‘Œ
@abucci Do you happen to have the feed uri handy? πŸ€”
@abucci Do you happen to have the feed uri handy? πŸ€”
@abucci Do you happen to have the feed uri handy? πŸ€”
@abucci Do you happen to have the feed uri handy? πŸ€”
@movq Come to think of it, it's actually an appealing "options" thing to support anyway I _think_. It sure does make looking things up a lot easier. It makes no difference to us now, since we all follow each other and have webb established clients and following maps, but if we think another few years from now how things might evolve, new users might appreciate a more "straight forward" mechanisms/lookup and address/identity.
@movq Come to think of it, it's actually an appealing "options" thing to support anyway I _think_. It sure does make looking things up a lot easier. It makes no difference to us now, since we all follow each other and have webb established clients and following maps, but if we think another few years from now how things might evolve, new users might appreciate a more "straight forward" mechanisms/lookup and address/identity.
@movq Come to think of it, it's actually an appealing "options" thing to support anyway I _think_. It sure does make looking things up a lot easier. It makes no difference to us now, since we all follow each other and have webb established clients and following maps, but if we think another few years from now how things might evolve, new users might appreciate a more "straight forward" mechanisms/lookup and address/identity.
@movq Come to think of it, it's actually an appealing "options" thing to support anyway I _think_. It sure does make looking things up a lot easier. It makes no difference to us now, since we all follow each other and have webb established clients and following maps, but if we think another few years from now how things might evolve, new users might appreciate a more "straight forward" mechanisms/lookup and address/identity.
@darch If we want to make follow users and cross-pod mentioning easier for users, I _would_ just drop the whole Twtxt feed URi entirely and just use webfinger period. Its far easier for non-technical people to reason about if we do that. Of course the actual Twtxt feed URL(s) are still there, just abstracted away from the users.
@darch If we want to make follow users and cross-pod mentioning easier for users, I _would_ just drop the whole Twtxt feed URi entirely and just use webfinger period. Its far easier for non-technical people to reason about if we do that. Of course the actual Twtxt feed URL(s) are still there, just abstracted away from the users.
@darch If we want to make follow users and cross-pod mentioning easier for users, I _would_ just drop the whole Twtxt feed URi entirely and just use webfinger period. Its far easier for non-technical people to reason about if we do that. Of course the actual Twtxt feed URL(s) are still there, just abstracted away from the users.
@darch If we want to make follow users and cross-pod mentioning easier for users, I _would_ just drop the whole Twtxt feed URi entirely and just use webfinger period. Its far easier for non-technical people to reason about if we do that. Of course the actual Twtxt feed URL(s) are still there, just abstracted away from the users.
And this is true, I wouldn't expect every Twtxt feed on ever web server to have a webfinger service. So we'd have to fallback anyway.
And this is true, I wouldn't expect every Twtxt feed on ever web server to have a webfinger service. So we'd have to fallback anyway.
And this is true, I wouldn't expect every Twtxt feed on ever web server to have a webfinger service. So we'd have to fallback anyway.
And this is true, I wouldn't expect every Twtxt feed on ever web server to have a webfinger service. So we'd have to fallback anyway.
@movq I think the only thing this bus us is "shorter identities" with feed uris that can be looked up and validated, really.
@movq I think the only thing this bus us is "shorter identities" with feed uris that can be looked up and validated, really.
@movq I think the only thing this bus us is "shorter identities" with feed uris that can be looked up and validated, really.
@movq I think the only thing this bus us is "shorter identities" with feed uris that can be looked up and validated, really.
@darch Hmmm πŸ€”
@darch Hmmm πŸ€”
@darch Hmmm πŸ€”
@darch Hmmm πŸ€”
Cool idea though πŸ˜…
Cool idea though πŸ˜…
Cool idea though πŸ˜…
Cool idea though πŸ˜…
I kind of. have a problem with this:

> Don’t share these addresses.
> They contain an identifier that other people could use to send you spam and to control your newsletter subscriptions.

How are you suppose to do that when the same identifier is part of the Atom feed's URI?! πŸ€¦β€β™‚οΈ Hmmm πŸ€”
I kind of. have a problem with this:

> Don’t share these addresses.
> They contain an identifier that other people could use to send you spam and to control your newsletter subscriptions.

How are you suppose to do that when the same identifier is part of the Atom feed's URI?! πŸ€¦β€β™‚οΈ Hmmm πŸ€”
I kind of. have a problem with this:

> Don’t share these addresses.
> They contain an identifier that other people could use to send you spam and to control your newsletter subscriptions.

How are you suppose to do that when the same identifier is part of the Atom feed's URI?! πŸ€¦β€β™‚οΈ Hmmm πŸ€”
I kind of. have a problem with this:

> Don’t share these addresses.
> They contain an identifier that other people could use to send you spam and to control your newsletter subscriptions.

How are you suppose to do that when the same identifier is part of the Atom feed's URI?! πŸ€¦β€β™‚οΈ Hmmm πŸ€”
@movq Yes πŸ‘Œ
@movq Yes πŸ‘Œ
@movq Yes πŸ‘Œ
@movq Yes πŸ‘Œ
@abucci It is however an RFC: https://www.rfc-editor.org/rfc/rfc7033
@abucci It is however an RFC: https://www.rfc-editor.org/rfc/rfc7033
@abucci It is however an RFC: https://www.rfc-editor.org/rfc/rfc7033
@abucci It is however an RFC: https://www.rfc-editor.org/rfc/rfc7033
The _only_ noticeable thing you would see at all is all of a sudden (assuming you followed the old feed and new feed) you would see otherwise identical replies to some "root" that looks like its from two different identifies (feeds)
The _only_ noticeable thing you would see at all is all of a sudden (assuming you followed the old feed and new feed) you would see otherwise identical replies to some "root" that looks like its from two different identifies (feeds)
The _only_ noticeable thing you would see at all is all of a sudden (assuming you followed the old feed and new feed) you would see otherwise identical replies to some "root" that looks like its from two different identifies (feeds)
The _only_ noticeable thing you would see at all is all of a sudden (assuming you followed the old feed and new feed) you would see otherwise identical replies to some "root" that looks like its from two different identifies (feeds)
@abucci Actually it wouldn't change any of the hashes at all. The old Twts from the previous feed's URI would still remain in-tact. In the case of Yarn.social pods running yarnd, they are also archived, the search engine running at search.twtxt.net running yarns would also have indexed them already. Merging an old feed of yours from a different feed URI to a new one would have no impact whatsoever.
@abucci Actually it wouldn't change any of the hashes at all. The old Twts from the previous feed's URI would still remain in-tact. In the case of Yarn.social pods running yarnd, they are also archived, the search engine running at search.twtxt.net running yarns would also have indexed them already. Merging an old feed of yours from a different feed URI to a new one would have no impact whatsoever.
@abucci Actually it wouldn't change any of the hashes at all. The old Twts from the previous feed's URI would still remain in-tact. In the case of Yarn.social pods running yarnd, they are also archived, the search engine running at search.twtxt.net running yarns would also have indexed them already. Merging an old feed of yours from a different feed URI to a new one would have no impact whatsoever.
@abucci Actually it wouldn't change any of the hashes at all. The old Twts from the previous feed's URI would still remain in-tact. In the case of Yarn.social pods running yarnd, they are also archived, the search engine running at search.twtxt.net running yarns would also have indexed them already. Merging an old feed of yours from a different feed URI to a new one would have no impact whatsoever.
New Year, New Avatar πŸ˜…
New Year, New Avatar πŸ˜…
New Year, New Avatar πŸ˜…
New Year, New Avatar πŸ˜…
@notvantablack Hey! πŸ‘‹ Welcome to Yarn.social πŸ€—
@notvantablack Hey! πŸ‘‹ Welcome to Yarn.social πŸ€—
@notvantablack Hey! πŸ‘‹ Welcome to Yarn.social πŸ€—
@notvantablack Hey! πŸ‘‹ Welcome to Yarn.social πŸ€—
@carsten Thank you! πŸ™‡β€β™‚οΈ
@carsten Thank you! πŸ™‡β€β™‚οΈ
@carsten Thank you! πŸ™‡β€β™‚οΈ
@carsten Thank you! πŸ™‡β€β™‚οΈ
@movq There are two primary problems that the use of WebFinger can help solve (that I can think of):

- Conveniently sharing your Yarn.social / Twtxt "identity" with others, much like other competing ecosystems have done. e.g: prologic@twtxt.net (which can be looked up now with a webfinger client)
- Verifying -mentions to be correct, potentially even rewriting them (yarnd does this anyway) to their proper @<url> form(s).
@movq There are two primary problems that the use of WebFinger can help solve (that I can think of):

- Conveniently sharing your Yarn.social / Twtxt "identity" with others, much like other competing ecosystems have done. e.g: prologic@twtxt.net (which can be looked up now with a webfinger client)
- Verifying -mentions to be correct, potentially even rewriting them (yarnd does this anyway) to their proper @<url> form(s).
@movq There are two primary problems that the use of WebFinger can help solve (that I can think of):

- Conveniently sharing your Yarn.social / Twtxt "identity" with others, much like other competing ecosystems have done. e.g: prologic@twtxt.net (which can be looked up now with a webfinger client)
- Verifying -mentions to be correct, potentially even rewriting them (yarnd does this anyway) to their proper @<url> form(s).
@movq There are two primary problems that the use of WebFinger can help solve (that I can think of):

- Conveniently sharing your Yarn.social / Twtxt "identity" with others, much like other competing ecosystems have done. e.g: prologic@twtxt.net (which can be looked up now with a webfinger client)
- Verifying -mentions to be correct, potentially even rewriting them (yarnd does this anyway) to their proper @<url> form(s).
@rsdoiel Not easily at this time, no. We would have to build an API endpoint so you can authenticate and grab an Atom version of your Timeline. I have to ask though... Why? πŸ˜…
@rsdoiel Not easily at this time, no. We would have to build an API endpoint so you can authenticate and grab an Atom version of your Timeline. I have to ask though... Why? πŸ˜…
@rsdoiel Not easily at this time, no. We would have to build an API endpoint so you can authenticate and grab an Atom version of your Timeline. I have to ask though... Why? πŸ˜…
@rsdoiel Not easily at this time, no. We would have to build an API endpoint so you can authenticate and grab an Atom version of your Timeline. I have to ask though... Why? πŸ˜…
@loopsaisei

> @prologic Hey, I had no intent to complain or express frustration. Just really feel excited about what you ppl have created around twtxt and would like to engage to make things better.

This is awesome! πŸ‘Œ We welcome any and all help we can get! πŸ™ We especially need help in the UI/UX side of things, especially on the Mobile App πŸ‘Œ
@loopsaisei

> @prologic Hey, I had no intent to complain or express frustration. Just really feel excited about what you ppl have created around twtxt and would like to engage to make things better.

This is awesome! πŸ‘Œ We welcome any and all help we can get! πŸ™ We especially need help in the UI/UX side of things, especially on the Mobile App πŸ‘Œ
@loopsaisei

> @prologic Hey, I had no intent to complain or express frustration. Just really feel excited about what you ppl have created around twtxt and would like to engage to make things better.

This is awesome! πŸ‘Œ We welcome any and all help we can get! πŸ™ We especially need help in the UI/UX side of things, especially on the Mobile App πŸ‘Œ
@loopsaisei

> @prologic Hey, I had no intent to complain or express frustration. Just really feel excited about what you ppl have created around twtxt and would like to engage to make things better.

This is awesome! πŸ‘Œ We welcome any and all help we can get! πŸ™ We especially need help in the UI/UX side of things, especially on the Mobile App πŸ‘Œ
@darch Why? πŸ€” Clients like twtr and twete are just so much better πŸ˜…
@darch Why? πŸ€” Clients like twtr and twete are just so much better πŸ˜…
@darch Why? πŸ€” Clients like twtr and twete are just so much better πŸ˜…
@darch Why? πŸ€” Clients like twtr and twete are just so much better πŸ˜…
@lyse Well if you're still up for it, I would be more than happy to write the client part itself, as a library that you could "just import". I'd probably base it on the code in yarnd but heavily refactor it and write a shittone more tests πŸ˜… Then eventually replace what yarnd uses too πŸ‘Œ
@lyse Well if you're still up for it, I would be more than happy to write the client part itself, as a library that you could "just import". I'd probably base it on the code in yarnd but heavily refactor it and write a shittone more tests πŸ˜… Then eventually replace what yarnd uses too πŸ‘Œ
@lyse Well if you're still up for it, I would be more than happy to write the client part itself, as a library that you could "just import". I'd probably base it on the code in yarnd but heavily refactor it and write a shittone more tests πŸ˜… Then eventually replace what yarnd uses too πŸ‘Œ
@lyse Well if you're still up for it, I would be more than happy to write the client part itself, as a library that you could "just import". I'd probably base it on the code in yarnd but heavily refactor it and write a shittone more tests πŸ˜… Then eventually replace what yarnd uses too πŸ‘Œ
open to building a new client? As a Go library and Cli?
open to building a new client? As a Go library and Cli?
open to building a new client? As a Go library and Cli?
open to building a new client? As a Go library and Cli?