@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.
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! 😅
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?
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
although I agree that it helps, I don’t see completely correct to leave the nick definition to the source .txt. It could be wrong from the start or outdated with the time.
I’d rather prefer to get it from the mentioned .txt nick metadata (could be cached for performance).
So my vote would to make it mandatory to follow @<name url> but only using that name/nick if the URL doesn’t contain another nick.
A main advantage is that when the destination URL changes the nick, it’ll be automagically updated in the thread view (as happens with some other microblogging platforms, following the Jakob’s Law)
@<url> form of mentions. Strictly require that all mentions include a nickname/name; i.e: @<name url>.
word of the thay, prosoal
Is it a typo of Proposal right? =P (Genuinely asking)
@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
@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.
@lyse@lyse.isobeef.org This could just be a bugger Makefile or something. I’m not sure what version @kat@yarn.girlonthemoon.xyz built/deployed from? 🤔🤔 – Also I need to release v2.0 soon™
ROFL 🤣
@@yarn.girlonthemoon.xyz where do I buy that lifetime ticket? Temme, I am ready!
Thanks, I’m trying my best. Also, nice to meet you (and welcome back?) @oevl@twtxt.net, never seen you around before. 🙌
@prologic@twtxt.net Don’t you dare fix it xD it’s not a bug, it’s a feature! xD
@kingdomcome@yarn.girlonthemoon.xyz I’m all in!
Hmm, I just noticed that the feed template seems to be broken on your yarnd instance, @kat@yarn.girlonthemoon.xyz. Looking at your raw feed file (and your mates as well), line 6 reads:
# This is hosted by a Yarn.social pod yarn running yarnd ERSION@OMMIT go1.23.4
^^^^^^^^^^^^
Looks like the first letters of the version and commit got somehow chopped off. I’ve no idea what happened here, maybe @prologic@twtxt.net knows something. :-? I’m not familiar with the templating, I just recall @xuu@txt.sour.is reporting in IRC the other day that he’s also having great fun with his custom preamble from time to time.
That “broken” comment doesn’t hurt anything, it’s still a proper comment and hence ignored by clients. It’s just odd, that’s all.
@movq@www.uninformativ.de Very cool!
The editor can launch a new shell now:
https://movq.de/v/6ec68b50dd/los86-edit-shell.mp4
Trivial to implement but super useful. It allows for simple but meaningful dev cycles: Edit source code, run/test it, back to editor. That’s what I do in the video.
(The Brainfuck program is silly, but I got nothing else at the moment.)
The I/O cache is also getting better. All that back and forth doesn’t hit the disk at all, once cached.
This whole thing is much more fun and interesting when you run it from a real floppy disk. It’s a 5.25” floppy in the video (so it’s actually floppy 😅). Disk seek times can be catastrophic and you don’t notice any of this on modern disks.
@<url> form of mentions. Strictly require that all mentions include a nickname/name; i.e: @<name url>.
tt currently supports all three forms: @<nick url>, @<url> and even the illegal @<nick>. The difference between the last two is whether the token in angle brackets looks like a URL or not. Whenever a nick is available, the nick is rendered. In case there is just a URL, it tries to resolve the nick from the subscriptions. If that also does not work, it displays the URL.
i wanna try streaming with owncast using my camcorder as the input device because i found out that i might be able to do that and now i really wanna fuckin try it lol
trying to set up @movq@www.uninformativ.de’s jenny client… currently trying to find where twtxt files are stored on the server so i can set up the scp script i have for this
@andros@twtxt.andros.dev Even though I’m not an Emacs user, that’s really cool! :-)
good morning yarn friends. we need a funny name for yarn posters. what’s something that fits the yarn theme…. i mean we quite literally have threads here. yarn threads. how epic is that. now us posters need a funny name too.
@prologic@twtxt.net i thought i was going insane when i saw blank posts on my TL i was like is noscript fucking with me again but no it’s you guys fucking around LOLLLL
(quiet… secret… 😀)
@bender@twtxt.net Hahaha! :-D
@kat@yarn.girlonthemoon.xyz Thanks!
@<url> form of mentions. Strictly require that all mentions include a nickname/name; i.e: @<name url>.
@prologic@twtxt.net @movq@www.uninformativ.de Well, the original Twtxt Specification explicitly allows for the short form with just a URL and no nick: https://twtxt.readthedocs.io/en/latest/user/twtxtfile.html#format-specification
Mentions are embedded within the text in either
@<source.nick source.url>or@<source.url>format […][…=]
I’d just continue supporting it, even though I don’t see it all that often in the wild. I guess more common is the case where just a nick is given, which is illegal. But yarnd users seem to produce it every now and then.
What’s the motivation for deprecation?
@andros@twtxt.andros.dev Being able to render user avatars is certainly nice. 😃 I’m always happy to see more twtxt/Yarn clients!
@prologic@twtxt.net lol 😅