# 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=37591
# next = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=37691
# prev = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=37491
@marado This approach is fine, as long as you're aware that there is no way to _actually_ attribute the authorship of the line in the feed that is essentially being used to let (potentially) anonymous visitors to your site/blog add comments.

I've given this a lot of thought over the months and I _think_ the best way to solve for this in general over time is to a) Build support for micro.Pub into yarnd b) Add support for IndieAuth (as a consumer) and then build out an ecosystem of Javascript and whatever libraries and tools to support this use-case.

This way when someone makes a comment on a blog post or website, they are in fact logging into their feed on some pod (that you choose to use) and they are able to take that with them, or continue using it, etc.

Just my $0.20 worth πŸ˜…
@marado This approach is fine, as long as you're aware that there is no way to _actually_ attribute the authorship of the line in the feed that is essentially being used to let (potentially) anonymous visitors to your site/blog add comments.

I've given this a lot of thought over the months and I _think_ the best way to solve for this in general over time is to a) Build support for micro.Pub into yarnd b) Add support for IndieAuth (as a consumer) and then build out an ecosystem of Javascript and whatever libraries and tools to support this use-case.

This way when someone makes a comment on a blog post or website, they are in fact logging into their feed on some pod (that you choose to use) and they are able to take that with them, or continue using it, etc.

Just my $0.20 worth πŸ˜…
We've had about ~20 or so new folks join Yarn.social / Twtxt in over the past ~2 weeks or so πŸ₯³ Its not as many as Mastodon's ~70k new folks, but its still _non-zero_ 🀣 ~
We've had about ~20 or so new folks join Yarn.social / Twtxt in over the past ~2 weeks or so πŸ₯³ Its not as many as Mastodon's ~70k new folks, but its still _non-zero_ 🀣 ~
@maya "The Cloud" is still someone else's computer or bunch of computers. The important point here is data locality, data security and authenticity.
@maya "The Cloud" is still someone else's computer or bunch of computers. The important point here is data locality, data security and authenticity.
@marado So I did πŸ˜… So the simplest way to do this is to just either use yarnc post or the API or even just write a line to your feed that announces your blog post. Use that as the Yarn/thread to place comments again πŸ˜…

The "scope" will blow out when you want to do things like:

- Allow arbitrary internet users to comment, so you'd have to do something around identity and maybe creating ephemeral feds for them.
- Searching for previous comments and displaying them.

Although the 2nd point is probably not so bad, just have to get integrated search into pods now that search.twtxt.net is _mostly_ done πŸ‘Œ (still needs an API I reckon? πŸ€”)
@marado So I did πŸ˜… So the simplest way to do this is to just either use yarnc post or the API or even just write a line to your feed that announces your blog post. Use that as the Yarn/thread to place comments again πŸ˜…

The "scope" will blow out when you want to do things like:

- Allow arbitrary internet users to comment, so you'd have to do something around identity and maybe creating ephemeral feds for them.
- Searching for previous comments and displaying them.

Although the 2nd point is probably not so bad, just have to get integrated search into pods now that search.twtxt.net is _mostly_ done πŸ‘Œ (still needs an API I reckon? πŸ€”)
@marado Oh interestinf! 😳 Did I ever comment on this idea? (I'll search later) πŸ˜†
@marado Oh interestinf! 😳 Did I ever comment on this idea? (I'll search later) πŸ˜†
@montsamu Hello! πŸ‘‹ Welcome to Yarn.social πŸ€—
@montsamu Hello! πŸ‘‹ Welcome to Yarn.social πŸ€—
Yarn/Twtxt is in fact fully decentralized πŸ˜†
Yarn/Twtxt is in fact fully decentralized πŸ˜†
@mckinley Also well said πŸ‘Œ
@mckinley Also well said πŸ‘Œ
@movq Oh! It never occurred to me it was a physical calendar πŸ€¦β€β™‚οΈ
@movq Oh! It never occurred to me it was a physical calendar πŸ€¦β€β™‚οΈ
it might even be possible to make the filters additive with a slight nod plus a little JS πŸ€”
it might even be possible to make the filters additive with a slight nod plus a little JS πŸ€”
@eaplmx Ahh damn browser inconsistencies πŸ˜… And yes and yes πŸ‘Œ
@eaplmx Ahh damn browser inconsistencies πŸ˜… And yes and yes πŸ‘Œ
Yes a PWA is a possible client we could build for Yarn.social pods πŸ‘Œ cc @markwylde πŸ€—
Yes a PWA is a possible client we could build for Yarn.social pods πŸ‘Œ cc @markwylde πŸ€—
But of course the mobile web is not so great 🀣



I hate CSS πŸ€¦β€β™‚οΈ
But of course the mobile web is not so great 🀣



I hate CSS πŸ€¦β€β™‚οΈ
So far so good πŸ˜†πŸ˜…
So far so good πŸ˜†πŸ˜…
@lyse I guess I'm missing something important here... Like if you have 365 photos/images as input, I'm not exactly sure what the output is? A set of web pages? Normally when I think of a calendar I think of a diary that helps remind me of what's coming up that's important to remember...
@lyse I guess I'm missing something important here... Like if you have 365 photos/images as input, I'm not exactly sure what the output is? A set of web pages? Normally when I think of a calendar I think of a diary that helps remind me of what's coming up that's important to remember...
There we go. Enabled πŸ‘Œ Of course as we build this out, we'll have to adapt the Mobile App and API too at some point πŸ˜…
There we go. Enabled πŸ‘Œ Of course as we build this out, we'll have to adapt the Mobile App and API too at some point πŸ˜…
@eaplmx I haven't enabled the feature yet (feature flag) was waiting a few hours to be sure I broke nothing πŸ˜…
@eaplmx I haven't enabled the feature yet (feature flag) was waiting a few hours to be sure I broke nothing πŸ˜…
@darch No it works it just wasn't very good at explaining what it was πŸ˜†
@darch No it works it just wasn't very good at explaining what it was πŸ˜†
@thgie Sure πŸ€— I'll let you explore the ecosystem we've helped create and we'll talk more πŸ™
@thgie Sure πŸ€— I'll let you explore the ecosystem we've helped create and we'll talk more πŸ™
@darch Is it a Deaktop software, Self-Hosted App or SaaS? πŸ€” I can't tell 🀣
@darch Is it a Deaktop software, Self-Hosted App or SaaS? πŸ€” I can't tell 🀣
@darch Sure no worries and I will πŸ‘Œ
@darch Sure no worries and I will πŸ‘Œ
@darch This is not search though πŸ€”
@darch This is not search though πŸ€”
Hey @darch can you fix the colors here? πŸ™ The contrast is rally bad on mobile Safari 😒
Hey @darch can you fix the colors here? πŸ™ The contrast is rally bad on mobile Safari 😒
What is Yellow ? πŸ€”
What is Yellow ? πŸ€”
@thgie Hello! πŸ‘‹ Welcome πŸ€—
@thgie Hello! πŸ‘‹ Welcome πŸ€—
@hashrock What if it were integrated into the yarnd UI as it is now or similar? πŸ€” What would that look like? πŸ€” What would we need to build? πŸ€”
@hashrock What if it were integrated into the yarnd UI as it is now or similar? πŸ€” What would that look like? πŸ€” What would we need to build? πŸ€”
@hashrock Yeah I think @darch has tried to create something like this πŸ‘Œ
@hashrock Yeah I think @darch has tried to create something like this πŸ‘Œ
@hashrock How would it work? (Given what I said above)
@hashrock How would it work? (Given what I said above)
@hashrock You _could_ probably achieve this now by going to Feeds and create a new persona/feed for yourself that you do nothing but post your artwork to? πŸ€”
@hashrock You _could_ probably achieve this now by going to Feeds and create a new persona/feed for yourself that you do nothing but post your artwork to? πŸ€”
The code for this is now rolled out to my pod but not enabled yet, going to wait a few hours (_per the sticky message at the top_) just in case I fucked something up πŸ˜… If all good I'll merge and enable the feature 🀞 -- Still work to do though on the lists part.
The code for this is now rolled out to my pod but not enabled yet, going to wait a few hours (_per the sticky message at the top_) just in case I fucked something up πŸ˜… If all good I'll merge and enable the feature 🀞 -- Still work to do though on the lists part.
@hashrock Yeah the whole "Web3" thing is just utter bullshit 🀣
@hashrock Yeah the whole "Web3" thing is just utter bullshit 🀣
Hey all πŸ‘‹ I've just update my pod at twtxt.net to a "dev" branch to test PR #1059, please let me know if you experience any issues or regressions, bugs, etc πŸ™ If everything is good after a few hours I will merge this PR and keep working. This is the new "Filter and Lists" feature... Thanks! πŸ™‡β€β™‚οΈ
Hey all πŸ‘‹ I've just update my pod at twtxt.net to a "dev" branch to test PR #1059, please let me know if you experience any issues or regressions, bugs, etc πŸ™ If everything is good after a few hours I will merge this PR and keep working. This is the new "Filter and Lists" feature... Thanks! πŸ™‡β€β™‚οΈ
@hashrock Oh 🀣 I mean I'm open to _many ideas_ that make Yarn.social different πŸ˜… For example we've talked about some kind of "events" thing before, it has a number of blockers though, so we're not quite there yet... One of the guiding principles of course is that we remain decentralised with a self-hosted focus. That means anything we build should be fully decentralised, capable of running on your own pod/instance and generally useful to the wider ecosystem in some way.
@hashrock Oh 🀣 I mean I'm open to _many ideas_ that make Yarn.social different πŸ˜… For example we've talked about some kind of "events" thing before, it has a number of blockers though, so we're not quite there yet... One of the guiding principles of course is that we remain decentralised with a self-hosted focus. That means anything we build should be fully decentralised, capable of running on your own pod/instance and generally useful to the wider ecosystem in some way.
@eaplmx Do you think this is the right direction roughly speaking? (aside from the UX which I suck at πŸ˜…)
@eaplmx Do you think this is the right direction roughly speaking? (aside from the UX which I suck at πŸ˜…)
@akoizumi Of course πŸ‘Œ
@akoizumi Of course πŸ‘Œ
@hashrock Is that something Twitterβ„’ has?! 😳
@hashrock Is that something Twitterβ„’ has?! 😳
How about this @eaplmx ? πŸ€” Getting better? 🀞
How about this @eaplmx ? πŸ€” Getting better? 🀞
@eaplmx Oh! You gamify your fitness level? 😳
@eaplmx Oh! You gamify your fitness level? 😳
@eaplmx Yup makes sense to call out the pod name there πŸ‘Œ

Trying to find the right model that will work nicely without too much rework πŸ˜† and trying to uliise existing cache functionality: grouping, filtering, sorting, views and user views.
@eaplmx Yup makes sense to call out the pod name there πŸ‘Œ

Trying to find the right model that will work nicely without too much rework πŸ˜† and trying to uliise existing cache functionality: grouping, filtering, sorting, views and user views.
What do we think of this approach of filtering your timeline? πŸ€”
What do we think of this approach of filtering your timeline? πŸ€”
@eaplmx Ahh thought so πŸ˜† That's why I have unread Gitea notifications πŸ˜… Ooops sorry πŸ€¦β€β™‚οΈ
@eaplmx Ahh thought so πŸ˜† That's why I have unread Gitea notifications πŸ˜… Ooops sorry πŸ€¦β€β™‚οΈ
@eaplmx The rebranding PR πŸ€” Unless you've done it already and I'm just behind πŸ˜†
@eaplmx The rebranding PR πŸ€” Unless you've done it already and I'm just behind πŸ˜†
@akoizumi I see πŸ˜… Why are you experimenting with IRC Seever (IRCD) and IRC Services software ? πŸ€”
@akoizumi I see πŸ˜… Why are you experimenting with IRC Seever (IRCD) and IRC Services software ? πŸ€”
Interesting discussion on electoral voting systems πŸ‘Œ
Interesting discussion on electoral voting systems πŸ‘Œ
@eaplmx You still have a PR to amend πŸ˜†
@eaplmx You still have a PR to amend πŸ˜†
Playing around with an implementations of Liats and Filters πŸ‘Œ
Playing around with an implementations of Liats and Filters πŸ‘Œ
@hashrock You can Twt (as we call it) or Yarn (as we sometimes call it) in whatever language you like πŸ˜…
@hashrock You can Twt (as we call it) or Yarn (as we sometimes call it) in whatever language you like πŸ˜…
cc @justamoment
cc @justamoment
@lyse A service to do what now? What's a day calendar anyway?
@lyse A service to do what now? What's a day calendar anyway?
@lyse Hahahaha 🀣 That's awesome, I didn't know Indian songs could sound so great πŸ˜…
@lyse Hahahaha 🀣 That's awesome, I didn't know Indian songs could sound so great πŸ˜