**
🧮 USERS:3 FEEDS:6 TWTS:220 BLOGS:0 ARCHIVED:53495 CACHE:2116 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:220 BLOGS:0 ARCHIVED:53495 CACHE:2116 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
🧮 USERS:1 FEEDS:6 TWTS:44557 BLOGS:3 ARCHIVED:106371 CACHE:15079 FOLLOWERS:23 FOLLOWING:44
**
🧮 USERS:3 FEEDS:6 TWTS:219 BLOGS:0 ARCHIVED:53234 CACHE:2064 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:219 BLOGS:0 ARCHIVED:53234 CACHE:2064 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
🧮 USERS:1 FEEDS:6 TWTS:44555 BLOGS:3 ARCHIVED:106018 CACHE:14922 FOLLOWERS:23 FOLLOWING:44
**
🧮 USERS:3 FEEDS:6 TWTS:218 BLOGS:0 ARCHIVED:52943 CACHE:2028 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:218 BLOGS:0 ARCHIVED:52943 CACHE:2028 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
🧮 USERS:1 FEEDS:6 TWTS:44554 BLOGS:3 ARCHIVED:105912 CACHE:14907 FOLLOWERS:23 FOLLOWING:44
D~d>1m and then fetched by !jenny -f. This brings back all deleted twts. Isn't lastmods used to skip older twts?
@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.
D~d>1m and then fetched by !jenny -f. This brings back all deleted twts. Isn't lastmods used to skip older twts?
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
**
🧮 USERS:3 FEEDS:6 TWTS:217 BLOGS:0 ARCHIVED:52648 CACHE:2015 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
🧮 USERS:1 FEEDS:6 TWTS:44553 BLOGS:3 ARCHIVED:105763 CACHE:14865 FOLLOWERS:23 FOLLOWING:44
**
🧮 USERS:3 FEEDS:6 TWTS:216 BLOGS:0 ARCHIVED:52412 CACHE:2110 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:216 BLOGS:0 ARCHIVED:52412 CACHE:2110 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
🧮 USERS:1 FEEDS:6 TWTS:44552 BLOGS:3 ARCHIVED:105647 CACHE:14845 FOLLOWERS:23 FOLLOWING:44
**
🧮 USERS:3 FEEDS:6 TWTS:215 BLOGS:0 ARCHIVED:52195 CACHE:2122 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:215 BLOGS:0 ARCHIVED:52195 CACHE:2122 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
🧮 USERS:1 FEEDS:6 TWTS:44551 BLOGS:3 ARCHIVED:105499 CACHE:14827 FOLLOWERS:23 FOLLOWING:44
**
🧮 USERS:3 FEEDS:6 TWTS:214 BLOGS:0 ARCHIVED:51989 CACHE:2112 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:214 BLOGS:0 ARCHIVED:51989 CACHE:2112 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
🧮 USERS:1 FEEDS:6 TWTS:44550 BLOGS:3 ARCHIVED:105434 CACHE:14813 FOLLOWERS:23 FOLLOWING:44
@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?
If
Subjectcontains 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. 😂
**
🧮 USERS:3 FEEDS:6 TWTS:213 BLOGS:0 ARCHIVED:51744 CACHE:2131 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:213 BLOGS:0 ARCHIVED:51744 CACHE:2131 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
@prologic@twtxt.net
Jenny populates Mutt’s subject with the entire twt. That makes for very, very long subject lines.
🧮 USERS:1 FEEDS:6 TWTS:44548 BLOGS:3 ARCHIVED:105327 CACHE:14831 FOLLOWERS:22 FOLLOWING:44
**
🧮 USERS:3 FEEDS:6 TWTS:212 BLOGS:0 ARCHIVED:51483 CACHE:2109 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:212 BLOGS:0 ARCHIVED:51483 CACHE:2109 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
🧮 USERS:1 FEEDS:6 TWTS:44547 BLOGS:3 ARCHIVED:105017 CACHE:14595 FOLLOWERS:22 FOLLOWING:44
@stackeffect@twtxt.stackeffect.de
I am seeing this characters on your twts: )?â\200¨â\200¨. Which client are you using?
@stigatle@twtxt.net
A twtxt client would be nice! Or a very simple cgi script to print twts to web nicely—not a second Yarn, just something to show twts in a pretty form on the web.
@movq@www.uninformativ.de
Fair enough, I will modify my cron job to match. When I come across edited twts, I just delete both knowing jenny will fetch the right one next iteration. I like keeping things tidy. 😊
@movq@www.uninformativ.de what is your cron job repeat time for jenny? Currently I have mine to every minute, and while it allows me to participate fairly quick on conversations it has some drawbacks: it captures every single edited twt, so I end up with seemingly the same twt, but not quite—as it has minor edits, etc. So, “repeats”. Perhaps setting cron to check every 5 minutes or so is best?
**
🧮 USERS:3 FEEDS:6 TWTS:211 BLOGS:0 ARCHIVED:51248 CACHE:2099 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:211 BLOGS:0 ARCHIVED:51248 CACHE:2099 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
Now, if there is going to be some sort of price, which for me equals to profit, then I will twt non-stop until I hit it! 🤣
🧮 USERS:1 FEEDS:6 TWTS:44546 BLOGS:3 ARCHIVED:104831 CACHE:14471 FOLLOWERS:22 FOLLOWING:44
@jlj@twt.nfld.uk
Just as jlj, that is exactly what I meant. Good point, Lyse!
Apple Event for 18 October 2021, 10:00 PDT, 13:00 EDT begins. Commentary will stream as replies to this twt. I might miss things here and there, as I will also be on a work meeting from 13:00 to 14:00 EDT.
**
🧮 USERS:3 FEEDS:6 TWTS:210 BLOGS:0 ARCHIVED:51012 CACHE:2089 FOLLOWERS:7 FOLLOWING:23
**
🧮 USERS:3 FEEDS:6 TWTS:210 BLOGS:0 ARCHIVED:51012 CACHE:2089 FOLLOWERS:7 FOLLOWING:23 ⌘ Read more
🧮 USERS:1 FEEDS:6 TWTS:44545 BLOGS:3 ARCHIVED:104759 CACHE:14454 FOLLOWERS:22 FOLLOWING:44
@jlj@twt.nfld.uk
While at it, fix this one too? You have me at netbros.com, but I am somewhere else. 😆
@jlj@twt.nfld.uk
Your avatar is healthy on your pod now. Still doesn’t show well on twtxt.net, but it is just a matter of time now (caching, etc.), it is all good. 🎉
🧮 USERS:1 FEEDS:6 TWTS:44543 BLOGS:3 ARCHIVED:104685 CACHE:14430 FOLLOWERS:21 FOLLOWING:44
I am noticing that Yarn doesn’t treat “outside” (that is, twts coming from a client other than Yarn) twts hashes right. Two examples:
There are many more, but those two will give you the gist. Yarn links the hash to the poster’s twtxt.txt, so conversation matching will not work.
🧮 USERS:1 FEEDS:6 TWTS:44542 BLOGS:3 ARCHIVED:104584 CACHE:14407 FOLLOWERS:21 FOLLOWING:44
@lyse@lyse.isobeef.org Unless you are stripping stuff on your twts, there is no much to implement. Things will be bold , italics , underlined , and so on, on a client that can render them. Since jenny uses Mutt, I can use my own regex in it to color them as I like. That’s pretty much it.
🧮 USERS:1 FEEDS:6 TWTS:44541 BLOGS:3 ARCHIVED:104519 CACHE:14401 FOLLOWERS:21 FOLLOWING:44
@movq@www.uninformativ.de But it makes sense, right? I spend way too much time trying to figure out who replied to whom. I treat twts replies as emails, pretty much.
🧮 USERS:1 FEEDS:6 TWTS:44540 BLOGS:3 ARCHIVED:102630 CACHE:13418 FOLLOWERS:21 FOLLOWING:44
@movq@www.uninformativ.de 12,342 twts, totalling 6.2 MB. Would deleting help, or will they come back? I guess there is one way to find out! 😄
@movq@www.uninformativ.de, how do you handle twts in Mutt? I mean, how do you organise, or manage the inmense amount that comes throught? Do you delete/trim? Move things to folders? Or simply keep that huge (12,000+ for me now) list?
@prologic@twtxt.net Excellent, nothing broke. I think what happened was you replied to a twt that I was in the process of editing.
🧮 USERS:1 FEEDS:6 TWTS:44539 BLOGS:3 ARCHIVED:102490 CACHE:13353 FOLLOWERS:21 FOLLOWING:44
🧮 USERS:1 FEEDS:6 TWTS:44537 BLOGS:3 ARCHIVED:102406 CACHE:13349 FOLLOWERS:20 FOLLOWING:44