# 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 172
# self = https://watcher.sour.is?uri=https://envs.net/~duriny/twtxt.txt&offset=72
I see that the competition for twtr is rapidly growing ;) I'll have to rush to get v0.2 out soon...
Russia just invaded Ukraine....
давай не будем говорить об этом :thumbsup:
Thank you, thank you! (My immune system did all the hard work, all I did was wait in a line for a bit lol)
The covid booster was a pain but I'm back up to a fully operational battlestation!
@novaburst thanks for taking interest in twtr! :) I am currently working to have twtr integrate with any yarn.social pod, but it won't be released until v0.2.0. I'm currently recovering from my boster shot, but in the meantime, twtr v0.1.x is fully cappable of posting to any yarn pod through creative use of the curl command and the pre/post tweet hooks :)
@novaburst thanks for taking interest in twtr! :) I am currently working to have twtr integrate with any yarn.social pod, but it won't be released until v0.2.0. I'm currently recovering from my booster shot, but in the meantime, twtr v0.1.x is fully capable of posting to any yarn pod through creative use of the curl command and the pre/post tweet hooks :)
Yes please :D, let me know if you need my help for testing or anything :)
.......well I feel like a right ninny, good thing I didn't finish my package to do exactly that XD, thank you, I'll use git.mills.io/yarnsocial/yarn/client instead of reinventing the wheel lol
For now I'm just planning on being able to choose a back end to twtr, e.g. a yarn pod, self hosting via ssh (like I am right now), maybe allowing hosting as a Github Gist, that sort of thing. I haven't taken a look at yarnc yet, but I might take a look now that you mention it :). I'm currently thinking of making the backend available as something like go get duriny.envs.sh/twtr/backend/yarn, but if you think yarnc might have some good overlap, maybe twtr can use go get Yarn.Social/go/api or something?
I hope you don't mind me creating an account on your pod? I do plan on removing the test tweets after myself once I'm done :)
I'm creating a wrapper for the Yarn.Social API as a back end to twtr, so twtr users can use a yarn pod as a twtxt.txt host. Makes it easy to be able to tweet from the command line and the browser (and presumably the mobile app?) all at once :)
Oh split it out for sure, the more the code is broken down into small pieces that do one thing well the better :)
@prologic I've rewritten the parser in twtr aproximiately 4 or 5 times in the past few weeks, I haven't quite worked out how to implement all of the spec extensions yet, so I recokon having a common parser would be fantastic! That being said, for the sake of diversity it's probably also good to have a couple of implementations floating about.
@prologic I've rewritten the parser in twtr approximately 4 or 5 times in the past few weeks, I haven't quite worked out how to implement all of the spec extensions yet, so I reckon having a common parser would be fantastic! That being said, for the sake of diversity it's probably also good to have a couple of implementations floating about.
pp as in the perl compiler/packager thingy? Yeah you can run any shell script in a server side CGI, as long as the permissions and PATH are all correct. Although envs.net already supports perl for CGI, so you could just use <!--#include virtual="cgi-bin/foo.pl" --> rather than calling pp
As I said, I'm clearly biased ;)
Personally I think <!--#include virtual=cgi-bin/fortune.sh--> is the simplest, but I'm an envs.neter, I'm clearly biased :D
Ah sorry @david I missed your twt lol. Yeah I don't think its the difference in the running version, non of the intermediary code changes stand out either. Could be a caching/config issue? I know @prologic's pod takes longer to pick up my twts than netbros does, maybe the twtxt.net cache just lost those twts?
strangely the actually commits don't show a significant code change that could break this, one is a CSS change and the other is a Makefile change :/
I think it might be that the two pods are on a different commit, I'll note them here for reference, netbros.com is on 0.13.0@278fda8, and twtxt.net is on 0.13.0@ee35b5c
No problem, tag me in any issues on git.mills.io and I'll take a crack at it :)
@adi what you don't see is the 15 or so times I have twtr tweet "I hope this works..." in my shell history lol
@prologic that would definitely be interesting! I'm hoping to have a (mostly) workable v0.1 release in the next day or two, I'd be happy to help out in the community :), what would you want help with?
@prologic that would definetely be interesting! I'm hoping to have a (mostly) workable v0.1 release in the next day or two, I'd be happy to help out in the community :), what would you want help with?
Hello World! This is the first tweet written using the pre/post hook functionality of twtr! I hope it works! :D
Tea might help, I'm already pretty exhausted, lets see where some jumping jacks take me
I haven't slept in two days :/
@movq 0.0 what happened to unicomp?!! I bought my model M from them a few years back, I love those guys
One possible way to use twtxt for private messages would be using http authentication, then it's private to anyone who's allowed to see the twtxt.txt file, otherwise the it returns 401 Unauthorized. That's not exactly an easy solution since both parties need to agree on authentication, and no client is set up for that, but it at least is self-hosted and decentralised :D
Ohh beat me to the punch, I've starred you on GitHub as well, the more clients we have the better :)
@fastidious would it be a good idea to add support for the pronouns field to yarn?
No worries mate, I've added a # pronouns = field to my twtxt.txt, should have thought to do that earlier
@fastidious Please let me know if it does end up working, it would be a really useful feature since I type out all my mentions by hand :D
@lyse No, I'm confined to my little corner of the internet here. @prologic would it be possible to support http headers as well? I think that the Go vanity imports style is clever :), just a little limiting to self-hosters like me :/
@prologic would it be possible to add this on non-root pages? I host my twtxt.txt on envs.net, which is a shared tilde, I don't control root page, and even if I did, that meta tag would only work for my one twtxt file. I wouldn't want to rob my fellow envs.neters of being able to use yarn :/
I haven't set up an automation for this (twtr is still WIP), but I thought I'd share. I like the idea, maybe I'll post a git push hook :)
I was thinking about how to best create a news twtwt.txt for twtr, and I've developed a way to format git commit logs as a twtxt file: git log --format="%aI%x09%ae: %s"
I might leave input validation for later, maybe I'll add an --html option to twtr to make it easier :)
Good catch on that typo @lyse, thanks :)
I'm going AFK for a while, @prologic let me know if your interested in my script and I'll make a repo for it :)
As it happens I just added thread support to my script, its up on my home page now ;)
to be honest I didn't think anybody would ever find my twtxt feed so the fact that it is getting picked up on twtxt.net automatically is kind of amazing lol
I also have script that renders my twts to my home page, I can post it if anybody is interested :)
It would be really cool to get some publicity for twtr, thanks! I'll have to make that v0.0.1 release soon lol
@prologic I'm using twtr to type this right now
@prologic twtr should be compatible with Yarn.Social out of the box :)
@prologic I did create a Yarn.Social account but I don't want to manage two feeds lol
@fastidious note that the Go import path is duriny.envs.sh/twtr :)
While not even remotely close to a v1 release, twtr is starting to take shape, I might tag v0.0.1 soon :D
It's a good day for a haircut
I sometimes wonder if the JWST will see the wreckage of an Inter Galactic empire in the distant past of our universe
I just discovered that you can write Go documentation to look and feel like a manpage
The go import path for "duriny.envs.sh/twtr" is now up and running! :)
It's a shame that the twtxt client is broken as of python 3.9, :/