@bender@twtxt.net I’m using both machines in English.

Checked my locale and it spits out:

LANG=en_US.UTF-8
LC_CTYPE=“en_US.UTF-8”
LC_NUMERIC=“en_US.UTF-8”
LC_TIME=“en_US.UTF-8”
LC_COLLATE=“en_US.UTF-8”
LC_MONETARY=“en_US.UTF-8”
LC_MESSAGES=“en_US.UTF-8”
LC_PAPER=“en_US.UTF-8”
LC_NAME=“en_US.UTF-8”
LC_ADDRESS=“en_US.UTF-8”
LC_TELEPHONE=“en_US.UTF-8”
LC_MEASUREMENT=“en_US.UTF-8”
LC_IDENTIFICATION=“en_US.UTF-8”
LC_ALL=

🤷🏽 … and that only happens when vi, vim or nvim are launched by Jenny to compose a twt.

@prologic@twtxt.net it actually does!

But I broke something trying to get rid of the random characters showing on my twts as mentioned here #k7tcqwq.
I taught it was as easy as swapping the ‘\u2028’ in jenny’s new_twt_from_file function but there’s a reason I’m not a developer (yet) 😅

It kinda got rid of them in a way but broke the new lines in the process. So I put things back the way the were till I figure out something else.

OK time to put this to the test, I ended up setting my $VISUAL env
{-here-} variable, so that jenny can launch neovim instead of plain old vi like
{-here-} it is instructed in the code. But as you can see, I still get these
{-here-} wired new lines every ~70th character (marked them with {-here-})

Thanks again @movq@www.uninformativ.de !! I have figured things out and set up Jenny and Vim completion following your blog post! Cheers!

Hello Jenny!

I am back on twtxt for now. I am using twtwt client. Don’t think that it does replies so I should try jenny with mutt again.

👋 Q: How do we feel about forking the Twtxt spec into what we love and use today in Yarn.social in yarnd, tt, jenny, twtr and other clients? 🤔 Thinking about (and talking with @xuu@txt.sour.is on IRC) about the possibility of rewriting a completely new spec (no extensions). Proposed name yarn.txt or “Yarn”. Compatibility would remain with Twtxt in the sense that we wouldn’t break anything per se, but we’d divorce ourselves from Twtxt and be free to improve based on the needs of the community and not the ideals of those that don’t use, contribute in the first place or fixate on nostalgia (which doesn’t really help anyone).

@movq@www.uninformativ.de, well, yes, that has always been the case. Not just on jenny, but on Yarn. I can’t follow everything, and everyone. To see whether is a reply, a simple h on mutt shows the headers, and there you have it. That is not too convoluted, is it? I mean, if you really want to know–but why?–it is a simple key press. If I don’t see a context on something as obvious as the example you used, it is simply a reply to someone I don’t follow, and pretty much ignore. End of story. 😂

Right now I have to setup jenny for my timeline. Just added myself to the Registry so that part is done.

@benk@kwiecien.us I am using jenny (we chatted a bit on IRC earlier today). I have been using it for over five months now, I think. It is truly a joy to use, specially because you can use the power of Mutt/NeoMutt to read your twts.

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

@fastidious@arrakis.netbros.com

I hit RETURN after the subject, and nick […]

I shows fine on jenny. Let’s see how Yarn renders mine above.

Not to boast, but jenny has never failed me 😂. It is so neat, powerful, and streamlined, not even funny! Thank you very much, @movq@www.uninformativ.de for it! 💛

@prologic@twtxt.net
Awesome! Hope he will reply as fast as he did with me. And yes about the noise and length. Not an issue on jenny, or my own pod (I have it set to 2048, I think), but yes, ephemeral is right.

@jlj@twt.nfld.uk
Yup, jenny. She is so cool! 😋

@lyse@lyse.isobeef.org

👀 jenny, you say 👀

😁 cc @movq

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

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

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

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

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

@movq@www.uninformativ.de Goryon parsing is broken. Yarn shows it as I see it on jenny. Exactly the same.

@movq@www.uninformativ.de To clarify, Markdown is just text. 😊 I can do bolding, link things, and if single return multilines ever comes to jenny, I would be able to do bulleted and numbered lists.

The only things—that I know of—that doesn’t work is “> “, but I can use “>”, like so:

D’oh!

So, jenny allows me to write Markdown almost just fine!

Boy, do I love jenny/latest, and Neomutt! 😊

https://pasteboard.co/CDMQJYvWuYtY.png

Only thing jenny is missing, to be completely happy, @movq@www.uninformativ.de already knows about. 🙈

@movq@www.uninformativ.de This is my env, on language:

LANGUAGE=en_US.UTF-8

LANG=en_US.UTF-8

LC_ALL=en_US.UTF-8

I had to explicitly set it on the cron job to make jenny work.

@quark@ferengi.one If so, @movq@www.uninformativ.de, not quite https://www.uninformativ.de/git/jenny/commit/4a02eeec58317107c07e759733312d168e319f17.html#h0-0-5... Markdown needs single new lines for many things. Bulleted, numbered, code, etc. need them.

@movq@www.uninformativ.de I am getting this when I run it on cron (extra lines in between becuase otherwise jenny will make them a mash):

Traceback (most recent call last):

File “/home/quark/jenny/jenny”, line 565, in

if not retrieve_all(config):

File “/home/quark/jenny/jenny”, line 373, in retrieve_all

refresh_self(config)

File “/home/quark/jenny/jenny”, line 294, in refresh_self

process_feed(config, config[‘self_nick’], config[‘self_url’], content)

File “/home/quark/jenny/jenny”, line 280, in process_feed

fp.write(mail_body)

File “/usr/lib/python3.8/encodings/iso8859_15.py”, line 19, in encode

return codecs.charmap_encode(input,self.errors,encoding_table)[0]

UnicodeEncodeError: ‘charmap’ codec can’t encode character ‘\U0001f4e3’ in position 31: character maps to

@quark@ferengi.one By the way, you reply did not showed as a reply to a conversation on jenny this time. I wonder is something broke with the latest changes.

How would jenny handle multiline twts? Let’s find out! - One - Two - Three And: 1. One 2. Two 3. Three

@quark@twtxt.netbros.com I have removed the cron job, and added jenny -f to the small script that starts mutt with the .muttrc-jenny file. That way when I open, it refresh the feed before. Let’s see how it goes.

Seeing repeated twts again. Only thing I am doing different is running jenny every 5 minutes on a cron job. I really don’t know what to think.

@movq@www.uninformativ.de I got it! I had jenny under my ~/.local/bin/, and didn’t realised the one on the repo changed. D’oh! I am symlinking it now, so this doesn’t happen again. I love autocomplete!

@movq@www.uninformativ.de I did a git pull but that isn’t pulling jenny-posting.eml. Am I missing something?

@movq@www.uninformativ.de I noticed that if I ran jenny -f on a cron job, and kept mutt open, messages will get duplicated (same message, time, different message-id). I run it now on a small script before opening mutt.

@movq@www.uninformativ.de Ah, I see. I mean, it is not biggie, as normally I just reply to people, so that part works beautifully. A vi/vim script would work, but it is not universal. What if I use joe, or Emacs, or nano? Meh, jenny is awesome as is, thank you for it! ☺️

I need someone with a nice, and clean twtxt.txt feed. One that doesn’t include much–if any–images, and in which twts have more content. Just looking to see how formatting is handled in jenny and how to tweak it to my liking.

I might have figure out what was causing duplicated entries here. I think running jenny -f while mutt is open was causing it. I have disabled the cron job, and it doesn’t seem to be happening anymore. Let’s see how accurate my theory is. 😂

@movq@www.uninformativ.de is there a better way to mention others while using jenny?

❓ How do I mention someone while using jenny? I wonder if I have to use the whole @nick@nick… 🤔

@movq trying your jenny/latest. I am loving it so far!

Another one from jenny (why don’t you love me Jenny?!)

This is a new twtxt from jenny.

This is a test from jenny.