Yeah, it's got advantages and drawbacks. /r/Europe had a fairly-strict implementation. It's helpful to avoid people editorializing titles, which was definitely originally a problem there, and for some reason, I've rarely run into here.

However, it hits a couple problems:

• Some publications have titles that are totally reasonable in the context of a reader of the publication, but which are unreasonable if you're just skimming titles from many publications on a social media website. I remember people complaining about some title in a publication aimed at US Navy personnel, and people on /r/Europe complaining that it didn't explicitly say which country it was talking about in the headline, which was talking about "the Army" or something like that.

• A bunch of publications stick their name on the titles of their page, which is just obnoxious when social media websites tend to also show the domain name of submissions.

• I see a lot of headlines with mis-escaped HTML ISO entities.

• Sometimes it's not immediately clear why a given story is relevant to the community. For example, maybe you're on, oh, a community that deals with books. An article comes out titled "Trump tariff policy gets additional executive order updating policy". In the context of the specific community, you might really want to know the fact up-front that the issue is that one of the items in the order is either books are excluded from tariffs or that there's a global 200% tariff.

The Threadiverse does let one attach some text to a submitted article, which both partly brings back the issue with editorialization (if I'm putting anything that'd be potentially-controversial, I try to put it in a top-level comment rather than the submission text), but can let one do some of the "context-information-providing" stuff. But that's not subject to community correction; only the submitter can deal with it. And it doesn't show up in the list of articles, just when viewing the comment page for an article.