@movq@www.uninformativ.de Interesting. Never came across the term presentation manager in my life, but I also never used OS/2. :-)

Yeah, stopping the scanning thread is more a learning experience than a necessity. The scanning message is hardly visible in your videos. It’s already very quick.

I’m with you, @bender@twtxt.net, weekends are way too short.

Recuperei o historico de mensagems no meu antigo MicroBlog, sera que funcionou?

@aelaraji@aelaraji.com I’ve never had a use for Syncthing but I hope I get one at some point so I can see how it works. Do three-way merges work on Keepass database files?

Agora mudei o arquivo de bd do Twtxt para a Public_Html

Ola esse é meu primeiro input do Blog nesse servidor

I have been up, and ready to go for hours. Partner is still in bed. She takes such a long time to wake up on weekends! Past noon already, and we need to get food for the elders, and come back to tidy up things to get ready for the next weekly cycle.

Ugh! Where did the weekend go?!

@dfaria well, your “original twtxt” is an example of anything, but social. It is more like an echo chamber. If I am going to follow someone, I seek interaction. Language isn’t a barrier, lack of engagement is.

@prologic@twtxt.net Your position doesn’t make any sense: it’s closing down and arbitrarily limiting the use of the Twtxt protocol. One more reason not to use https://twtxt.net/

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

Oh, you finally did implement multithreading, @movq@www.uninformativ.de. Cool, cool. :-) https://www.uninformativ.de/blog/postings/2024-04-21/0/POSTING-en.html Just in case you want to keep working on PMdusage, my suggestion for a future upgrade is to make the scan abortable. 8-) By the way, what does “PM” in “PMdusage” stand for?

Always great to see that bugs are quickly fixed.

There’s a tiny typo in the second to last paragraph: “Windows NT is something that I had no contact with…”

@sorenpeter@darch.dk Good points 👌

@lyse@lyse.isobeef.org This ☝️

@lyse@lyse.isobeef.org Thanks! 🙇‍♂️

@mckinley@mckinley.cc Haha, interesting read.

@aelaraji@aelaraji.com Nice, I can confirm it’s now fixed. I reckon the Content-Type: text/plain; charset=utf-8 did the trick. Something in the twtxt client must have incorrectly guessed ISO-8859-1 or something along those lines when there was no charset advertised in the response header.

@prologic@twtxt.net @bender@twtxt.net Agreed, looking heaps better. <3

The wording can be more subtle like “This feed have not seen much activity within the last year” and maybe adding a UI like I did in timeline showing time ago for all feeds

I agree that it good to clean up the Mastodon re-feeds, but it should also be okay for anyone to spin up a twtxt.txt just for syndicating they stuff from blog or what ever.

The “not receiving replies” could partly be fixed by implementing a working webmentions for twtxt.txt

@mckinley Do you have an alternate proposal? What we want to avoid really (if possible) is the idea of “1-ay posting” or “posting to the void”. As an obvious example, the idea of syncing your Mastoon toots to Twtxt twts that you never see replies to is well umm just silly 🤣 and thus creates unwanted noise as it’s just like talking to a “brick wall” 😥

@rrraksamam@twtxt.net You must live in the southern hemisphere? 🤔 It doesn’t ever snow here in Brisbane 🤣

I use KeePassXC because I really only use one device. I imagine it would be challenging to rsync the database around if I needed my passwords on more machines. It’s probably fine if you’re deliberate enough, but I don’t think it would take long before I’d lose a password by editing an outdated version of the repository and overwriting the main copy.

I like the simple architecture of Pass, and it would indeed lend itself well to a Git repository, but I don’t like that service names are visible on the filesystem. pass-tomb might mitigate this somewhat but it seems messy and I don’t know if it would work with Git without compromising the security of the tomb.

What’s so good about Bitwarden? Everyone seems to love it. I like that it can be self-hosted. I certainly wouldn’t want a third party in control of my password database.

@prologic@twtxt.net This seems like it would drive a wedge between Yarn.social and the people on regular old twtxt.

Apparently it’s snowing in some places now