Email or username:

Password:

Forgot your password?
Julia's posts Post Back to profile
Top-level
Gaelan Steele

@b0rk I wonder if it's a federation thing - since Mastodon users can't necessarily see other existing replies, you lose a form of self-regulation where you hold back if several people have already said the thing

13 February at 14:42 | Wall-to-wall | Open on cathode.church
8 comments | Expand all CWs
Gaelan Steele

@b0rk (when I worry I might be doing this, I specifically go to the original instance to check there aren't already similar replies - but I suspect I'm in the minority there)

13 February at 14:43 | Open on cathode.church
Julia Evans

@Gaelan yeah i wrote a blog post about this and other technical factors jvns.ca/blog/2023/08/11/some-n but i was left feeling like that’s not the only thing

13 February at 14:46 | Open on social.jvns.ca
Gaelan Steele

@b0rk ah oops sorry! I've probably read that, even

but yeah, I'd totally believe that there are social factors too

13 February at 14:50 | Open on cathode.church
Ed Cashin

@b0rk @Gaelan That is a really interesting blog post. Thank you for recording all those facts and impressions.

13 February at 14:55 | Open on infosec.exchange
Andreas

@b0rk @Gaelan I have seen that complaint (about replies not being shown) quite a bit recently.
Similar to @Gaelan I usually open a reply-worthy post on the original instance to see the replies and then often can close the browser tab because hey, someone already did take the words out of my mouth.

That would support the idea that the reply fetching behavior needs to be improved. On the other hand, I've already seen some improvements with recent Mastodon releases showing way more replies on "older" posts.

But on fresh posts, still nothing. Unfortunately.

Case in point, I do not see any replies from @Gaelan here but only on the original instance.

So much for the technical aspect... But I do keep wondering about the social aspects. Do you think being very liberal with the blocking function would help after a few weeks of using it?
I recently had a typical reply-guy experience. Asking about technical advice for a laser printer problem, get someone telling me how they are always driving to the local copy-shop to print.
Completely useless post, a waste of electricity...
I ignored it but for someone with a lot of followers that can get tiring soon I'd guess... So blocking is the easy approach... Maybe?

@b0rk @Gaelan I have seen that complaint (about replies not being shown) quite a bit recently.
Similar to @Gaelan I usually open a reply-worthy post on the original instance to see the replies and then often can close the browser tab because hey, someone already did take the words out of my mouth.

That would support the idea that the reply fetching behavior needs to be improved. On the other hand, I've already seen some improvements with recent Mastodon releases showing way more replies on "older" posts.

13 February at 17:15 | Open on mastodon.bawue.social
Matt Ferrel

@Gaelan @b0rk thanks for the reminder that we don’t necessarily see all replies

13 February at 16:13 | Open on mastodon.sdf.org
Rihards Olups

@Gaelan @b0rk
I used to check the original instance, but it's too much of a hurdle, and eventually I had a choice between "check the source" or "stop engaging".

Firefox addon Substitoot might help, BTW:
addons.mozilla.org/en-US/firef

13 February at 17:04 | Open on mastodon.social
JimmyChezPants

@Gaelan @b0rk

I think this is definitely a problem also, and I've gotten into the habit of clicking through on anything that looks like it would have replies, even if I see none, though not for the reason you described (now that also tho lol).

This process also seems like something that could be handled at the client level, really.

13 February at 16:46 | Open on growers.social
Go Up