@prologic@twtxt.net @movq@www.uninformativ.de Same with tt, hash v2 has to be used right from the epoch onward. (And now replying to a message with a timestamp before the epoch still results in a v1 hash.)

@david@daiwei.me I think yhwre was 😅

@david@daiwei.me That should be it fixed!

@david@daiwei.me I think it might be a bug i just fixed 🤞

@prologic@twtxt.net Additional: I still get the 403 if I don’t specify a feed URL.

@prologic@twtxt.net That’s more-or-less it. If I could do it without Codeberg (just using SCP, SSHFS, or something similar), that would be even better, but probably out-of-scope for the project.
My thinking behind how twtxt.app worked was that I could give it access to a repo, in order to add to my twtxt.txt, but that the alternative feed URL would then be presented to other users instead of the Codeberg URL; unless, of course, this is already part of the twtxt metadata.
In short, the feed URL would just be a dummy.

@movq@www.uninformativ.de I can’t do Java ever again 🤣

@movq@www.uninformativ.de Dair enough

@lyse@lyse.isobeef.org Good question, I don’t know yet if the standard library has been extended a lot. 🤔

@prologic@twtxt.net No. After the cutoff-date, hashes are expected to be v2. End of story.

(In jenny, a twt can only ever have one thing that can be used for threading.)

@dce@hashnix.club So let me get this straight… You want to store your feed on a Codeberg repo right? But you want to clone that repo down somewhere else to serve it on a different location. Right? And you’d like to use the Twtxt App (https://twtxt.app) to front all of this? Right?

@bender@twtxt.net LOL 😂

You may have noticed I am not as active as I used to be here. Old @bender@twtxt.net isn’t going anywhere, though! But… I am Hyde, and my Jekyll resides at @david@daiwei.me. Jekyll is having his turn more often now, so if you follow my pure, unrestrained evil, you may as well follow my dark desires, hypocrite counterpart. 😈🤣

Follow @david@daiwei.me, or I will bend you!

@david@daiwei.me @prologic@twtxt.net Oh, I see.

@david@daiwei.me My twtxt.txt is on Codeberg. The repo contains (or would contain) an exact copy of the file as it is on Hashnix.

@prologic@twtxt.net Details: “https://codeberg.org”, “(API key)”, “twtxt”, “twtxt.txt”, “https://hashnix.club/~dce/twtxt.txt”

@prologic@twtxt.net I created a repo called twtxt and an application key with read/write access to it (and only it). I then cloned the repo on Hashnix and hardlinked my twtxt into it, before committing and pushing. Next, I supplied the appropriate details on twtxt.app, under Codeberg/Gitea, and clicked “Connect”. gitea https://codeberg.org/api/v1/user: 403 Forbidden.

@david@daiwei.me Yes, but then I have to create and maintain an account I’ll never use 🤣

@dce@hashnix.club Ahh! Let’s fix the 403 error then? I don’t have access to Codeberg, so I can’t reasily test. Can you walk me through what you tried and any other details? I’ll get this fixed.

@prologic@twtxt.net I was actually trying to use twtxt.app, with Codeberg as a backend, but I kept getting a 403 error. As for twtd, well, my twtxt is hosted on a pubnix. The people behind Hashnix are really nice, but I’d rather not bother them with software requests if there’s a simpler solution, and I imagine it would be rude of me to run a deamon from my homedir without permission. Could be worth asking, though, unless I decide to write a client myself.

@dce@hashnix.club You may also be interested in the Twtxt App and the little tiny twtd publishing backend? 🤔

@david@daiwei.me Of course 🤣 Incognito sessions store nothing once closed. 🤣

@prologic@twtxt.net twet 1.3.0 built from v1.3.0-21-gff43ee0 at 2025-08-25T23:27:41Z, from https://github.com/quite/twet. Unmaintained since 2020. To be honest, I was considering writing a basic client of my own…

@movq@www.uninformativ.de @lyse@lyse.isobeef.org Are you clients remaining compatible with Hash v1 in case older clients are still well not upgraded? 🤔

@dce@hashnix.club which version of Twet are you using? I might see if I can get it updated for you.

@david@daiwei.me Those two twtxts were separate replies. However, I am currently using twet, which doesn’t support hash v2.

@lyse@lyse.isobeef.org I rather like KornShell. Not as awkwardly bare-bones as Bourne or Almquist; but more minimal and lightweight than Bash or Zsh.

@lyse@lyse.isobeef.org Thank you!

Cool, @dce@hashnix.club. You’re the first one I come across who actually writes Korn shell scripts. :-)

@movq@www.uninformativ.de The nice thing about properties is that you can compute and cache things on the fly at first attempt and also ensure validation for writing. But like you said, since it’s not obvious that reading or writing might do some more things, it’s strongly advised to avoid doing expensive stuff disguised as properties.

I reckon the vast majority of property use cases is to provide read-only access. At least that was my impression when I was doing a lot more in Python.

Personally, I think that this just reads a lot nicer:

oink.my_property
oink.my_property = 42

Than:

oink.get_my_property()
oink.set_my_property(42)

Btw, any field access is implemented using method calls. I might be wrong, but I believe there’s always __getattr__ and __setattr__ involved. 8-)

@movq@www.uninformativ.de My grief with Java is that it’s sooo verbose. Sure, all the enterprise garbage makes it a hell lot more terrible, but even regular Java feels always so lengthy. And back in the days when I was using it daily, I missed so many convenient things in the stdlib after having experienced Python’s “batteries included”. Not sure if or how recent Java versions caught up.

@david@daiwei.me Oh, really? I thought I’ve posted compose view screenshots before. Anyway. Glad you like it as much as I do. :-)

The update interval has always been one second. I just didn’t remember and thus tried to time it by watching the preview update while typing. It felt like roughly under two seconds, but apparently my inner clock was off. After taking the screenshot and then examining it more closely, I noticed that the interval is stated right in the UI. :-D So, I just amended my message and didn’t bother taking a new screenshot. I figured I just leave it alone and see who spots the change, if at all. And, of course, you found the easter egg. Congrats, mate! 8-)

@movq@www.uninformativ.de Looks like subject parsing is broken.

@david@daiwei.me Ramen! Bon appetit.

@balloon-fu-sen@tw.fus.f5.si Not bad, quite a groovy sound.

@zvava@twtxt.net hunter2

@prologic@twtxt.net Not sure if this really counts as a draft mode or this is what you had in mind. I just was in the editor for ages and didn’t close it. tt provides an integrated preview for the rendered message in there. It automatically updates every second.

Here’s a screenshot of the compose view with the conversation context on the top to which to reply to, the editor in the middle and the almost-live preview at the bottom, I hope it’s big enough:

But it’s not like I hit the “Add message” button in the compose view (the one currently selected on the screenshot), see the message in the conversation tree and then come back into the compose view to continue editing. There’s no edit functionality in tt. Once the message is appended to my twtxt.txt file on disk, all I can do is edit it with vim. The U+2028 line breaks are really annoying to deal with (I’m sure I could do something about that if I spent the time), so I try to avoid that at all costs.

Once new messages have been added to my local file, I then manually upload the file to my server in a separate terminal. There’s no upload command integrated into tt. Right from my very first message in the beginning, I’ve always done it exactly like that. I’m used to this and it really doesn’t bother me. But I can see that others might not be fans of that at all. I might add an upload mechanism to tt at some point in the future.

@david@daiwei.me Very nice!

Dear weather gods, can we please also have a decent amount of rain and not just a few drops that only make the humidity even worse?

@david@daiwei.me The stuff in parens is lost on yarnd:

@dce@hashnix.club I like the teal colors in the file manager.

@david@daiwei.me agreed on those. I have also noticed that the buttons are the top (Timeline, Mentions, Follows, Settings) shift a bit when clicked. I am not sure what’s causing that.

@david@daiwei.me Yeah, Oracle is a Dumpster Fire, that’s true. 🫤

@movq@www.uninformativ.de ha ha in this case I think I’m OK with a broken thread ha ha

@prologic@twtxt.net See, that’s what edit/delete is good for. 😅🤪

@movq@www.uninformativ.de yeah it’s one of the fundamental principles of Yarn social and everything that I’ve poured into the ecosystem that we’ve collectively built here over the last, What is it six or seven years now?

@zvava@twtxt.net oooos 🤣

@david@daiwei.me That’s a good thing. I still use it heavily, but I also realize that it is addictive. This whole idea of getting likes and boosts is horrible. Seeing “number goes up” is inherently addictive design, if you ask me. This should never have been added to a Free Platform like Mastodon, and I’m glad that twtxt doesn’t have anything like it.

@movq@www.uninformativ.de That’s crazy… Do not want!

@david@daiwei.me @prologic@twtxt.net No worries, I was just trying it on for size.

I played it again today (10/12 on first try), but I can’t say that I love the format of the “share link” (the unnecessary yellow and green circles).

I think if I did want to post daily scores or something (for posterity), I’d likely setup a separate feed just for my “achievements”. 😁

@misskatie@twtpub.com Awesome!!! Welcome 🤗