I’d also be very interested to hear what some other users of yarnd have to say, sadly there are only a handful of pods around that I’m aware of and/or that peer with my pod (twtxt.net) 😢

Image

Maybe Yarn.social/Twtxt has become boring or too niche? 🤔 Anyway cc @eldersnake@yarn.andrewjvpowell.com @xuu@txt.sour.is @stigatle@yarn.stigatle.no @abucci@anthony.buc.ci

Another feature as mentioned in #iq4rusa is using filters on the Timeline and/or Discover views. One of the most common “workflows” I use is to go to “Discover” and use the “Without replies” and “Hide my posts” filters to see if there’s anything new and interesting in my pod’s cache I haven’t seen before or maybe could reply to (or not).

Of course as I’ve locked down registrations on my pod anyway (have kept it locked down now for months) due to SPAM accounts and bots just creating rubbish accounts/feeds, this workflow may no longer be all that useful? hmmm 🧐

Hah 🤣 @dfaria@twtxt.net Your @dfaria.eu@dfaria.eu feed really does consume about >50% of a “Discover” search with filters “Without replies” and “Hide my posts”. 🤣

Image

36/2 = 18 at 25 Twts per page, that’s about ~72% of the search/view real estate you’re taking up! wow 🤩 – I’d be very interested to hear what ideas you have to improve this? Those search filters were created so you could sift through either your own Timeline or the Discover view easily.

One thing to be clear about here is that it was never my intention for a pod’s “front page” (Discover view when not logged in) to be any kind of “listing” or “advertising” or such. That was completely unintentional. If this is expected somehow, we should probably discuss that too more seriously and discuss its merits, and if it can be support, should be supported, or if there’s a different solution entirely? For example. there is the search engine which could show a global feed/timeline view, albeit the domain could be something different.

I’d like to hear some ideas that fix or improve the signal / noise ratio for all users and even benefits non-users (anonymous users just hitting a pod’s index page, which is the discover view)

There’s also a pod-level setting (admins) that control what the “Discover” (or front page if you’re not logged in) display:

Image

This is either:

• Local posts only (local to the pod)
  
• All posts in the pod’s cache

One of the problems I have with changing the way the “Discover” view works whilst at the same time keeping it “clean” (depending on who you talk to) is the behaviour between “Timeline” (what you follow explicitly) and “Discover” (a view into the pod’s cache). See attached, where I by default prefer a “collapsed” view (hiding replies). The default behaviour for Discover (no controls) is “everything”.

Image

The reason I bring this up is that part of my “workflow” has become to occasionally use the “Discover” view to see if I’ve missed any “in-between” replies that often happen, find new interesting folks to follow and/or interact with, etc.

Changing this to anything but the current behaviour would break this flow for me 😢

@bender@twtxt.net Nah feeling pretty rubbish today actually 😢

@prologic@twtxt.net woah, such a good life! 🙈

@marcorocco@roccodrom.de What are you updating and changing out in your bathroom? 🤔 We probably need to update our bathroom too, the spa pipes are getting a bit uggh 😅

@aelaraji@aelaraji.com I just woke up fianally 🤣 It’s 12:45pm here (midday)

@aelaraji@aelaraji.com here as in, here? It’s a quarter to 22:00 here, and after a rather tiresome day I am trying to rest, while alternating with folding freshly washed and dried clothes. Quiet indeed! 😅

It’s kinda quiet in here today!

renovating the bathroom on the upper floor

@bender@twtxt.net Haha I know and @lyse@lyse.isobeef.org is awesome🤣

To expand on this, Lyse is the only person I know to send in code contributions with a full test suite. That’s awesome.

Looks like there’s not a lot of fancy magical stuff:

• https://komh.github.io/os2books/progfaq/112_L2_Whatisthebestwaytoco.html
  
• https://komh.github.io/os2books/progfaq/111_L2_Whatisthebestwaytoco.html
  

There is, however, a DosKillThread() function, which, as far as I know, does not exist on POSIX. 🤔 You can only send a signal to a POSIX thread and then it’ll hopefully end some day, right?

Killing threads is probably a bad idea, though. Who knows which state it’ll leave behind. It’s not like a process which will be properly cleaned up by the OS.

I think I’ll leave it as is. 🙂

@prologic@twtxt.net isn’t it evident? It surprises me you need to ask! 😂

@dfaria@twtxt.net plunk.

@dfaria@twtxt.net you are not who you say you are, you are who you show to be. You demonstrated a certain lack of levelled engagement, and sound reasoning; you were borderline hysterical. All qualities everyone should have, even more so someone who has chosen the teaching path.

This is not a train terminal. No need to give so many warnings about leaving, so many “bye-byes”. If that’s your intention, just leave.

@dfaria@twtxt.net Appreciate this 👌 Right now the algorithm is quite dumb – and I’d also hate to develop any algorithm that abuses any data from users. So definately needs to be things like:

• one post per day per domain
  
• or latest post per domain
  

etc/./

@sorenpeter@darch.dk Yup! Some good simple ideas there 👌

@sorenpeter@darch.dk Thanks for your positivity and support ! 🤗 This is exaxrly spot on, however I also realize getting things “right” is actually quite hard 😅

@lyse@lyse.isobeef.org How much emphasis do you place on test coverage?

To be fair cleaning up “noise” is quite hard to do. Obciously all the 1-way Mastodon feeds were easy because there’s just no way to interact with them!

@dfaria@twtxt.net That’s fair. Also removed the block on your domain btw.

Executing all tests of the online registrations I’m building for the scouts takes now 70 seconds. Initializing a new SQLite database in RAM and creating all the tables for each test case sums up and takes its time. During development cycles I more often resort to the -run flag for go test to specify only one area of tests to be executed. Much more fun this way to quickly go back to writing code.

At least the service layer line coverage is a whopping 99.5%, branch coverage is 93.3% (the latter could still be bumped slightly). However, only 17.6% lines of the web layer are covered (I definitely should increase this by a lot). This still good test base, if I say so myself, came in extremely handy a lot of times when refactoring stuff. Esp. the service layer changed, web not so much. It slows development down quite a lot, that’s for sure. I reckon it’s easily five to ten times more effort to come up with useful tests than writing productive code, probably even more. I’m bad at guessing. But the confidence of not breaking stuff is sooo much more valuable. The tests certainly paid off in the past, zero doubt about that.

It takes a lot of discipline to first write all the tests in the service layer before doing the web stuff and finally see it in action and play around. It’s funny that I always have to force myself to do so, but in the end, I’m always happy to have done it exactly like that. It once again worked out very smoothely that way. But something inside me wants to fast forward. I wonder if that irrational part eventually fades away.

Having a code coverage report does make a night a day difference. It actually turns writing tests into a fun game for me. The older I get, the more I do enjoy writing tests. Rest assured, producing productive code is still cooler. :-)

I’m also sooo happy about vim-go. I can’t believe how much that sped up and boosted my development process.

Whoops, 57 minutes later, this message turned out much more elaborated that I initially envisioned. Oh well. ;-)

@bender@twtxt.net You don’t know me and you’re already making arbitrary judgments about me. I only got upset because they didn’t warn me that they were going to block my domain. Nobody likes being canceled without warning. There were other civilized ways of letting me know that there was a problem with my domain instead of blocking it unilaterally. Bye-bye!

@bender@twtxt.net I guess all I can do is unblock the domain and sit down and rethink the “Discover” view’s design and behavior? hmmm 🧐 Alternatively, build a new yarnd 2.0? as a single-user pod only?

@bender@twtxt.net Yeah I could get behind that. Define minimalistic though? What features (if any) would we drop? Would it be mobile-first or desktop-first?

@bender@twtxt.net I couldn’t agree more 🤣

@bender@twtxt.net I never see problems on my end, so I suspect this has to be Cloudflare doing this occasionally. I’ll have to poke around there again. At least I have a close enough timestamp :D Maybe message me your IP and approximate timestamp?

Image

This happens more often than I would like. 😢

@prologic@twtxt.net now, the mention of multiuser pods brought an idea. What if you design, and code, single user pods that are extremely lean (extremely low processor, memory, and storage footprint), and brutally minimalist?

@prologic@twtxt.net I think trying to please everyone is a mistake. 😈

@prologic@twtxt.net “let it go, Indiana”. Evidently Assistant Professor Faria can’t—or doesn’t want to—engage in civil discourse. Using Her Majesty’s proper: fuck it!

I think multi-user pods were a mistake.

@dfaria@twtxt.net Sorry this has pissed you off so much (unintentional) – Also why the irrational outburst?! 😱 That’s no way to have discourse or help improve anything 🤦‍♂️

If you have ideas for improvement we’re all ears 👂

@dfaria@twtxt.net Cancelling is a strong word. I’d you follow your other feed yourself it’s still visible to you!

This whole exercise just reenforces that the idea of the “Discover” view was and is a terrible idea. 😢

I think I’ll be doing this again:

https://dataswamp.org/~solene/2022-07-01-oldcomputerchallenge-v2-rtc.html

The source code of “DOS 4” was released:

https://github.com/microsoft/MS-DOS/tree/main/v4.0

Not without issues:

https://www.os2museum.com/wp/how-not-to-release-historic-source-code/

(Hence “DOS 4” in quotes, is it 4.00 or 4.01? Probably the latter.)

More DOS 4 history:

https://www.os2museum.com/wp/dos/dos-4-0/

Well, there was one subtle bug: jenny did not fetch archived twts from your own feed (only from other people). I just happened to wipe all twts/cache from my disk, so I noticed that all my old stuff was missing. It’s a corner case, but it’ll be fixed in the next release.

@osnews@feeds.twtxt.net

We’ll have to see how this policy will be implemented, but I like that Gentoo is willing to take a stand.

Me too😅

Gentoo bands use of “AI” tools
Gentoo, the venerable Linux distribution which in my headcanon I describe as ‘classy’, has banned any use of “AI”. A proposal by Gentoo Council member Michał Górny from February of this year banning it use has been unanimously accepted by the Gentoo Council. The new policy reads: It is expressly forbidden to contribute to Gentoo any content that has been created with the assistance of Natural Language Processing artificial intelligence tools. This motion can be revisited, … ⌘ Read more

I just found out about last(1) and lastb(1) while wondering about /var/log/wtmp. This can come in handy! The filenames remain a bit mysterious: https://unix.stackexchange.com/questions/127211/why-are-utmp-wtmp-and-btmp-called-as-they-are

Je découvre Kalandra à cause de <@fredg@pouet.chapril.org>, j’aime beaucoup : https://invidious.fdn.fr/watch?v=Vcpe23dG-jk

@movq@www.uninformativ.de Oh wow! Better not mess up with that responsibility. :-)

@movq@www.uninformativ.de @prologic@twtxt.net Hahaha, thanks for sharing, @bender@twtxt.net! :-D

IBM has realized it’s cheaper to buy Hashicorp than to buy Vault licenses

@movq@www.uninformativ.de Yeah, things like that can really make one ill.

@movq@www.uninformativ.de I can’t think of a single one. Pretty lucky so far.

@bender@twtxt.net Holy cow, congrats on that title. I do have plugged in the more important equipment in a power strip with surge protection. The weird thing was, that only one of the monitors went black for a second. The other one (both are behind surge protection) remained operational the entire time. Maybe EMP? It was closer to the window than the other one.