@david@daiwei.me I had to look these up, horror isn’t my genre at all. :-D No idea what the cool kids use today, but I still have zsh as my interactive shell. For shell scripts, though, I try to stick to POSIX and only resort to bash if really needed or it would be too cumbersome.

@david@daiwei.me Not sure if you only mean the code segments or in general. In theory, a general darker text color for read messages would probably work. The thing is that regular white on black is quite standard. In Newsboat, new articles are red (I opted for yellow here) and read ones white. I found that useful and kinda copied it for tt.

@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 I think it might be a bug i just fixed 🤞

@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 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.

@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. 🤣

@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.

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:

Image

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:

Image

@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.

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

@balloon-fu-sen@tw.fus.f5.si yes I wouldn’t go and change your feeds location the location a fourth time that’s for sure! 🤣

@david@daiwei.me Thank you! 🙏

@david@daiwei.me Found it. Some bugs in the “claim limiter”. Fixing…

@david@daiwei.me Please write an issue for this 🙏 I don’t mind which way we go!

@lyse@lyse.isobeef.org Ahh yes, but tt has a “draft” mode right? You didn’t publish, then edit over and over did you? 😅

@lyse@lyse.isobeef.org LOL 😂

The only place where this would be an issue is the Twtxt Search Engine – But as the GDPR also points out:

Art. 17

The one place the “it propagated and I can’t recall it” problem is legally acknowledged is Art. 17(2), and it explicitly scales to what’s technically feasible:

“…the controller, taking account of available technology and the cost of implementation, shall take reasonable steps, including technical measures, to inform controllers which are processing the personal data that the data subject has requested the erasure…”

Best-effort, given the technology. A decentralised, append-only, content-addressed feed is the available technology, and its limits are baked into the standard the law applies. Nobody — not the user, not you — is obliged to guarantee every cached copy vanishes.

@david@daiwei.me you had to poke me, eh?

@david@daiwei.me You mean, you mean… like mowing down a whole rain forest in a thunderstorm’s brutal heat? :-?

Show us today’s rain. :-)

@david@daiwei.me Hahaahaaahaaaaa, that was funny as heck, mate! I had to laugh really hard! :‘-D

@david@daiwei.me Hahaha, for sure. (But my observation wasn’t meant as a complaint.)

@david@daiwei.me 🤣

@david@daiwei.me :-D

@lyse@lyse.isobeef.org Yeah, okay, the default being local means it only stores this stuff offline. So they claim. I don’t trust this and I don’t want to go anywhere near it.

@prologic@twtxt.net @david@daiwei.me Thanks! Hahaha, rest assured, it was not right from the beginning at all. I had to fix it over and over again.

Uuhh, nice, @eldersnake@we.loveprivacy.club is back!

@prologic@twtxt.net Perhaps somebody tried to register “yarn_secret_service”. 8-)

@prologic@twtxt.net Where’s the before picture!? :-D

@movq@www.uninformativ.de Yes, this is absolutely a no-go!

A long time ago when the first telemetry shitstorm happened, I added export GOTELEMETRY=off in my ~/.zshrc. But it doesn’t seem to be picked up at all (I actually call this sabotage!):

$ go env GOTELEMETRY
local

$ go env -w GOTELEMETRY=off
go: GOTELEMETRY cannot be modified

$ go telemetry off

$ go env GOTELEMETRY
off

@prologic@twtxt.net @david@daiwei.me I just want to bring up the following: From a data protection point of view, edits and deletions are important. But that’s about it, I will not join discussions on that topic. :-)

@david@daiwei.me well I happen to agree because one of the fundamental problems is that you can’t have a tax file specification and assume that you can edit it freely by hand as a human and then clients that deal with that specification in machine possible mechanisms the two kind of conflict because humans get things wrong machines don’t

@movq@www.uninformativ.de please don’t waste your time to bugging this. I’ll figure out what’s going on with these new clients.🙏

@prologic@twtxt.net It’s from Gabe’s feed: https://gabesarcade.com/twtxt.txt

@david@daiwei.me It really is almost impossible to debug these hash issues. Only thing I can do is some trial-and-error, to see if I somehow end up at pmrf6ftxsdhr instead of ksou5aqw7w5a. So far, no luck. 😅

@david@daiwei.me LOL 🤣

@kat@yarn.girlonthemoon.xyz Welcome back 🥳

@eldersnake@we.loveprivacy.club Ahh awesome! No worries mate! 🙌

@itsericwoodward@itsericwoodward.com Well I clearly suck 🤣 putt.day #62 ⛳ 22/12 +10
🟡🟢🟡🟡🔴🔴🟡🟢🟢🟢🟡🔴🔴🟢🟢🟢🟡🟢🟢🟢 +2
https://putt.day/s/b4UKsjw0olkS

had to clean a lot of gunk off the top of the van I have to wake up back from our holiday! 😱

@david@collantes.us heads up 👋 that verification code never reached you — outbound email was broken on my end (my mail relay was rejecting twtxt.net senders 🤦‍♂️). Fixed + deployed now 🥳 give the hosted feed another go, it’ll land this time 🤞

@itsericwoodward@itsericwoodward.com Wrote it up 👌 Single-user twtd API is now documented (plain JSON, one bearer token) — posting, uploads, profile, followers + WebFinger: https://git.mills.io/yarnsocial/twtd/src/branch/main/API.md 🎉 Shout if anything’s unclear for TwtKpr 🙏

New in the Twtxt App 🥳 a Hosted feed backend — claim a nick, one tap, no account, no server, nothing to run. Your feed lives at https://twtpub.com/u/yournick and you’re posting from the app straight away 🎉

@GabesArcade@gabesarcade.com Anywhere I can find ‘em 🤣 Gitea Issues, here, there anywhere you want really 😅

@bender@twtxt.net Pffft bender is never mean haha 😆

@bender@twtxt.net LOL 😂

@kat@yarn.girlonthemoon.xyz let me know if mean old Bender can help on anything (especially if it is bending things [please let it be bending, let it be bending!]).

@prologic@twtxt.net I know, I am feeling sentimental. After all the bending done today, a bender needs to find solace in the little things, right?

@bender@twtxt.net ROFL 🤣 That post was from ~17w ago 😅

@prologic@twtxt.net one of my happiest day! Imagine loving pizza, and hearing someone saying “let’s do pizza!”. That’s bending for me! 🤩

Some further ideas/enhancements for Twtxt App …

• On the “Followers” tab, new followers should appear at the top I thnik.
  
• On the Following/Followers, each feed should be clickable/tappable.
  
  • Maybe also tidy it up a bit, displaying the full raw Feed URI is messy.

@balloon-fu-sen@tw.fus.f5.si Thank you for reaching out 👌 I had alraedy done so via Email too a few days back and she upgraded her Pod to yarnd/0.16.x 🎉

@kat@yarn.girlonthemoon.xyz You did! 🎉

@lyse@lyse.isobeef.org None. I rejected ithe invite request 🤣

@david@daiwei.me Well… I can’t! becuase the email supplied was nobody@invalid or some shit™ 💩

@prologic@twtxt.net You also have to tell us the username!

@david@daiwei.me I agree, the App (https://twtxt.app) really does work quite nicely 👌

@david@daiwei.me that was literally one of the messages I got this morning with an invite request to join this pod 😱

Hell yeah, @kat@yarn.girlonthemoon.xyz is back! \o/

@yarn_police@twtxt.net LOL 😂

@lyse@lyse.isobeef.org Quite effective then eh? 🤣

@kat@yarn.girlonthemoon.xyz Welcome back!!!! 🎉 Did you upgrade your yarnd? 🤔

@david@daiwei.me Yeah the search engine/crawler has only found 28 active users in the ecosystem so far 😅

@prologic@twtxt.net this is so epic!!!

anyway thank you to @prologic@twtxt.net for the email heads up to upgrade this pod! we SHOULD be on the latest version, if i did it right…

@kat@yarn.girlonthemoon.xyz omg i haven’t been here in FOREVER i’m sorry yarn friends!!! i’ve had a lot going on including being extremely depressed :(

@kat@yarn.girlonthemoon.xyz REAL SHIT?

@david@daiwei.me Not so keen on the mowing part. :-)

@prologic@twtxt.net That’s a good way to keep spammers out:

Your browser did not pass the anti-spam check! Please make sure JavaScript is enabled and try again.

It was turned on.

@david@daiwei.me Haha, great response!

@movq@www.uninformativ.de Hottest room is still at 24°C. But that will change in this week, no doubt. :-(

@david@daiwei.me It’s all fixed now, for good 😌

Yeah this is my fault sorry! In this case i’ve axtually found yarns to be soex non-compliant 😱 Twtxt.app is doing yhe right thing🤣 As is Jammy 👌