**

🧮 USERS:3 FEEDS:6 TWTS:240 BLOGS:0 ARCHIVED:58477 CACHE:2205 FOLLOWERS:7 FOLLOWING:23

@jlj@twt.nfld.uk Ooh fantastic. I love shots like this!

🧮 USERS:1 FEEDS:6 TWTS:688 ARCHIVED:125695 CACHE:12698 FOLLOWERS:25 FOLLOWING:49

🧮 USERS:1 FEEDS:2 TWTS:41 ARCHIVED:10607 CACHE:768 FOLLOWERS:9 FOLLOWING:12

**

🧮 USERS:3 FEEDS:6 TWTS:239 BLOGS:0 ARCHIVED:58235 CACHE:2177 FOLLOWERS:7 FOLLOWING:23

🧮 USERS:1 FEEDS:6 TWTS:676 ARCHIVED:125180 CACHE:10027 FOLLOWERS:25 FOLLOWING:46

🧮 USERS:1 FEEDS:2 TWTS:40 ARCHIVED:10383 CACHE:700 FOLLOWERS:9 FOLLOWING:12

**

🧮 USERS:3 FEEDS:6 TWTS:238 BLOGS:0 ARCHIVED:57986 CACHE:2166 FOLLOWERS:7 FOLLOWING:23

🧮 USERS:1 FEEDS:6 TWTS:668 ARCHIVED:124723 CACHE:13955 FOLLOWERS:25 FOLLOWING:46

🧮 USERS:1 FEEDS:2 TWTS:35 ARCHIVED:10220 CACHE:650 FOLLOWERS:8 FOLLOWING:12

**

🧮 USERS:3 FEEDS:6 TWTS:237 BLOGS:0 ARCHIVED:57505 CACHE:2082 FOLLOWERS:7 FOLLOWING:23

🧮 USERS:1 FEEDS:6 TWTS:662 ARCHIVED:124594 CACHE:13671 FOLLOWERS:24 FOLLOWING:45

🧮 USERS:1 FEEDS:2 TWTS:31 ARCHIVED:8745 CACHE:747 FOLLOWERS:8 FOLLOWING:10

@jlj@twt.nfld.uk Lol! Fantastic that your grandma has been able to live to that age! My grandfather made it to 96, quite healthy and happy, and actually walking around by himself until the end. Best wishes of health!

**

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

🧮 USERS:1 FEEDS:6 TWTS:661 ARCHIVED:124463 CACHE:12661 FOLLOWERS:24 FOLLOWING:45

🧮 USERS:1 FEEDS:2 TWTS:27 ARCHIVED:8654 CACHE:720 FOLLOWERS:8 FOLLOWING:10

**

🧮 USERS:3 FEEDS:6 TWTS:235 BLOGS:0 ARCHIVED:57056 CACHE:2114 FOLLOWERS:7 FOLLOWING:23

🧮 USERS:1 FEEDS:6 TWTS:660 ARCHIVED:124286 CACHE:10259 FOLLOWERS:24 FOLLOWING:45

🧮 USERS:1 FEEDS:2 TWTS:25 ARCHIVED:8268 CACHE:685 FOLLOWERS:8 FOLLOWING:9

**

🧮 USERS:3 FEEDS:6 TWTS:234 BLOGS:0 ARCHIVED:56804 CACHE:2094 FOLLOWERS:7 FOLLOWING:23

🧮 USERS:1 FEEDS:6 TWTS:657 ARCHIVED:124059 CACHE:8773 FOLLOWERS:23 FOLLOWING:45

🧮 USERS:1 FEEDS:2 TWTS:24 ARCHIVED:8158 CACHE:641 FOLLOWERS:8 FOLLOWING:9

@movq@www.uninformativ.de i believe the delete of any twt was a tech limitation with retwt parser not knowing where in the file a twt came from. lextwt tracks the bytes in file where a twt was read from. which could be used to delete a twt from file.. in theory.

I am in the camp of wishing i could delete arbitrary twts.

**

🧮 USERS:3 FEEDS:6 TWTS:233 BLOGS:0 ARCHIVED:56550 CACHE:2066 FOLLOWERS:7 FOLLOWING:23

🧮 USERS:1 FEEDS:6 TWTS:651 ARCHIVED:123454 CACHE:6499 FOLLOWERS:23 FOLLOWING:45

🧮 USERS:1 FEEDS:2 TWTS:16 ARCHIVED:6605 CACHE:541 FOLLOWERS:5 FOLLOWING:8

**

🧮 USERS:3 FEEDS:6 TWTS:232 BLOGS:0 ARCHIVED:56318 CACHE:2033 FOLLOWERS:7 FOLLOWING:23

🧮 USERS:1 FEEDS:6 TWTS:44582 ARCHIVED:122836 CACHE:10043 FOLLOWERS:23 FOLLOWING:45

@movq@www.uninformativ.de I don’t by your example (rebasing behaviour), sorry.

Writing a twt is more similiar to writing a commit message. Git does quite some checks to detect that nothing new was written and happily discards a commit if you just leave the editor. You don’t need any special action, just quit your editor. Git will take care for the rest.

But it’s OK as it is. I just didn’t expect that I have to select and delete all to discard a twt. So it’s C-x h C-w C-x C-c for me.

@darch@twtxt.net
Getting this when trying to use it:

error executing template timeline: template: timeline:131:43: executing "twt" at <formatForDateTime>: wrong number of args for formatForDateTime: want 2 got 1

**

🧮 USERS:3 FEEDS:6 TWTS:231 BLOGS:0 ARCHIVED:56056 CACHE:2038 FOLLOWERS:7 FOLLOWING:23

🧮 USERS:1 FEEDS:6 TWTS:44581 ARCHIVED:122474 CACHE:9991 FOLLOWERS:23 FOLLOWING:45

**

🧮 USERS:3 FEEDS:6 TWTS:230 BLOGS:0 ARCHIVED:55821 CACHE:2086 FOLLOWERS:7 FOLLOWING:23

🧮 USERS:1 FEEDS:6 TWTS:44580 ARCHIVED:122069 CACHE:11727 FOLLOWERS:23 FOLLOWING:45

@prologic@twtxt.net

I think something has caused my feed to be in a bad state and is now unpardable😥

I can read this on jenny, but the twt isn’t making it to my own pod. Something has gone really wrong, me thinks.

**

🧮 USERS:3 FEEDS:6 TWTS:229 BLOGS:0 ARCHIVED:55620 CACHE:2133 FOLLOWERS:7 FOLLOWING:23

🧮 USERS:1 FEEDS:6 TWTS:44578 ARCHIVED:120748 CACHE:10544 FOLLOWERS:23 FOLLOWING:45

**

🧮 USERS:3 FEEDS:6 TWTS:228 BLOGS:0 ARCHIVED:55428 CACHE:2134 FOLLOWERS:7 FOLLOWING:23

@prologic@twtxt.net Its not FormatText stripping out the lines. That formats with \n newlines so when unmarshalling it tries to parse the text and sees that as the end of twt. LiteralText keeps the newlines as \u2028

@prologic@twtxt.net make the text field twt.LiteralText() instead of twt.FormatText() and you should be good.

🧮 USERS:1 FEEDS:6 TWTS:44574 ARCHIVED:120245 CACHE:6137 FOLLOWERS:23 FOLLOWING:45

multi.

line.

twt..

multi
line
twt

@movq@www.uninformativ.de Your scenario would produce observed behaviour, agreed. On the other side I’m sure I’ve set very URL in lasttwt > 1630000000.0 (manually, in my editor).

But I can’t reproduce any weird behaviour right now. I’ve tried to “blackhole” twt.nfld.uk temporarily. That does not have any effect.

I’ve also tried to force twt.nfld.uk to deliver an empty twtxt. That does not have any effect either.

So I guess everything is fine with jenny.

I have wrapped jenny into some shell script to versionize ~/.cache/jenney. This way I have better data if anything unexprected is showing again.

**

🧮 USERS:3 FEEDS:6 TWTS:227 BLOGS:0 ARCHIVED:55228 CACHE:2173 FOLLOWERS:7 FOLLOWING:23

🧮 USERS:1 FEEDS:6 TWTS:44571 ARCHIVED:117826 CACHE:19109 FOLLOWERS:23 FOLLOWING:45

@movq@www.uninformativ.de Yes, it was exactly those twts. I don’t think I’ve managed to “match” the downtime while fetching twts. But even if I had, how can this lead to inserting old twts?

@movq@www.uninformativ.de Another feature request: sometimes I start writing a twt but then would like to discard it. It would be great if jeny could detect that I did not wrote (or saved) anything and then discards the twt instead of creating an “empty” one.