Wow, so pretty, dude! The one you used on this twt (tiny photo too, not sure what happened here) doesnât make justice to the entire set. Very good clicks there!
@aelaraji@aelaraji.com Like deebs.net đ¤
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) đ˘
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
Hah 𤣠@dfaria 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.
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 đ˘
This happens more often than I would like. đ˘
Today in the news
Microsoft is a security risk
@bender This is what I fell over and bunged up my shin đą
@bendwr and I discussing something along the lines of: I.e: How to deal with or reduce noise from legacy feeds.
Renders like this: