@InspectorCaracal I think it's to support different instances having embed capability-things?
like how the.resize.club has "read more" links for long posts
Because a toot from some other instance may contain a feature that depends on that instance, you can't federate *just* plain text.
standard posts in mastodon don't allow you to put a link with a name - I can put the link, but I can't name it
but on the resize club, they don't have a character limit. So on the server itself, they store the whole text of a long toot. But if a long toot is federated, it is cut off at a certain point and there's a "Read More" link.
@InspectorCaracal another example is custom emojos - they need to be sent as images, not as the :emojo_code:, because your server doesn't know how to render them
@InspectorCaracal (this is all guesswork, mind, I haven't delved into the actual code)
@lizardsquid Oh, no, they're not sent as images, custom emoji federation is a whole different ball of wax.
@lizardsquid custom emoji are done more like user avatars, I believe, they're stored locally and referenced by the code.
@InspectorCaracal ah, that would make more sense
@lizardsquid huh! I've never seen that. 🤔 I feel like that might be taking advantage of it federating in html more than vice versa, though... But that sounds like an awesome feature.
What I want to know right now is how the web app decides how to display local toots, without having all the html data??
@lizardsquid *studies this for a minute*
I'm not following.