# 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 20
# self = https://watcher.sour.is/conv/ceripcq
Finally I propose that we increase the Twt Hash length from 7 to 12 and use the first 12 characters of the base32 encoded blake2b hash. This will solve two problems, the fact that all hashes today either end in q or a (_oops_) 😅 And increasing the Twt Hash size will ensure that we never run into the chance of collision for ions to come. Chances of a 50% collision with 64 bits / 12 characters is roughly ~12.44B Twts. That _ought_ to be enough! -- I also propose that we modify all our clients and make this change from the 1st July 2025, which will be Yarn.social's 5th birthday and 5 years since I started this whole project and endeavour! 😱 #Twtxt #Update~
We have 4 clients but this should be 6 I _believe_ with tt2 from @lyse and Twtxtory from @javivf?
I will be adding the code in for yarnd very soonâ„¢ for this change, with a if the date is >= 2025-07-01 then compute_new_hashes else compute_old_hashes
@bender Thank you! I am writting on PR page.
July 1st. 63 days from now to implement a backward-incompatible change, apparently not open to other ideas like replacing blake with SHA, or discussing implementation challenges for other languages and platforms.
Finally just closing #18, #19 and #20 without starting a proper discussion and ignoring a 'micro consensus' feels... not right.
I don't know what to think rather than letting it rest (May will be busy here) and focus on other stuff in the future.
twt-hash-v2.md#implementation-timeline
@prologic I'm very sorry but my feelings are similar to @eapl.me . For a long time I thought that Yarn was part of the Twtxt ecosystem, and not that Twtxt is an extension of Yarn. I don't feel comfortable with what has happened. I didn't expect this change of direction.
The nice part of Twtxt is that it is read by humans, with a simpler format. It's the heart of the social network.
I need to think for a little time, but I'm thinking of stopping my involvement in the community.
I'm with @andros and @eapl.me on this one. But I have also lost interest in twtxt lately and currently rethinking what digital tools truly add value to my life. So I will not spending my time on adding more complexity to Timeline. Still a big thanks to you @prologic for all the great work you have done and all the nice conversations both here and on our video calls.
I'm with @andros and @eapl.me on this one. But I have also lost interest in twtxt lately and currently rethinking what digital tools truly add value to my life. So I will not spending my time on adding more complexity to Timeline. Still a big thanks to you @prologic for all the great work you have done and all the nice conversations both here and on our video calls.
I'm with @andros and @eapl.me on this one. But I have also lost interest in twtxt lately and currently rethinking what digital tools truly add value to my life. So I will not spending my time on adding more complexity to Timeline. Still a big thanks to you @prologic for all the great work you have done and all the nice conversations both here and on our video calls.
I'm with @andros and @eapl.me on this one. But I have also lost interest in twtxt lately and currently rethinking what digital tools truly add value to my life. So I will not spending my time on adding more complexity to Timeline. Still a big thanks to you @prologic for all the great work you have done and all the nice conversations both here and on our video calls.
just for the record I didn't say I was leaving the twtxt 'community' (did I?) but than I have other priorities to focus on in the following months. Please don't be condescending, is not cool.
Development of Timeline (PHP client) has been stale for some reasons, a few of them in my side, so I think it won't be updated to the new thread model, at least pretty soon.
So is not that I'll stop using twtxt, just the client I use won't be compatible with the new model in July.
that said, and reading to @sorenpeter and @andros I have new thoughts. I assume that this won't change anyone's opinions or priorities, so it makes no harm sharing them.
It's always tempting to use something that already exists (like X, Masto, Bsky, etc.) rather that building anything through effort and disagreement until reaching to something useful and valuable together. A 'social service' is only useful if people is using it.
I'll add that I haven't lost interest on the 'hacky' part of twtxt about developing tools, protocols, and extensions as a community. It's the appealing part! It's a nice hobby to have, shared with random people across the world.
But this is not the right way for me, and makes me feel that I'm unwelcome to propose something different (after watching replies to my previous twt). Feels like "If you don't agree, you are free to leave, we'll miss you." Naah, not cool. I've lived that many times before, and nowadays I don't have enough spare time and energy for a hobby like that.
Let's see what happens next with the micro-community!