Welcome, @c0by@c0by.de and @robbinaer@robbinaer.info!
My coworker Brian Douglas invited GitLab’s Jacob Schatz and me to discuss GitLab’s use of Vue.js on the latest episode of his podcast, JAMStack Radio - https://www.heavybit.com/library/podcasts/jamstack-radio/ep-21-why-gitlab-chose-vue-js/
@tx@0x1a4.1337.cx #stagit looks really cool, thanks for mentioning it.
Re: support for other protocols, it seems like twtxt would be pretty easily adapted to work over the p2p file network DAT, though it’d need client support for DAT or some way to follow people via files and sync in the background, which might be simpler for clients to support but would still require changes to most clients.
@dave@davebucklin.com bingo!
@kas@enotty.dk I’m not currently using a handrolled client, but I’ve started a couple.
Rethemed my desktop using the colors from the atom-one-dark theme: https://imgur.com/a/IDunX
@nblade@nblade.sdf.org I could probably put something together, but I went this route originally because existing generators felt like they took too much control from me over the exact output. I want very small, static pages I can throw behind nginx, and I want to know exactly what the contents are. My current mess of spaghetti Racket is getting hairy since I’m halfway through an unfinished rewrite I started a while ago and forgot about, but at least I know exactly what it’s doing.
@leveck@leveck.us for sure! Especially when you’re bad at doing frequent git commits when you’re the only one working on something.
I’m trying to decide whether soldiering on with the messy codebase of my homegrown site generator is worth it or if I should redo my site in a more established tool.
@leveck@leveck.us welcome to twtxt!
@nblade@nblade.sdf.org welcome!
@pete@petedeas.co.uk that’s a clever solution; I’ll have to set up something like that.
Despite that, I’m still a big fan of the service and check it daily. It’s much more enjoyable than Twitter is, for sure, even with its drawbacks.
@tdemin@tdemin.github.io good points, though another that I’ve noticed is that it’s difficult to tell who in your network is actually reachable with your tweets. My HTTPS cert went unupdated for a brief while and now I have no idea who is still following me since I got it working again, so it’s difficult to tell where I can really have a conversation. A centralized service can tell who’s following who, but that’s basically impossible in twtxt.
@c-keen@pestilenz.org welcome!
@tdemin@tdemin.github.io yikes! It’s unbelievable that “We physically can’t give you that data” is treated as “It was clear that there was no intention to cooperate with the investigation” - that’s utterly absurd.
@freemor@freemor.homelinux.net @kas@enotty.dk #twtxt’s quietness is actually something I enjoy about it. I care a lot more about signal-to-noise ratio than I care about the regular activity. It’s also a really fun thing to write clients for to play around with new libraries or languages.
@tdemin@tdemin.github.io too busy working on a twtxt client to tweet on twtxt
another test tweet…
@kas@enotty.dk my bad - I’ve been developing a twtxt client, hence the frequent requests. I’m switching it over to use a fs cache for testing so I’m not hitting the twtxt files so much.
/me is finally working on a twtxt client
/me really wishes asciinema had audio support.
@quite@lublin.se the static site CMS? It’s open source: https://github.com/netlify/netlify-cms/
@phil@philmcclure.duckdns.org I actually just started a new job working on a frontend for Hugo (and other static site generators).
@quite@lublin.se that’s one of the approaches I was thinking of.
@kas@enotty.dk that sounds fair to me.
Additionally, there’s a lot that can be done by a client to reduce the network traffic and UI latency of twtxt without changing the protocol.
When it comes to performance issues, I honestly think the solution is just “don’t follow so many people”. You only pull the feeds you read, and once one’s feeds are too much for the computer to handle, they’ll almost certainly have far too much content for a person to actually read.
@mdom@domgoergen.com, @kas@enotty.dk re: metadata, I’m (obviously) in favor of my suggestion for metadata-in-comments, but I don’t think we should have comments in comments.
@mdom@domgoergen.com, @dave@davebucklin.com, @kas@enotty.dk I agree with the “no max length; show at least 140chars” idea.
lsc has an initial scoping mechanism: https://asciinema.org/a/73now0dbnauz44f4rjqpdfva5
lsc has lambdas now: https://asciinema.org/a/aihpsfibe1u55bqpogkq6qyt3
I’m not working on bussard, I’m just IRC friends with @technomancy@technomancy.us and he expressed interest in making scheme available there.
@mdom@domgoergen.com mostly for fun, but once I have it working more it’ll get integrated into https://gitlab.com/technomancy/bussard.
My latest side project: https://asciinema.org/a/0iur84zj6tb2gm93ys7l8p8za
Last night I learned the hard way that rubber-dome keycaps are quite intolerant of being removed on a whim.
Been checking out Dyalog APL lately - it’s definitely a mind-bender.
(EDIT: it worked)
@mdom@domgoergen.com @kas@enotty.dk thanks! I was checking access logs on nginx and noticed a bunch of 404s to my twtxt url, so I decided to pick it back up.
Think I’ll try out twtxt again for while…
How should metadata about a twtxt feed be stored? Weigh in @ https://github.com/buckket/twtxt/issues/48
Who all is using the node version? I’m more of a JS hacker so I might contribute to that, but the .py version seems more popular.
no shortcut for unfollowing cause who needs that kind of negativity
part 3: make ‘tf’ run ‘twtxt follow “$@”’
part 2: make ‘tw’ run ‘twtxt tweet “$@”’
twtxt-able twtxt helper scripts, part 1: make ‘tt’ run ‘twtxt timeline -l 1000 | less’
I find the wide variety of ways people are deploying twtxt pretty fascinating
Guess I’m too late: https://github.com/plomlompom/htwtxt
Been thinking about writing a twtxt-AAS provider.
Hello, world