@fastidious@arrakis.netbros.com
Boot media created. All set an ready for this weekend. Woot!

sudo /Applications/Install\ macOS\ Monterey.app/Contents/Resources/createinstallmedia --volume /Volumes/USBDrive

@prologic@twtxt.net I’ve been working away on side projects: http://git.jb55.com. Trying more these days to not tweet about stuff I’m working on until I’m finished.

**

🧮 USERS:3 FEEDS:6 TWTS:218 BLOGS:0 ARCHIVED:52943 CACHE:2028 FOLLOWERS:7 FOLLOWING:23

@thecanine@twtxt.net
LOL. Now I need to convince my boss. 😩

@movq@www.uninformativ.de
Yes, I did ask whether or not it was possible to move twts to an “archive” folder, but it will be the same at @stackeffect@twtxt.stackeffect.de experienced (which I have, too), that is, twts will “come back”.

There is no clear solution, I am afraid, right? It is the nature of the beast.

@movq@www.uninformativ.de

I’m curious, what is your use case for deleting twts?
Not just deleting, also sorting into other folders is impossible.
It also doesn’t scale in the long term. When I cannot delete twts then I have a full copy of every twtxt I follow - forever. That’s a waste of bandwidth and disk space.

@movq@www.uninformativ.de How is deletion supposed to work? In mutt I deleted by D~d>1m and then fetched by !jenny -f. This brings back all deleted twts. Isn’t lastmods used to skip older twts?

**

🧮 USERS:3 FEEDS:6 TWTS:217 BLOGS:0 ARCHIVED:52648 CACHE:2015 FOLLOWERS:7 FOLLOWING:23

@fastidious@arrakis.netbros.com
Some signs from here: $ (one), $$ (two), $$$ (three).

@fastidious@arrakis.netbros.com
The signs show fine on jenny. So, it is a display thing. Probably related to Markdown.

**

🧮 USERS:3 FEEDS:6 TWTS:216 BLOGS:0 ARCHIVED:52412 CACHE:2110 FOLLOWERS:7 FOLLOWING:23

@prologic@twtxt.net
Temme about it! 🤪

@prologic@twtxt.net

No, it would be sufficient to skip avatar discovery when metadata does contain an avatar.

**

🧮 USERS:3 FEEDS:6 TWTS:215 BLOGS:0 ARCHIVED:52195 CACHE:2122 FOLLOWERS:7 FOLLOWING:23

@prologic@twtxt.net
Thank you, that’s the correct one.

Still I have this in my logs (first access of “eleven” by yarnd):

ip.ip.ip.ip - - [21/Oct/2021:20:05:36 +0000] “GET /eleven.txt HTTP/2.0” 200 344 “-” “yarnd/0.2.0@46bea3f (Pod: twtxt.net Support: https://twtxt.net/support)”
ip.ip.ip.ip - - [21/Oct/2021:20:05:36 +0000] “HEAD /avatar.png HTTP/2.0” 200 0 “-” “yarnd/0.2.0@46bea3f (Pod: twtxt.net Support: https://twtxt.net/support)”

And I guess without avatar.png sitting there I would have seen even more requests like /eleven.txt/avatar.png.

I’ve copied stackeffect.png to avatar.png to make yarnd happy when accessing stackeffect.txt.

So in this setup yarnd fetched eleven.txt along with avatar.png which belongs to another twtxt. This feels buggy.

**

🧮 USERS:3 FEEDS:6 TWTS:214 BLOGS:0 ARCHIVED:51989 CACHE:2112 FOLLOWERS:7 FOLLOWING:23

@prologic@twtxt.net
Keep in mind that there are plenty of icons already there, it is a quite busy “neighborhood”.

@prologic@twtxt.net
Validating the mention will be consuming, no? I mean, right now it takes a bit when clicking on the nick of an external user. Also, discovery occurs mostly by mentioning, yes? It seems a hard problem to solve.

@darch@twtxt.net
It will only use the nick of the person to whom you are replying, no the occasional never ending chain link of nicks. 😄

@prologic@twtxt.net
Kind of a pickle. I would say, if the user isn’t following the feed, then @something and @something@example.com doesn’t get linked.

@movq@www.uninformativ.de

We should be able to remove those subject hashtags, they’re just noise.

Yes! I would say they are not even needed on the web UI. You click conversations, and that’s done by Yarn. No need for humans to see it.

FOLLOW: @xuu@txt.sour.is from @quark@ferengi.one using jenny/latest

@prologic@twtxt.net
Yeah, it is kind of rubbish. 😬

@movq@www.uninformativ.de
Aha! Cool! Not just deleting, but proceeding as if the twt is going to be send. If I :q! on vi it will add an empty line. If, instead, I go :x like I normally do, it works as you said—and as I wanted it. Thanks!

@movq@www.uninformativ.de OK, I am on request/question asking mode today. 😋 How do you cancel a twt, or a reply to a twt? Say I hit my reply, and then I change my mind? Right now, even exiting vi is creating an empty line on my twtxt.txt. Is there an obvious way to cancel a twt, reply, or fork that I am missing?

@movq@www.uninformativ.de

If Subject contains the full twt, then you can skim over conversations just by reading those lines in mutt’s index pager

Yes, I do the same, true.

So I decided: Okay, let’s have mutt do it.

And Mutt does it well. I agree it was/is a good idea.

The subject lines are already “compressed”

I noticed, yes.

I am not sure why I asked to begin with; in retrospect, in was a silly request. Perhaps the OCD in me got triggered while viewing rich headers, on a specific twt, when I saw the huge subject line that is, otherwise, always hidden.

Anyway, don’t mind me, move along. 😂

@movq@www.uninformativ.de
I find sleeping while storming the best sleep, and we have hurricanes passing by, or near by, almost every year.

@prologic@twtxt.net
It is still too early, and too few of us. Give it some time, and your wife might revise her statement. 😂

**

🧮 USERS:3 FEEDS:6 TWTS:213 BLOGS:0 ARCHIVED:51744 CACHE:2131 FOLLOWERS:7 FOLLOWING:23

@prologic@twtxt.net
Sounds like a good plan. It is, of course, up to the Master Crafter. 😋

@prologic@twtxt.net
Jenny populates Mutt’s subject with the entire twt. That makes for very, very long subject lines.

@movq@www.uninformativ.de would it be possible to trim the subject to, say, 100 or 140 characters? Just the subject.

@lyse@lyse.isobeef.org
Indeed, it is a fairly common “disease”. 🤣

@darch@twtxt.net
I prefer darch’s one.

@stackeffect@twtxt.stackeffect.de

now Apache also announces content-type: text/plain; charset=utf-8

Well, that fixed things. 🥳

@quark@ferengi.one No client, those were created using date -Is and emacs. Off course all is UTF-8 encoded, but now Apache also announces content-type: text/plain; charset=utf-8

@prologic@twtxt.net Are you sure? The avatar file announced in my twtxt.txt was never fetched. Only non existing default avatars were fetched.

@lyse@lyse.isobeef.org
Bottomline, twtxt is a poor’s man email system. 🤣

@movq@www.uninformativ.de
No worries, I understood you perfectly. My reply was merely a commentary, because some here—specially the youth, and I have a 20 years old son—think that the vaccine makes the 100% impervious, and thus behave pretty stupidly.

I am the one in charge of bringing food, and helping the elderly in the family, so I take super extra precautions… for their sake.

@movq@www.uninformativ.de
I still worry, perhaps a little less. But I still take precautions. For me, and for others. I mean, you might have a bullet proof vest, but even so, would you actively seek to get shot?

@eldersnake@yarn.andrewjvpowell.com
Google or (insert your favourite search engine here) have never let me down. Also, Youtube has repair guides, and HOWTOs for just about anything, and everything.

@stigatle@twtxt.net
I really do not understand anyone not willing to get vaccinated. It is just plain stupid.

**

🧮 USERS:3 FEEDS:6 TWTS:212 BLOGS:0 ARCHIVED:51483 CACHE:2109 FOLLOWERS:7 FOLLOWING:23

@stackeffect@twtxt.stackeffect.de
I am seeing this characters on your twts: )?â\200¨â\200¨. Which client are you using?

@movq@www.uninformativ.de What I would really like to see if jenny could use HTTP range requests to fetch only new content.

E.g. it could refetch only last twtext line of last request to make sure it starts off at correct position.

I guess there are twtxt files that only grow, then this will save a lot bandwidth over time.

For twtxt files that “forget” older content this situation would be detected and as a fallback the whole twtxt file could then be fetched.

@movq@www.uninformativ.de
With those two (Message-ID, and In-Reply-To) the hashing could become superfluous, and no longer needed. I would vote for that!

@eldersnake@yarn.andrewjvpowell.com Maybe they are just lurking (and learning)?

;-)

@prologic@twtxt.net I would like to see “header” lines in twtxt.txt parsed.

Personally I started looking at some twtxt files with curl and saw information about avatar images.

I assumed that to be sort of standard and mentioned my avatar image in my stackeffect.txt. But it was not “avatar.png”.

Later I saw in logfiles that the info was totally ignored and instead several “avatar.png” locations were tried by the pulling side.

When information in “header” of twtxt file were respected one could easily change avatar file to one with a new filename and there would be no caching problem.

@movq@www.uninformativ.de

and the little cricket story stays there forever.

🤣🤣🤣

@movq@www.uninformativ.de
I replied to the one he originally sent (and later edited, so it was deleted). That’s probably what happened.