ws very busy day at work today, now I’m home, watching TV and chilling. kids are out playing, Tonight Ill code or play some games.
Hope you all are having a nice day!
Hey @firstname.lastname@example.org 👋
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!
@email@example.com (#ifphkga) Nothing wrong with asking. 😊 I think I might actually implement more aggressive subject “compression”. We should be able to remove those subject hashtags, they’re just noise. 🤔
@firstname.lastname@example.org 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?
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. 😂
(#sojctqq) I also do genuinely think that Yarn.social is pretty hard to abuse and quite hard to create “noise” too ☺️
(#sojctqq) @email@example.com 💯 👌 @firstname.lastname@example.org may not yet appreciate this but the technical and design choices made here on Yarn.social and indeed built upon a very simple but extended Twtxt are very deliberate to all these points 🤗 Even such things as an active cache and archival process 😆 were deliberate !
(#sojctqq) [2 / 2]…made far worse by platforms such as Facebook etc using algorithms to encourage negativity and conflict.
I think communities such as the ones you find here have a massive advantage of not having those algorithms obviously, but also the nature of the platform (protocol?) is you kind of make your community around you. And the whole experience is more interpersonal (as much as can be in text exchanges) and full of less distractions. I could ramble on but you get it 😄
(#sojctqq) @email@example.com Seriously! @firstname.lastname@example.org is gonna get sick of me pinging him on every platform we share, thanking him, but… Well, I just love it! It’s on nfld.uk now, for cryin’ out loud! :-P Particularly because I spent quite a bit of time reading Hayek over the last few years and came to the conclusion that we really don’t share much of a worldview… How wrong I was!
(#sojctqq) Yeah I think behind a keyboard and monitor has made people act quite differently as a society towards each other. For example people will be rarely so radical or lean to such political extremes in person, but online is a different matter. I think also this grows exponentially on larger online spaces - the reason why as communities grow they tend to become more ‘noisy’ and what some may deem ‘toxic’. I think we’ve all seen that in some way or another, on those platforms [1⁄2]
I mean, part of that is being a small community of higher than average intelligence, of course… lol! ;-)
But I think you deserve lots of credit for building software that has time to reflect built in; I honestly think that’s hugely important, and I’m glad that we’ve preserved it through this rebranding / enhancing.
(#sojctqq) One thing my lovely wife pointed out to me this evening on the subject is how we’ve effectively built a way to have honest open conversations without riling each other up 👌
@email@example.com pointed me to this wonderful quote from Hayek that’s particularly relevant here too, I feel:
[On true, and false, individualism, one] might even say that the former is a product of an acute consciousness of the limitations of the individual mind which induces an attitude of humility toward the impersonal and anonymous social processes by which individuals help to create things greater than they know, while the latter is the product of an exaggerated belief in the powers of individual reason and of a consequent contempt for anything which has not been consciously designed by it or is not fully intelligible to it.
From Individualism and Economic Order, circa 1948. I wonder what he’d make of the Internet. :-P
(#sojctqq) @firstname.lastname@example.org I could not agree more 😁 I genuienly think so many of us have become too sensitive and judgmental 😥 Worse is this whole PC phase many parts of the world are going through 🤦♂️
From a chat on Matrix, where it seems it was one of my more coherent moments: 🤪
… Why can’t they just be individuals? Individuals with their own individual beliefs and their own individual reasons for having those beliefs…
And so just default to a stance of respect and courtesy. The fact is, most of your interactions with others will be very limited; approaching those encounters from a place of respect for the complexities of the human mind and an individual’s experiences and traumas costs you very little, typically.
To be human is to generalise, but that doesn’t mean you can’t push back against those tendencies.
Well, in the context of chat, it would be something like you’ve just done: don’t put words in my mouth, based on my avatar, nick, grammar, etc., and instead ask me to elaborate on points of potential confusion.
And don’t bring agendas to everything. Default to assuming that this is likely an interaction of hours, and people don’t change based on that, typically.
You’ll probably get more from interactions that you’re open to, but, be honest with yourself: if you aren’t up to that, because it isn’t easy, then just default to respect and courtesy, which isn’t difficult, and costs you little. And then excuse yourself, if they’re proper jerks. ;-)
(#dzzwcvq) @email@example.com Thanks for spinning this up btw and putting it through its paces! 🤗 You’ve reminded me I want to do a bit of work on that codebase now, I think I’m renaming it to “twtxtfeeds” or something like that… Open to suggestions for a better codename 🤣 But essentially I want to take advantage of the new Metadata spec 👌
(#ri6lq6a) How exactly is this a patent?! 🤦♂️ da fuq?! 😳 I hate patents 😂
Another storm is coming… ⛈
(#dzzwcvq) Just committed this:
* 914268a 2021-10-21 | Add a working docker-compose (HEAD -> master, origin/master) [James Mills]
This should hopefully get you going 👌
(#dzzwcvq) And a sample config just looks like:
$ cat config.yaml.sample --- root: ./feeds baseurl: / maxsize: 1048576 feeds: unexplained_mysteries: http://www.unexplained-mysteries.com/news/umnews.xml
Although this is also managed from the Web interface.
image: rss2twtxt:latest command: -s -c /config/config.yaml volumes: - feeds_config:/config - feeds:/feeds
(#ifphkga) Just for some more background: I wrote a StatusNet client years ago which worked very similar to jenny, with mutt as a frontend. That program did indeed truncate the subject lines – but it turned out to be a bit annoying in practice. It was always cut off a little bit too early. 🤣 So I eventually removed truncation altogether.
Subject contains the full twt, then you can skim over conversations just by reading those lines in mutt’s index pager. I often do that. On the other hand, if they’re truncated, then the question is: Where do you truncate them? 72, 100, 140, 200? Some people have wide terminals, others don’t. So I decided: Okay, let’s have mutt do it. 🙃 (Or you could make it a user option, but I like to avoid those, because you quickly end up with a ton of options and things get very hard to test, because I myself don’t use most of them.)
The subject lines are already “compressed”, btw. For example, a full mention like “@” gets compressed to just “@foo”. Maybe it’d be possible to expand on that idea, like also strip the hashtags of conversation grouping. 🤔
I like the way Hashicorp manage and generate their Release notes and Changelog. This is a nice way to do it, immutable changelog and kept alongside your Git commits with context behind every change, not just a (often) poorly worded commit message.