prologic

twtxt.net

"Problems are Solved by Method" 🇦🇺👨‍💻👨‍🦯🏹♔ 🏓⚯ 👨‍👩‍👧‍👧🛥 -- James Mills (operator of twtxt.net / creator of Yarn.social 🧶)

Recent twts from prologic
In-reply-to » 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".

Maybe some kind of option that when enabled will collapse multiple posts from the same feed and only show the top most recent one, with some kind of UI/UX that indicate “N more today…”?

⤋ Read More
In-reply-to » 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".

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

Download

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

⤋ Read More
In-reply-to » 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".

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 🧐

⤋ Read More

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”. 🤣

Download

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.

⤋ Read More
In-reply-to » 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".

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.

⤋ Read More
In-reply-to » 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".

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)

⤋ Read More
In-reply-to » 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".

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

Download

This is either:

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

⤋ Read More

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

Download

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 😢

⤋ Read More
In-reply-to » Been clearing out my pod a bit and blocking unwanted domains that are basically either a) just noise and/or b) are just 1-way (whose authors never reply or are otherwise unaware of the larger ecosystem)

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

⤋ Read More
In-reply-to » Been clearing out my pod a bit and blocking unwanted domains that are basically either a) just noise and/or b) are just 1-way (whose authors never reply or are otherwise unaware of the larger ecosystem)

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

⤋ Read More
In-reply-to » 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.

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

⤋ Read More
In-reply-to » @bender 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!

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!

⤋ Read More
In-reply-to » @dfaria 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 🤦‍♂️

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

⤋ Read More