Notices by Matt Wilcox (mattwilcox@mstdn.social)

@fae2535 Because that's how federation works. Your own server may not have seen all the responses from other servers yet. It's a technical limitation of not being a centralised service.

@fae2535 No worries. It's one of those quirks of the platform - it's not obvious why it'd be that way.

Mastodon isn't "one giant thing" like Twitter. When you post, it takes time for other servers to know about it. Same for replies to posts. Not all servers know about each other, so replies from one of those places might be missing for you - unless you go to the same server as the person who's post you're looking at.

TLDR: A nerdy weirdness of the system.

@hirsebirse I can't blame the young-uns.

Unfortunately this sort of tooling seems to me to be the result of engineers solving genuine problems, but engineers who have historically maligned HTML because "HTML is not a real language" and dismissed CSS because it simply doesn't work in the way that other programming paradigms do.

As a result, their ignorance has produced a little ecosystem of crap, that got big enough to sustain itself, for a while.

Can't wait to see it die out.

If your developer tooling is putting out #HTML that looks like this; I don't care what advantages that tooling seems to give to you the developer - the output is garbage that does not work with the grain of the web itself.

It's using the core technologies of the web in a manner entirely antithetical to their design.

It is anti-web.

This is a cul-de-sac of development practice.