# 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 4637
# self = https://watcher.sour.is?uri=https://twtxt.net/user/https://twtxt.net/user/prologic/twtxt.txt/twtxt.txt&offset=3037
# next = https://watcher.sour.is?uri=https://twtxt.net/user/https://twtxt.net/user/prologic/twtxt.txt/twtxt.txt&offset=3137
# prev = https://watcher.sour.is?uri=https://twtxt.net/user/https://twtxt.net/user/prologic/twtxt.txt/twtxt.txt&offset=2937
@xuu if we want to focus on trying to standardize some kind of Twtxt “identity” \nthen that’s a different conversation, my only personal take on this is to use EDCH25519
or in other words it’s only a content post addressing not an identity of the user
also it’s worth noting but the hush of previously created content doesn’t actually change so if you change your feed URL it only affects you post going forward
@xuu Hmmm The problem with using the domain is there’s no standardization around where you can host your feed
I wonder if we can add a read it later feature or bookmark feature to Twtxt? 🤔
📣 FYI existing conversations are broken in that the links to them no longer work since we merged a breaking change to how Twts are hashed and addressed.
@xuu We _could_ do that. PR?
@xuu I _would_ absolutely love you to contribute! Please do! ❤️ If types.Twt is close enough, let's make it an Interface :) Why not! What kind of interface are you thinking about anyway?
@xuu @lyxal There are in fact _some_ users that host their twtxt.txt files in Gopherspace over gopher://... I _coudl_ add support for this in jointwt/twtxt by using [go-gopher](https://github.com/prologic/go-gopher (_one of the first things I wrote in Go!_) -- If there was enough interest... But it would only be _limited support_ (fetch, and host, not much else...)
@xuu Do you keep your pop up-to-date with jointwt/twtxt as we push commits to master? 🤔
@iolfree I like it, very jumpy and catchy 😀
@deadguy Yeah that's "fair enough". I _think_ you've seen my say this in other Twt(s), I _fully_ intend to provide more features to the API and command-line client twt so what you probably _thought_ was possible will* become possible. I'd like it myself anyway (_just becuase_), on the upside, hopefully when we get around to it it'll mean you get the best of both worlds, self-hsoted twtxt.txt file, synced to your "Pod" account, with API and Mobile App access 👌*
@deadguy I know! That's why I felt compelled to write a version of ed in Go with some modern takes on _some_ aspects of it (_mostly edit history and syntax highlighting_) 😎
@deadguy Agree with @lyxal in regards to having an account but being on "hiatus" or just keeping it as a "claim" / "identity"?
@adi Yup Gotcha. Although there are server-side variants of this too that basically tell a Browser, "here's your updated DOM or subset of it, go patch yourself".
@adi do you mean one that doesn’t refresh or one that’s a single page?
@adi What _really is a "web app" anyway? I mean without fancy client-side code like Javascript (_gough gough_) isn't it just a web server serving up a bunch of resources (_pages_)?_
This is something I want to do anyway for Bitcask so that it can scale almost indefinitely unless your entire keyspace is hot and active all the time! 🤣
Yeap all good points. LIke I said, it doesn't _really_ hurt, it just consumes key space... But that's something I _could_ solve in Bitcask itself as a "technical" level where I evict inactive keys out of the in-memory keyspace and archive them to disk instead only keeping "active" keys in memory for fast lookups.
You _have_ to identify yourself as an owner of a feed somehow though? I mean sure I get what you're saying, each Pod _has_ accounts. The decentralised parts are the Feeds and Conversations, not so much the "Users". You have to belong to a Pod somewhere, or run your own. At _some_ point I'd like to be able to carry your "identity" around through a network of pods which I _think_ is there things like IndieAuth can help (_PR not merged yet..._).
@prologic It snot a problem now per se, but they do consume key space in memory as the database used for storing things like accounts and who owns what feed and sessions stores its key space in memory.
How so? I mean people that have swung by to "test" and "check" things out, never to be seen again. There are hundreds of accounts on this pod that have never posted a thing. If course OTOH I don't actually know if they ever login and are just idle lurkers/readers...
We _should_ probably start thinking about cleaning up old inactive accounts... 🤔
Yeah :D I _might_ seriously consider using it a bit more again, I _did_ quite like it really.
You know ed right? 🤣 I _mean_ that I do quite literally use a non-visual line-based editor 😂 I _even_ used it to write a few commits for the implementation (_See [Why](https://github.com/prologic/ed#)..._) -- Because of my vision impairment where I only get to see a few measily lines of code anyway, it kind of makes sense that it can work for me 😌
@xuu Nice! What’ll it be used for? 🤔
@lyxal @xuu Yeah you mean any non-TLS Feed URI(s)?
... That _might_ change with some upcoming changes to the API and the twt command-line client where I will probably add things like twt sync that can sync between a local twtxt.txt file and your Twt.social account on the pod where your account lives.
@lyxal Yeah they are using their own "client" -- Or client here is a rather loose term, since Twtxt itself is just _really_ a twtxt.txt file hosted somewhere. What you you use here is a multi-user backend with API and a nice Mobile App (Goryon) to go along with. But under the hood it still manages a set of twtxt.txt files in /data/feeds/<username>. But no, you're right it would not be possible for any user to artificially go and post something in the future here, that would be silly, since you don't have _direct_ access to the file per se. Although...
An editor I _sometimes_ use although sometimes that is more often than you might think... Is called ed -- One day I _might_ just stop using Vim in favor of ed 😉
it’s a really good way of pinning a Twt at the top of the timeline bar isn’t it? 🤣
Ahh here 7 days ago from you 🙃 Very pretty 🌆
@123 where have I seen this image before? 🤔
Hahaha 🤣 I _know_ you're just being funny here, but I _believe_ they are literally just writing a timestamp/date that is in the future to their feed twtxt.txt file 😂
But they don't follow me, so we'll never know for sure 😂\n\n 
I dunno 🤷♂️ But this guy/gal is 🤣 I had to double-check time zones and his/her feed file/uri to be sure, but I'm 99.9% sure they are writing to their twtxt.txt feed file with a timestamp in the future 🤣
@mckinley Why do you Twt with timestamps in the future? 🤣
@adi That’s actually really cool! I didn’t know you could do animations with SVG 😳 I wonder if there’s a similar tool written in Go 😁
@antonio Hmmm haven’t heard of Wallabag ... Link?
@emm Hello! 👋 Welcome to Twtxt! 🤗
@lyxal Ahh no wonder you have the energy for "coding for fun" 😀 (_I only do in spurts!_)
@lyxal what do you do for a job again? I’m so spent after a day of work that I can’t be bothered coding let alone doing a puzzle 🤣
@lyxal @xuu I'd recommend you "unfollow" that erroneous user/feed 🤣 (_its just me, but not the me you want!_)
@prologic @lyxal @xuu I _can't_ even snipe that out of the cache without destroying the cache and letting the pod rebuild it 😂
@prologic @lyxal @xuu Oh no wait... It's an external user https://twtxt.net/external?nick=admin&uri=http%3A%2F%2F10.0.0.109%3A8000%2Fuser%2Fadmin%2Ftwtxt.txt and its from my iMac doing local dev testing, but I got things mixed with production by mistake :/
@xuu @lyxal Not unless you count me being the hacker! I _think_ I accidently did some debugging on twtxt.net by mistake 😢 Sorry about that! I nuked that account/feed!
@lyxal Hah! 😀 Yeah I _find_ it funny/interesting reading some of the /. comments, not _really_ sure how much of what folks are saying is _actually_ true, but 🤷♂️
@slashdot it amazes me that people tolerate ads in their timeline at all 😳
@chelseyc90 @ionores that’s because I was drinking lemon lime n bitters and I was done for the night 😂
@lyxal Damn 🙃 Would have been cool 😎
@lyxal Oh! did you take a pic? 🤣
Hmmm memory usage on pods seems to double when you post media 🤔 gotta figure this out 🙃
so what was your day like today? 🤔
I’m really disappointed with Storidge It doesn’t work on a custom Linux OS or Rancher OS 😥 I doubt it’ll even run or install without problems on CRUX 😳 Ahy do so many software developers and companies make blatant assumptions about wheee and how you’ll run their software?! 😡
Came across sdk.split.io today in my AdGuard DNS filtering. All ~4k hits are blocked but coming from my personal iMac. Kind of curious which software I'm running is using this feature flagging + analytics service split.io -- Anyone have any ideas on this? I typically have open at all times, Signal, Messages, Textual 7, Google Chrome, Plex Amp, Micro.Blog, ITerm 2 and Typora. I'd love to know which one of these pieces of software are using this service...~
@jibarito123 Did you also create an account called @jibarito (_which looks really similar_)? Did something go wrong? 🤔 LMK if I can help in any way... Unfortunately there is no way to identify accounts at all as we collect zero personal information on signup, not even an email address, so if you created this account too and you'd like them both merged I can do that (_if you can prove it! 😀_)_
@jibarito123 Glad you like it so far 😎 it’s also decentralized 👌
@dooven Yeah me too I’m afraid! 🤣 I’m not enjoying it last day 7 😥
Containers themselves OTOH have been around for the longest time, they were just made "popular" so to speak by Docker. They existed in the form of BSD Jails (_still do_), then OpenVZ for LInux, then LXC then Linux Namespaces in general (_now part of the Kernel along with CGroups_) and popularized by Docker and Kubernetes.
@adi @lyxal That depends... If you are building static binaries, I _would_ agree with you. But deploying complex software on bare-metal or virtual-machines is actually quite error prone and not very portable at all. Docker (_if it did anything at all_) really shined in what I call a really really good "packaging model" and build tooling. This is now called the OCI Spec. Caching and CoW (_copy-on-write_) or OverlayFS + SHA255 of layers is a wonderful ting for portability.
@adi @lyxal Oh? Why's that? 🤔 They're just Linux Namespaces afterall...
@adi I _think_ because my replies have fallen off the cache and now archived. See this post for the "why"
@lyxal I _should_ do the same shortly... 🤣 But I'm hacking on box 😴
@adi Looks good :) Do you want me to deploy this on ulinux.org ? :)
it was really fucking annoying though walking down the train stairs into the underground tunnel only be faced with a wall of cigarette smoke 🤬 some people just have no decency 😡
@lyxal Haha! 😂 i’m still on day seven so slack 😳
some fucking asshole smoking in the train tunnels 🤬
Quiet day for everyone eh? 🤔