# 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 61083
# self = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=35491
# next = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=35591
# prev = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=35391
@akoizumi Ahh dam, it was very good πŸ˜…
@akoizumi Ahh dam, it was very good πŸ˜…
@darch I will try then πŸ‘Œ
@darch I will try then πŸ‘Œ
@walves HellO! πŸ‘‹ And you've also found my pod twtxt.net -- Hopefully you see this on Discover soon 🀞 (you don't yet follow anyone -- I'll reply via @support as well just in case...) -- There are a number of clients you can use, the one you're on right now is called yarnd -- What we call a pod, can either by single-user (yourself) or multi-user (yourself + friends, family, etc).
@walves HellO! πŸ‘‹ And you've also found my pod twtxt.net -- Hopefully you see this on Discover soon 🀞 (you don't yet follow anyone -- I'll reply via @support as well just in case...) -- There are a number of clients you can use, the one you're on right now is called yarnd -- What we call a pod, can either by single-user (yourself) or multi-user (yourself + friends, family, etc).
@abucci Ahh fair enough πŸ˜… Totally get where you're coming from πŸ‘Œ I very nearly left Signal myself for similar reasons... I haven't yet, only because Salty.im isn't where I'd like it to be (yet) -- soonβ„’ 🀞 -- I'll catch ya on IRC then, sorry not a fan of XMPP, tried and just keep giving up πŸ˜…
@abucci Ahh fair enough πŸ˜… Totally get where you're coming from πŸ‘Œ I very nearly left Signal myself for similar reasons... I haven't yet, only because Salty.im isn't where I'd like it to be (yet) -- soonβ„’ 🀞 -- I'll catch ya on IRC then, sorry not a fan of XMPP, tried and just keep giving up πŸ˜…
@abucci You are 100% right. Relying on email security is an oxymoron. I'm not sure how many _actually_ use it to auth to their pod, so if there's enough reason to remove it, I'm happy to do so πŸ‘Œ
@abucci You are 100% right. Relying on email security is an oxymoron. I'm not sure how many _actually_ use it to auth to their pod, so if there's enough reason to remove it, I'm happy to do so πŸ‘Œ
Alternatively there is the #Yarn.social IRC channel on Libera Chat if you're in to IRC πŸ˜…
Alternatively there is the #Yarn.social IRC channel on Libera Chat if you're in to IRC πŸ˜…
@abucci Do you happen to use Signal btw? πŸ€” If you do, it would be great if you could join the Yarn.social Signal Group (_at least until we have Group support and better apps for Salty.im πŸ˜…)_
@abucci Do you happen to use Signal btw? πŸ€” If you do, it would be great if you could join the Yarn.social Signal Group (_at least until we have Group support and better apps for Salty.im πŸ˜…)_
@akoizumi Haha πŸ˜‚ Did you draw this? πŸ€”
@akoizumi Haha πŸ˜‚ Did you draw this? πŸ€”
@justamoment πŸ‘
@justamoment πŸ‘
@eaplmx Correct. I should probably improve the startup a bit to catch this earlier on. Maybe expose it in the UI as well in Poderator Settings πŸ€”
@eaplmx Correct. I should probably improve the startup a bit to catch this earlier on. Maybe expose it in the UI as well in Poderator Settings πŸ€”
@eaplmx Yes please πŸ™
@eaplmx Yes please πŸ™
I _think_ Email has been broken on my Pod since some time now since @lyse made this commit the default behaviour of the flags/env had changed requiring SMTP_PORT to be set (used to default toi 25) ooops πŸ˜…
I _think_ Email has been broken on my Pod since some time now since @lyse made this commit the default behaviour of the flags/env had changed requiring SMTP_PORT to be set (used to default toi 25) ooops πŸ˜…
@eaplmx Yup πŸ˜…
@eaplmx Yup πŸ˜…
@eaplmx Can you file an issue? πŸ€”
@eaplmx Can you file an issue? πŸ€”
Try now. fixed my pod's email configuration πŸ˜…
Try now. fixed my pod's email configuration πŸ˜…

twtxt_twtxt.1.cytd0qqnwbpw@dm4.mills.io    | time="2022-10-10T05:17:46Z" level=warning msg="sending emails disabled in configuration"


That would be why it's not working... Hmmm πŸ€”

twtxt_twtxt.1.cytd0qqnwbpw@dm4.mills.io    | time="2022-10-10T05:17:46Z" level=warning msg="sending emails disabled in configuration"


That would be why it's not working... Hmmm πŸ€”
@justamoment No it _should_ work immediately. Check your spam folder perhaps? Let me test it real quick to be sure my infra isn't fucked πŸ˜…
@justamoment No it _should_ work immediately. Check your spam folder perhaps? Let me test it real quick to be sure my infra isn't fucked πŸ˜…
@justamoment Talk to him about your thoughts on the MithrilJS library and "mess" you speak of πŸ˜… @markwylde happens to quite like the library, so much so he even forked it _I believe_ πŸ˜‚
@justamoment Talk to him about your thoughts on the MithrilJS library and "mess" you speak of πŸ˜… @markwylde happens to quite like the library, so much so he even forked it _I believe_ πŸ˜‚
@mckinley Ooop yeah πŸ˜… you caught me! 🀣
@mckinley Ooop yeah πŸ˜… you caught me! 🀣
@justamoment From the Loign view:
@justamoment From the Loign view:
@justamoment I used to work with him here in Oz, great UI/UX designer, best I've ever known πŸ˜…
@justamoment I used to work with him here in Oz, great UI/UX designer, best I've ever known πŸ˜…
@justamoment yarnd implements this too πŸ‘Œ Its basically called "Magic Link Auth". We've had this for a while, not sure if anyone uses it though πŸ˜…
@justamoment yarnd implements this too πŸ‘Œ Its basically called "Magic Link Auth". We've had this for a while, not sure if anyone uses it though πŸ˜…
sharkdp/hyperfine: A command-line benchmarking tool Found this really great tool whilst reading this other blog post You Don't Need a Library for File Walking in Go | Kablamo Engineering Blog πŸ‘Œ
sharkdp/hyperfine: A command-line benchmarking tool Found this really great tool whilst reading this other blog post You Don't Need a Library for File Walking in Go | Kablamo Engineering Blog πŸ‘Œ
@lyse That is just cool! πŸ‘Œ
@lyse That is just cool! πŸ‘Œ
@justamoment Oh! 😳 You should talk to @markwylde about this πŸ˜†
@justamoment Oh! 😳 You should talk to @markwylde about this πŸ˜†
Haha 🀣 I have to admit I'm not a fan of GNU 🀣
Haha 🀣 I have to admit I'm not a fan of GNU 🀣
@abucci Nah you're all good πŸ€— I literally hacked this up in a day πŸ˜‚ Thays why I needed this feedback! πŸ™‡β€β™‚οΈ Gimme time to improve things before final integration πŸ™
@abucci Nah you're all good πŸ€— I literally hacked this up in a day πŸ˜‚ Thays why I needed this feedback! πŸ™‡β€β™‚οΈ Gimme time to improve things before final integration πŸ™
The indexing and searching of Emojis? πŸ˜†
The indexing and searching of Emojis? πŸ˜†
Ahh good πŸ‘Œ
Ahh good πŸ‘Œ
Thanks! I commented and not sure I'd you got search working finally?

Ice just woken up β˜•οΈx1
Thanks! I commented and not sure I'd you got search working finally?

Ice just woken up β˜•οΈx1
@abucci There is nothing to do with websub -- It is completely transparent to the user: it makes updates across pods near real-time.
@abucci There is nothing to do with websub -- It is completely transparent to the user: it makes updates across pods near real-time.
Hmmmm
Hmmmm
Good Evening πŸ‘‹
Good Evening πŸ‘‹
@akoizumi Behind calls to conf.IsFeatureEnabled(...)
@akoizumi Behind calls to conf.IsFeatureEnabled(...)
FYI I've enabled the moving_average_feed_refresh feature on this pod (retesting it). Feed update _may_ be slower than normal. Please let me know if the experience is worse or otherwise just garbage. Note: Does not affect feed updates between Yarn pods (With websub enabled, those are near real-time).
FYI I've enabled the moving_average_feed_refresh feature on this pod (retesting it). Feed update _may_ be slower than normal. Please let me know if the experience is worse or otherwise just garbage. Note: Does not affect feed updates between Yarn pods (With websub enabled, those are near real-time).
@abucci Thank you! πŸ™ I'm _probably_ looking to fully integrate this work into the Web UI and API by next weekend hopefully 🀞
@abucci Thank you! πŸ™ I'm _probably_ looking to fully integrate this work into the Web UI and API by next weekend hopefully 🀞
@abucci Normally the process if this:

1. build a new feature, put it behind a feature gate
2. announce it and tell other pod operators about it
3. after a while promote it

That being said, if there are more than one optional feature being gated at the same time, they can be listed:


$ ./yarnd --enable-feature list
Available Features:
 - foo
 - moving_average_feed_refresh
 - jump_timeline_age
 - websub


And oops looks like we need to retest a couple of other features (I no longer run them) and see if we need to either improve them or nuke 'em πŸ˜…
@abucci Normally the process if this:

1. build a new feature, put it behind a feature gate
2. announce it and tell other pod operators about it
3. after a while promote it

That being said, if there are more than one optional feature being gated at the same time, they can be listed:


$ ./yarnd --enable-feature list
Available Features:
 - foo
 - moving_average_feed_refresh
 - jump_timeline_age
 - websub


And oops looks like we need to retest a couple of other features (I no longer run them) and see if we need to either improve them or nuke 'em πŸ˜…
@abucci If you're trying out the CLI tools index_archive and search_archive (I know @xuu is) -- I would appreciate feedback in terms of correctness of the indexed data, whether or not you couldn't find what you wanted easily, etc.

Kind of want to get the "indexing" right -- Even though I _think_ I'll design it such that you can rm -rf data/indexx and let yarnd re-index from the archive. At least this is how it works now, I see no reason to change the source-of-truth here
@abucci If you're trying out the CLI tools index_archive and search_archive (I know @xuu is) -- I would appreciate feedback in terms of correctness of the indexed data, whether or not you couldn't find what you wanted easily, etc.

Kind of want to get the "indexing" right -- Even though I _think_ I'll design it such that you can rm -rf data/indexx and let yarnd re-index from the archive. At least this is how it works now, I see no reason to change the source-of-truth here
@abucci Yes, essentially at "ingestion" time from the Cache.
@abucci Yes, essentially at "ingestion" time from the Cache.
@abucci Settings -> Poderating Settings

Add websub to "Enabled Optional Features"

@abucci Settings -> Poderating Settings

Add websub to "Enabled Optional Features"

@ullarah Hey! πŸ‘‹
Btw, who's has the websub feature enabled on their pod? Thinking about promoting this feature soon...
Btw, who's has the websub feature enabled on their pod? Thinking about promoting this feature soon...
I had no idea you _could_ even spread "misinformation" through the use of PayPal 😳
I had no idea you _could_ even spread "misinformation" through the use of PayPal 😳
@justamoment Btw... Were you still wanting to write a nice sexy MithrilJS PWA for Yarn.social we can host on app.yarn.social or yarn.social/app πŸ˜…
@justamoment Btw... Were you still wanting to write a nice sexy MithrilJS PWA for Yarn.social we can host on app.yarn.social or yarn.social/app πŸ˜…
@mckinley I _think_ I've misspoken. I can't even access that feed either, it's "connection refused". If we're talking about an API (of some kind) that lets me post some text, that's totally fine. I _assume_ at that point the feed is basically a feed that anyone can post to but the "authorship" of the feed id still just one entity (although I note this feed in particular has no metadata about it so πŸ€·β€β™‚οΈ) What gets a bit weird IMO is when you start to do things like:


<timestamp>\tPost by prologic: Hello World!


I mean sure its a hack but no client will recognize this Twt in some random feed as a post by me.
@mckinley I _think_ I've misspoken. I can't even access that feed either, it's "connection refused". If we're talking about an API (of some kind) that lets me post some text, that's totally fine. I _assume_ at that point the feed is basically a feed that anyone can post to but the "authorship" of the feed id still just one entity (although I note this feed in particular has no metadata about it so πŸ€·β€β™‚οΈ) What gets a bit weird IMO is when you start to do things like:


<timestamp>\tPost by prologic: Hello World!


I mean sure its a hack but no client will recognize this Twt in some random feed as a post by me.
@mckinley I _think_ I've misspoken. I can't even access that feed either, it's "connection refused". If we're talking about an API (of some kind) that lets me post some text, that's totally fine. I _assume_ at that point the feed is basically a feed that anyone can post to but the "authorship" of the feed id still just one entity (although I note this feed in particular has no metadata about it so πŸ€·β€β™‚οΈ) What gets a bit weird IMO is when you start to do things like:


<timestamp>\\tPost by prologic: Hello World!


I mean sure its a hack but no client will recognize this Twt in some random feed as a post by me.
Wait what?! 😳
Wait what?! 😳
@pkill9 Hello! Welcome πŸ€— There are a number of other clients listed on Yarn.social πŸ‘Œ
@pkill9 Hello! Welcome πŸ€— There are a number of other clients listed on Yarn.social πŸ‘Œ
I _still believe_ the right way to do this really is for a site owner (for example) to run up a yarnd instance (a Yarn.social pod), embed a widget on the website that uses IndieAuth to your pod, dynamically creates a new feed for the user(s) and the widgets uses microPub to post to their feed on their behalf via some Javascript.

Of course we're still missing microPub support.
I _still believe_ the right way to do this really is for a site owner (for example) to run up a yarnd instance (a Yarn.social pod), embed a widget on the website that uses IndieAuth to your pod, dynamically creates a new feed for the user(s) and the widgets uses microPub to post to their feed on their behalf via some Javascript.

Of course we're still missing microPub support.
@justamoment The _troulbe_ with a website and trying to support some kind of "comment system" or "guestbook" type thing is that Twtxt was designed to be a text format with a 1:N mapping of author to twt(s). In essence a single feed is owned by one author that can contain zero or more twts. It is not really possible (_although @darch is trying and finding various ways to break the spec πŸ˜…_) to have a "centralised" feed that lets N users add to it.

To really support this kind of thing, you'd really have to "dynamically" create a new feed for every user, uniquely identify them in some way so you can do this (e.g: with OAuth, IndieAuth, etc), then have an API or Form that they can enter content to and it write to "their" feed._
@justamoment The _troulbe_ with a website and trying to support some kind of "comment system" or "guestbook" type thing is that Twtxt was designed to be a text format with a 1:N mapping of author to twt(s). In essence a single feed is owned by one author that can contain zero or more twts. It is not really possible (_although @darch is trying and finding various ways to break the spec πŸ˜…_) to have a "centralised" feed that lets N users add to it.

To really support this kind of thing, you'd really have to "dynamically" create a new feed for every user, uniquely identify them in some way so you can do this (e.g: with OAuth, IndieAuth, etc), then have an API or Form that they can enter content to and it write to "their" feed._