Ok then that with the post you linked its more like shitstorm with Lemmy rather than about Sublinks like in your title

When you say devs in the start of the post, which devs are you referring to. You never clarify

Theres more than just the api repo and pull requests are squashed in some of them making it show as less

There's no relation to google docs, just has a similar name for the event

Its grants for hiring a technical writer

!linux@programming.dev

Code blocks got updated in 0.19, lemmy.world is still on a 0.18 version

Converting ampersands to say amp instead is a bug that got fixed in version 0.19, world hasnt upgraded yet though

Didnt say to go anywhere, just said that people on .world cant see content from hexbear on lemmy.ml posts shown by those comment counts above even though lemmy.ml federates with hexbear. (hexbear used since its the best example of a large blocked instance that can showcase this well. Could have also used .world, .ml and beehaw and same point stands)

Same logic would apply to .world federating with threads. People on lemmy.dbzer0 for example wont see content from threads on .world posts or communities even if .world federates with threads

Just wanted to put a counterpoint to you saying people would need to deal with it indirectly which isnt true proven by the above. You dont need to strawman it by making it a different point

Instances that defederate with threads wont see content from threads even on other instances that may federate with them.

As an example here lemmy.ml federates with hexbear and world but hexbear and world dont federate with each other. On lemmy.ml posts world users cant see any comments made from people on hexbear and vice versa

• A post in the view of .world: https://lemmy.world/post/9466410 (282 comments)
• The same post in the view of hexbear: https://hexbear.net/post/1304992 (76 comments)
• The same post in the view of lemmy.ml: https://lemmy.ml/post/9207671 (306 comments)

So they wont have to deal with them indirectly

oops didnt see that header

will keep them in the description there just in case people dont know what 3.11 added since I dont believe theres been a 3.11 post here before

I havent used nvchad before but im assuming theres a mapping set to make that behaviour happen

Would be in a core/mappings file if its from nvchad or a custom/mappings file if its not (inside where you cloned the repo to)

https://nvchad.com/docs/config/mappings