Man mastodon is broken.

I try to read this thread from mastodon.social and it clicks me into @newt instance: https://stereophonic.space/notice/A0nlzJPNBGYGlpKl2O

Where I see they are talking to someone on another instance, like @thatbrickster but I can't see the conversation interlaced on their interface, even though I can see their toots if I go to the third person's instance timeline.

Not saying it's those person's fault, just that this shouldn't be an issue period.

@surfingalot here's the reply from Moon, who runs shitposter.club. I suggest you find a better instance that doesn't block people left and right. I hear, stereophonic.space is a nice place ;)

@newt So clicking on the little timestamp on your winamp toot directly jumps me into your url: https://stereophonic.space/notice/A0nlzJPNBGYGlpKl2O from mastodon.social and when I open that url in an incognito window with no adblock, i still get the same experience.

I think it might be an auth issue since I see a "This API requires an authenticated user" error when clicking on one of the users, so it might be a weird config thing in stereophonic.space, but either way that shouldn't happen.

@surfingalot ah yes, our instance is somewhat under maintenance at the moment. You can enjoy it fully if you're a local user, but from the outside experience is a bit limited.

Basically, we do not show external statuses to external users to avoid all kinds of trouble.

@newt ah I see. That shows me that reading threads shouldn't be dependent on the root toot server to render. Not a great design :|

@surfingalot this is a somewhat forced measure. SPC was DMCA'd a few months ago, so in order to avoid this happening to us we disabled unauthenticated access. It will probably be re-enabled some time in the future.

@newt yeah that shows that rendering a thread shouldn't be the responsibility of the root toot server, but the user themselves when logged in , although I understand why they would do that for efficiency reasons. Would need some more design thought.