@kat@yarn.girlonthemoon.xyz Thinking maybe you’d like to alpha teat EdgeGuard too? 🤔 – My own alternative solution to Clownflare 🤣
@kat@yarn.girlonthemoon.xyz This is so cool!
@kat@yarn.girlonthemoon.xyz definitely a fun way to get better at bash scripting by hand (AKA learn how it works besides the extreme basics i know) and use gum to make them cute too
@kat@yarn.girlonthemoon.xyz both scripts are here under the names ‘getlyr’ and ‘now playing’ if you wanna try them out yourself, just make sure you have gum installed (also curl and jq but most people have those i think) https://git.sr.ht/~chasinglightning/dotfiles/tree/main/item/home/.local/bin
been playing with making fun scripts using charm CLI’s gum library :P
one that gets lyrics from an open lyrics database’s API and accepts input for artist & song names: https://asciinema.org/a/697860
and one that uses a user-provided last.fm API key to pull what’s currently playing or what last played on your account :) https://asciinema.org/a/697874
@prologic@twtxt.net ah that’s good lol! i once pulled from main for a huge web app that i deployed and it haunts me because it will make upgrading so much harder lol
@slashdot@feeds.twtxt.net Have to agree with the comments on this one 😆 Zuck hasn’t invented shit. Period.
Nooooooooi 😅
twtxt.txt
, following your recommendation, there could be many "twtxt" nicks. 😀
@doesnm@doesnm.p.psf.lt the logic that keeps on growing! :-D
@<url>
form of mentions. Strictly require that all mentions include a nickname/name; i.e: @<name url>
.
@bender@twtxt.net Hahahahah 🤣🤣
@bender@twtxt.net That could work aactually…
@kat@yarn.girlonthemoon.xyz pretty much 🤣🤣
@ocdtrekkie@twtxt.net Do you have a copy of his feed in your archive? 🤔🤔
Anyway… Sounds like there is a bug with the version logic. I’ll see if I can fix it.
@kat@yarn.girlonthemoon.xyz Building from source and from the main
branch is totally fine. In fact encouraged. I have a philosophy of main
being stable anyway and making sure backwards compatibility is kept in mind when changing things. i.e: No database migrations to run by hand or what not.
Ugh! Not @david@collantes.us, but this one. I am going nuts. Well, I am nuts!
I am letting this domain go at the end of this year. Another of my alter ego feeds will be gone then. Oh, the humanity! 😅
Yes, error on my side. All of the sudden jenny refused to show me my own posts. Had to recreate mailbox (got rid of cache too) to make it work.
@movq@www.uninformativ.de I think it was user error. Testing again.
Testing … (yeah!)
@bender@twtxt.net (secret received!).
example.com/x/bananas/yo.txt
, and the feed has no nick. What is the nick?
I mean, since most feeds are named twtxt.txt
, following your recommendation, there could be many “twtxt” nicks. 😀
example.com/x/bananas/yo.txt
, and the feed has no nick. What is the nick?
@doesnm@doesnm.p.psf.lt so, example.com/x/pineapples/yo.txt
nick is also yo?
@doesnm@doesnm.p.psf.lt I see problems with that, that do not exist on my approach. You could see, example.com/x/bananas/yo.txt
, and the feed has no nick. What is the nick?
@prologic@twtxt.net so i did a mistake that i’ve done before and i think i just pulled from the main branch which is STUPID i KNOW and i don’t LEARN but whatever. i was having trouble with my go version and the makefile so i think i literally just ran it as my user with go in the path and redirected the binaries to go to a temporary directory i made and then moved them to /usr/bin lol. i’m not sure what could’ve caused this! probably something in the pipeline of weirdness i just wrote out
@prologic@twtxt.net thank you so much!
@prologic@twtxt.net LMAO thats so funny i need to try jenny i was trying it but i couldn’t figure out my twtxt sync script for it
@prologic@twtxt.net wait thats so cute re: the yarn name! i had no idea! we’re all just keeping the yarn ball rolling…
@kingdomcome@yarn.girlonthemoon.xyz love this for you
@kingdomcome@yarn.girlonthemoon.xyz trueee! good point
@kat@yarn.girlonthemoon.xyz I mean, you could do the mjd approach & record your monitor while sitting a few feet away, with a Bluetooth mouse & keeb, watching your inputs from the view finder
I’m so hot when I do things with fabric no sensible person would do
Or using the same twt hash method, but only for the URL, to generate the nick, if it doesn’t exist, like so, @5vxo4ia@twtxt.net
@<url>
form of mentions. Strictly require that all mentions include a nickname/name; i.e: @<name url>
.
@eapl.me@eapl.me yeah, it is a typo, meant to be proposal. OP is the “Lord of the Typos”. :-P
@probiotic@twtxt.net I see nicks as a label, but otherwise superfluous. I can give whatever nick I want to anyone, as long as the feed exists (at least on Yarn).
So, if nick exist on feed, great, use it! if it doesn’t, assign a random hash derived from whole URL as nick. Done. :-D
@lyse@lyse.isobeef.org Hmmmm the smell of burning cotton 🤣
@<url>
form of mentions. Strictly require that all mentions include a nickname/name; i.e: @<name url>
.
@lyse@lyse.isobeef.org Hmm you ate right 😆 Also did you volunteer to fix this 🤔🤣
@<url>
form of mentions. Strictly require that all mentions include a nickname/name; i.e: @<name url>
.
@prologic@twtxt.net If you’ve got the feed URL in yarnd’s cache, you can easily look up a missing nick. If you can’t find it, just show the URL (or maybe just the domain name to be halfway consistent with this @nick@domain
thing that yarnd invented) and be done. It’s really that simple.
When yarnds peer with each other, the odds of actually having come across that feed URL in the past are higher than with traditional clients that only have their local set of subscribed feeds. One additional improvment would be to also look at all the mentions and see if somebody used a nick for that URL and go with that.
Yeah, yarnd currently renders some really weird shit when the mention contains just a URL, but I’d call that a bug for sure.
Personally, I do not like the @nick@domain
syntax at all. It looks silly to my eyes. What might have also contributed is the fact of this mentions syntax gotten screwed up so many times by yarnd in the past. But that’s a totally different topic.
@kat@yarn.girlonthemoon.xyz @prologic@twtxt.net So, a burning roll of yarn…? :-D
@prologic@twtxt.net Since I live in Germany, I do believe the media here is generally reputable. It really depends where you live of course. Source I look at are Reuters, NPR, The Guardian, Die Zeit, NY Times, CNN, Tagesschau, Spiegel Online, RP Online (for local news), … I would never just trust what I see in my social media feeds.
@gallowsgryph@prismdragon.net Sorry to hear that dude 😢 Hope things improve for you! 👌👌
Wow, what a busy month-and-a-third it’s been. Between family health issues and my own injuries, I’m finally getting a bit of a decent breather.
2025 has been off to a perfect start. /s
@bender@twtxt.net Yes yes I konw 🤣🤣
@kat@yarn.girlonthemoon.xyz It most certainly was us fucking around 🤣🤣 Turns out to be a side-effect of the way the Twt Subject
extension is implemented in yarnd
and now apparently jenny
🤣🤣 Where it strips out the subject from the displayed/rendered content. Which is what you want… But oh well haha 😆
@kat@yarn.girlonthemoon.xyz Haha, that’s why we came up with the name “yarn” and “yarn social”. A yarn is an Australian and Canadian (and a few other places) term that means “to have a friendly conversation”, “to have a chat”. Usually around a campfire 🔥
@kat@yarn.girlonthemoon.xyz The twtxt files for yarnd
are stored under /path/to/data
under the feeds
directory. Oner per user.
@<url>
form of mentions. Strictly require that all mentions include a nickname/name; i.e: @<name url>
.
Was there ever a reason to do that? 🤔
I’m not sure to be honest. I have no idea why you’d ever want to do a “nameless” @-mention@twtxt.net.
As an aside, if we could all agree, I’d personally just say we scrap this whole fragile broken shit and bring out WebMentions and be done with it. And then mentions are always @nick@domain
and looked up, cached and can never be screwed up haha 🤣
@<url>
form of mentions. Strictly require that all mentions include a nickname/name; i.e: @<name url>
.
What’s the motivation for deprecation?
Namely that without the mention having a label (as such) it becomes very hard to render it in any sane/nice way. I think we should just stick to @<label url>
personally. It makes implementations have to worry about far less edge cases.