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

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:

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

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 😢

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

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

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

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

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

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

@movq@www.uninformativ.de Haha 🤣 I saw this too and immediately thought

I have to stop using Terraform

🤣

@bender@twtxt.net Oh my 😱

@mckinley@twtxt.net I’m not sure to be honest I think it’s just a straight up duplicate post. This actually does happen, it’s not a bug, it’s a “human problem”, but yeah it’s annoying, so it’s making me want to figure out a way of keeping some kind of similarity db to strip duplicates out like this.

Hmmm the feeds service needs some kind of deduping 🤔 Slashdot seems to be the most frequent culprit 🙄 For example #oc2vksa and #wbx7ioq

Oh wow that’s a lot of UPS(es) 🤣

@bender@twtxt.net good idea 😅

@bender@twtxt.net Get well soon! 🤞

@bender@twtxt.net A: Yes

@bender@twtxt.net Yup! It maybe should try to detect a pipe maybe too?

And yes @bender@twtxt.net pods will reintroduce old root Twts like this back into active caches 🤣 Just not the ones in/between (old replies)

Funny how well shit works that we’ve collectively built 🤣

@jdtron@tilde.team As did I 🤣

@bender@twtxt.net Haha 😝

@bender@twtxt.net LOL 😂 I tried to even read the blog post, but I couldn’t. In all bluntness and honestly the layout and style of the website is total garbage, not to mention it’s written in a language I cannot read, but because it’s just so poorly written the translation service can’t translate it properly 🤦‍♂️ So point across FAIL

@bender@twtxt.net What is?! 😆

@lyse@lyse.isobeef.org Ahh yea! I’ll setup some CD for it this weekend 👌

@bender@twtxt.net Hmmm? 🤔

@movq@www.uninformativ.de

If you all were to clear your caches, would your clients fetch archived feeds?

No.

And I’m also thinking of nuking my pod at some point and starting over. But maybe after we refactor a few important things.

@bender@twtxt.net I think it comes down to one of the principles Yarn.social was founded on, which is to say, users should have choices and what they “see” is not driven by “algorithms”. The “Discover” view in and of itself has utility/value to others, and is otherwise just a “view” of a pod’s cache, but I agree with you. It was even getting noisey for me 🤣

@aelaraji@aelaraji.com Unofficially yarn supports the type field

Meg https://feeds.twtxt.net/slashdot/twtxt.txt

@aelaraji@aelaraji.com Probably not? https://dev.twtxt.net/doc/metadataextension.html

@aelaraji@aelaraji.com Same to you!

In other words, there isn’t anything specifically wrong with the Twtxt spec (+extensions), but if you for example use a client and server combination that never considered the User-Agent header and check logs or intercept requests for your feed, than you end up missing an important part of the whole flow (unless you are of course deliberating ignoring that, e.g: 1-way feeds, news feeds, etc).

In my opinion, this can all be solved by a “better standard client”.

For example I noticed in this thread, someone, me, and you, and now it’s just a bad @-mention mentioned Soren Peter with a bad link :/

This also just reminds me of the other problems that exist:

• bad mentions.
  
• knowing whether someone will you’ve @-mentioned will even see your reply at all.

@mckinley@twtxt.net I think we just need a way of surfacing this information better for both users and operators? 🤔