afontenot

I see a couple issues with this implementation. 1. It needs `resize: none` set as a CSS style or else it looks weird. (You also didn't fix up the CSS;...

Each instance does its own verification. Some instances (including mastodon.social) are currently believed to be having problems due to overload, so that's probably your issue. See some of the comments...

> I don't think it's some kind of issue with a queue unless there's a priority queue for link verification of users on the same instance. Not priority, it just...

So, just to be clear about this issue, the first comment says that this applies to *any* 4.0.0rc1 server. Presumably (because the changes are irrelevant) it would apply to 4.0.0rc2...

> This seems like the very same bug, just taken from a different point of view: #19991 I think it's best to keep this bug about the memory issues resulting...

I don't like the idea of making users enter html tags directly. I think any version of this should strive to be markdown compatible in case something like #10787 is...

@ioquatix Ah, sorry, I misread your most recent comment as changing the proposal to just adding parsing for the code fences directly, rather than adding markdown support for them.

Incidentally, I know there's a lot of action on this issue tracker right now, so I want to emphasize that I'm not trying to create any pressure to have this...

I like this idea although I suspect there is probably some significant amount of server overhead with allowing users to retrieve a very large (or indefinite) amount of timeline at...

Ideally, this would include a way to treat opengraph previews seperately from oembed embeds. The former are almost always pretty reasonable and static, and most users probably won't want to...