# 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=37991
# next = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=38091
# prev = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=37891
@laz Helllo!!! π Welcome back! π€ -- For reference:
make image
Scammers are getting rather creative π
Scammers are getting rather creative π
So for the rest of the world shall we have another Yarn.social Wwekly call at 1200 UTC (4hrs from now) ? π€
So for the rest of the world shall we have another Yarn.social Wwekly call at 1200 UTC (4hrs from now) ? π€
@mckinley Haha π Thanks again for the summary π€
@mckinley Haha π Thanks again for the summary π€
@hashrock I have an ask of you then... Either:
a) You file appropriate Issues
or
b) You write something that _wants_ to use something like this, and work with me to "just build" it π
@hashrock I have an ask of you then... Either:
a) You file appropriate Issues
or
b) You write something that _wants_ to use something like this, and work with me to "just build" it π
@ocdtrekkie We talked about this Twitterβ’ thread (screenshot) in our Yarn.social Weekly call today/tonight -- This is just funny as hell π
π€£ Elon Musk and Twitter, what a disaster π€£
@ocdtrekkie We talked about this Twitterβ’ thread (screenshot) in our Yarn.social Weekly call today/tonight -- This is just funny as hell π
π€£ Elon Musk and Twitter, what a disaster π€£
@hashrock Pretty much... But I also think we can produce and give nice JSON responses for feeds / profiles and even searches π
@hashrock Pretty much... But I also think we can produce and give nice JSON responses for feeds / profiles and even searches π
@marado Let me do some testing to be sure... π
@marado Let me do some testing to be sure... π
@eaplmx I _think_ its a good idea. Let's build something minimal -- A PoC if you will. My first requirement is that its only "Login/Auth" is IndieAuth -- As every Yarn.social Pod is a valid IndieAuth provider.
@eaplmx I _think_ its a good idea. Let's build something minimal -- A PoC if you will. My first requirement is that its only "Login/Auth" is IndieAuth -- As every Yarn.social Pod is a valid IndieAuth provider.
@marado is that a good thing or bad? π
@marado is that a good thing or bad? π
@eaplmx Oh you mean, let's just build it? π
@eaplmx Oh you mean, let's just build it? π
Twitter-implosion This is a nice write-up of the very problematic "Advertising Business" model(s) of _many_ modern tech companies. The "noise" to "signal" ratio is _spot on_ π
Twitter-implosion This is a nice write-up of the very problematic "Advertising Business" model(s) of _many_ modern tech companies. The "noise" to "signal" ratio is _spot on_ π
@deepend Hello! π Welcome to Yarn.social / Twtxt π₯³
@deepend Hello! π Welcome to Yarn.social / Twtxt π₯³
@deepend Hello! π Welcome to Yarn.social / Twtxt π₯³
@deepend Hello! π Welcome to Yarn.social / Twtxt π₯³
@deepend Hello! π Welcome to Yarn.social / Twtxt π₯³
@deepend Hello! π Welcome to Yarn.social / Twtxt π₯³
Here (on Yarn / Twtxt) you get to know who people are by interacting with them and getting to know one another π
Even when we have our Yarn.social Weekly calls I call y'all by your feed names π
Here (on Yarn / Twtxt) you get to know who people are by interacting with them and getting to know one another π
Even when we have our Yarn.social Weekly calls I call y'all by your feed names π
@eaplmx I know you and I have a lot of "things" going on, but we _should_ try to build this. I know @darch has wanted something like this as well... I _really_ want to see more things integrated into the Yarn.social ecosystem, because yeah we really do take privacy quite seriously and as you probably aware away, go out of our way to ensure there is no "Personal Information" (PII) stored, collected or otherwise.
@eaplmx I know you and I have a lot of "things" going on, but we _should_ try to build this. I know @darch has wanted something like this as well... I _really_ want to see more things integrated into the Yarn.social ecosystem, because yeah we really do take privacy quite seriously and as you probably aware away, go out of our way to ensure there is no "Personal Information" (PII) stored, collected or otherwise.
And by "Yarn native" I mean, get updates as a feed itself π
And by "Yarn native" I mean, get updates as a feed itself π
@eaplmx Also I'm thinking... Can we build something similar to this, or fork something that's close and add IndieAuth support so we can sign-in with our respective Yarn.social pod accounts? π€ This _would be ideal_ as it means we preserve who we are without giving away any _actual_ personal information (PPII) -- I notice this tool wants your Name / Email Address (okay the name you can make up or use an alias) but the Email is a bit well questionable (sure you can get updates, but it would be nicer if it was Yarn native I guess?)
@eaplmx Also I'm thinking... Can we build something similar to this, or fork something that's close and add IndieAuth support so we can sign-in with our respective Yarn.social pod accounts? π€ This _would be ideal_ as it means we preserve who we are without giving away any _actual_ personal information (PPII) -- I notice this tool wants your Name / Email Address (okay the name you can make up or use an alias) but the Email is a bit well questionable (sure you can get updates, but it would be nicer if it was Yarn native I guess?)
@eaplmx I did it π As you're the organiser, please let me know how many other responses you get. I tried to have two fairly wide options for me so hopefully that means we can have two sessions and we can have as many folks from the community join π
@eaplmx I did it π As you're the organiser, please let me know how many other responses you get. I tried to have two fairly wide options for me so hopefully that means we can have two sessions and we can have as many folks from the community join π
@eaplmx Hmmm can someone find a online tool where we can anonymously or so pick a time-slot that works best for each, but on a single 24hr period of time. That is to say, I don't mind holding two sessions, and I don't mind staying up late just to do so one day a week, but I need two UTC time-slots on my Saturday (the only day I can really do this, because I also have a day job and need to sleep on Sundays π
)
@eaplmx Hmmm can someone find a online tool where we can anonymously or so pick a time-slot that works best for each, but on a single 24hr period of time. That is to say, I don't mind holding two sessions, and I don't mind staying up late just to do so one day a week, but I need two UTC time-slots on my Saturday (the only day I can really do this, because I also have a day job and need to sleep on Sundays π
)
Hey @axodys question for you, is @zags a feed/persona of yours on your pod, and is it basically automated, i.e: a bot? π€
Hey @axodys question for you, is @zags a feed/persona of yours on your pod, and is it basically automated, i.e: a bot? π€
@marado Hmmm good question. I'm not sure, but I _feel_ like you should not be able to do this? I'm a bit worried even more things _may_ go wrong? π€ Thoughts?
@marado Hmmm good question. I'm not sure, but I _feel_ like you should not be able to do this? I'm a bit worried even more things _may_ go wrong? π€ Thoughts?
I _think_ I know how to solve this. I just have two sessions per week (my Saturday). One at around 0400-0500 UTC and another one a few hours later.
I _think_ I know how to solve this. I just have two sessions per week (my Saturday). One at around 0400-0500 UTC and another one a few hours later.
@markwylde Sounds about right. I _think_ there are some toggles to make it go a bit faster (but less data durability) and I'm sure we can improve this too π
@markwylde Sounds about right. I _think_ there are some toggles to make it go a bit faster (but less data durability) and I'm sure we can improve this too π
@markwylde Yeah we have to be clear on what you behaviour you actually want here... So for example Read Solomon Erasure Encoding basically describe what you're describing here whereby you can recover data from N/M nodes. I _feel_ like this is something we could built that sits in front of a Bitraft cluster (or single node)? π€
@markwylde Yeah we have to be clear on what you behaviour you actually want here... So for example Read Solomon Erasure Encoding basically describe what you're describing here whereby you can recover data from N/M nodes. I _feel_ like this is something we could built that sits in front of a Bitraft cluster (or single node)? π€
@mckinley No problems π Timezones are hard π€£
@mckinley No problems π Timezones are hard π€£
@mckinley is right. There are three different things going on here.
- The Cache limits what it hold "in-memory" by Size per Feed
- The Cache limits what it holds "in-memory" by TTL
- Old Twts are Archived to disk.
At _some_ point soonβ’ we will have integrated search on all Yarn.social pods (running yarnd) that will give us the capability of two things:
- Full Text / Keyword / Tag search (searching the archive)
- Pulling up older Twts for a Conversation view (from the archive)
@mckinley is right. There are three different things going on here.
- The Cache limits what it hold "in-memory" by Size per Feed
- The Cache limits what it holds "in-memory" by TTL
- Old Twts are Archived to disk.
At _some_ point soonβ’ we will have integrated search on all Yarn.social pods (running yarnd) that will give us the capability of two things:
- Full Text / Keyword / Tag search (searching the archive)
- Pulling up older Twts for a Conversation view (from the archive)
Actually @darch has gone to bed π
So usual time of 0500 UTC? π€
Actually @darch has gone to bed π
So usual time of 0500 UTC? π€
Shall we do the Yarn/social weekly call now since it appears most people are awake and available?
Shall we do the Yarn/social weekly call now since it appears most people are awake and available?
@markwylde If you could benchmark this that would be wonderful! π -- Also reading your thought son "Sharding", I _think_ you might be slightly confused, because what you just described is essentially "High Availability", and not Sharding.
In fact Bitraft already has this anyway. It fully supports forming a High Availability Cluster.
@markwylde If you could benchmark this that would be wonderful! π -- Also reading your thought son "Sharding", I _think_ you might be slightly confused, because what you just described is essentially "High Availability", and not Sharding.
In fact Bitraft already has this anyway. It fully supports forming a High Availability Cluster.
Does this make sense? π€ In fact I _probably_ wouldn't have any Metadata on your Github feed side at all, just delete it and re-sync (after fixing the dupes), and then help me add some additional features to add additional KV pairs to your feed's Metadata in yarnd (the backend for Yarn.social) π
Does this make sense? π€ In fact I _probably_ wouldn't have any Metadata on your Github feed side at all, just delete it and re-sync (after fixing the dupes), and then help me add some additional features to add additional KV pairs to your feed's Metadata in yarnd (the backend for Yarn.social) π
@rsdoiel Where is your Github feed you're mirroring? π€ The only reason for "dupes" is the way hashes are calculated. They are based on what's called a "Hashing URI", essentially the first # url = field in your feed's metadata. I _think_ (but would have to confirm) that if you're trying to sync your Github hosted twtxt.txt feed to your twtxt.net feed (on my pod), if you have a # url = field in your Github side that isn't the same value as your feed on your twtxt.net feed, then you'll end up with dupes. You _can_ have multiple # url = fields, but the first one is used as the "Hashing URI" and if you're syncing, it must be the same on both sides.
@rsdoiel Where is your Github feed you're mirroring? π€ The only reason for "dupes" is the way hashes are calculated. They are based on what's called a "Hashing URI", essentially the first # url = field in your feed's metadata. I _think_ (but would have to confirm) that if you're trying to sync your Github hosted twtxt.txt feed to your twtxt.net feed (on my pod), if you have a # url = field in your Github side that isn't the same value as your feed on your twtxt.net feed, then you'll end up with dupes. You _can_ have multiple # url = fields, but the first one is used as the "Hashing URI" and if you're syncing, it must be the same on both sides.
@rsdoiel Hmmm I think you might have run into a bug π€£ I might need your help figuring this out π
@rsdoiel Hmmm I think you might have run into a bug π€£ I might need your help figuring this out π
@rsdoiel Hmmm you shouldn't be getting duplicates. Can you share how you're doing this? I use the tool myself to backup my feeds π
@rsdoiel Hmmm you shouldn't be getting duplicates. Can you share how you're doing this? I use the tool myself to backup my feeds π
@markwylde No but I could do some testing and publish the results π
As for the sharding though... Let's discuss this?
@markwylde No but I could do some testing and publish the results π
As for the sharding though... Let's discuss this?
@lyse Your cover pic seriously looks like a nice oil painting π
@lyse Your cover pic seriously looks like a nice oil painting π
@lyse No it's not right but as I said on IRC I haven't figured out a way to handle bad Following yet π€£
@lyse No it's not right but as I said on IRC I haven't figured out a way to handle bad Following yet π€£
@jlj I think I've managed to fix bugs there recently π€
@jlj I think I've managed to fix bugs there recently π€
@off_grid_living It's being moved to a filter. It's a current feature being developed and enables on my pod only π€
@off_grid_living It's being moved to a filter. It's a current feature being developed and enables on my pod only π€
@off_grid_living This is the poem:
Title: in the ocean waves
in the ocean waves I can see a dolphin swimming next to me.
and if listen I can here fish swimming in the currents near.
I can taste the salty air and fish jumping there.
there's so much to see here and taste in this ocaen wave's community.
@off_grid_living This is the poem:
Title: in the ocean waves
in the ocean waves I can see a dolphin swimming next to me.
and if listen I can here fish swimming in the currents near.
I can taste the salty air and fish jumping there.
there's so much to see here and taste in this ocaen wave's community.
@jlj It's known to work for dozens of users actually π What's the error? π€