… Or, maybe (most likely) I don’t know what I’m talking
about.

Anyway, let’s get … Twtn’? Twtxting? Tw… /me will shut up! 😶

@mckinley@twtxt.net I can’t say for sure. I didn’t even know how three-way merges work till I looked it up. I guess it’s more of git thing that would prove useful in the case of using passwordstore/pass.
As for Keepass, all I do is syncing it’s database file across devices using syncting. Never felt the need to try anything else.

I guess it is safe enough for my use case, with Backup database before saving on and custom Backup Path Placeholders as Backup plan in case of an Eff up.

I might have found the actual source of my problem.

Jenny uses an .eml file when composing a twt …
and vim kinda auto formats it and inserts in those line breaks every ~70 character.

Then, I stumbled upon this link where Where someone reports that saving a .eml into a .txt might… corrupt the data?

@lyse@lyse.isobeef.org Awesome! glad to hear that!

@mckinley@twtxt.net You definitely have got a point!

It is kind of a hassle to keep things in sync and NOT eff up.
It happened to me before but I was lucky enough to have backups elsewhere.
But, now I kind of have a workflow to avoid data loss while benefiting from both tools.

P.S: my bad, I meant Syncthing earlier on my original replay instead of Rsync. 🫠

@bender@twtxt.net can’t say for sure, but I believe it’s a JetBrainsMono Nerd Font … I’m kind of the set it and forget it type. but will try and check later to be sure.

@prologic@twtxt.net sure! Give me a couple of minutes to set things up.
Also, you can check the charset again, I did set it up even tho I do observe the problem in my twtxt.txt file on my local machine way before doing scp to the remote one. They show up when I use bat but not when I cat the file nor on neomut.

@prologic@twtxt.net Thank
you! and here’s a twt with the said random characters, since I’ve been
cleaning them up manually, earlier before scp-ing my twtxt.txt file. And
maybe a screenshot of how things look in my editor?

Image

Those new lines are added automatically as I type (except for the ones
after the screenshot.

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

@shreyan@twtxt.net ever tried KeepassXC or Pass/Password Store ? They are worth giving a try … Then you can keep your KeepassXD database in synch across your devices with (NOT /R/s/y/n/c) I meant Syncthing or git in the case Pass (using a git repo in within your local network of course) 👍🏼(edited)

borked it! no new lines for me 😂👍🏻

Wait a second! I did get the new line in my editor but the s dissapeared from the twtxt.txt file. let’s add in a new line just to make sure I did not break anything. 😂👍

lets test this now yadi yadi yada a gray fox jumped from I don’t know what over something or someone! … nope! still does the thing …

Now I’m about to do something that May…be… stupid, I’m no dev but
I’ll try and replace the U+201 in the script with a space and see what
happens …

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-})

… or is it vi? 🤔

yep, it did! And it’s definitely something with vim.

@lyse@lyse.isobeef.org Thank you! and sorry, I’ve just noticed your twt. About the funky characters, it’s probably something off with my editor, I’ve just ssh-ed from mobile and checked my .txt file, it looked like that when I cat the file but normal on neoutt. I’ll try and see what’s the deal first thing in the morning. (/me wondering if the same thing would happen with this twt)

Down the rabbit hole we go… Wee !!

@prologic@twtxt.net Haha! I’m still figuring my way around but Thank you!

@movq@www.uninformativ.de yeah, it seems like it. But I don’t mind using neomutt to go through my feed, it feel like a huge upgrade compared to the usual pager 😄

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

Test!

Hello Jenny!

Ok! third one is the charm… right? right!!?

Aaaaand another one?

Testing! Testing! One two FREEE!!

I wonder if anyone got that as a replay 🥲 I tried and copied thread’s tag from twtxt.net

Oh! thank you @movq@www.uninformativ.de and @bender@twtxt.net ! I’ve noticed your replays by chance checking my logs 😊

Oh, nevermind… it did! I’ve just checked my twtxt.txt file. Now I have to figure out replays 🫤

Nope! it didn’t work… I still have some digging to do.

I’m still figuring out interactions mechanics on Twtxt, for example the at symbol is sufficient to mention someone you follow I guess, like @twtxt@buckket.org when using the twtwt cli. is that implemented in the twtxt cli as well? it wouldn’t heart to try

Good! I guess I’m done setting up my Twtxt. I’ll be juggling between the official CLI and Twixter, although I already have a favorite.

At last! my Twtxt feed is up and running and I can post to it from a remote client! Yey!

Hello Twtxters!