작성자가 명확히 표시된 블로그 게시글이 더 좋습니다

I’ve noticed over the last wee while that the linked topics to blog posts have @Discourse as the ‘owner’, regardless of who authored the blog.

This somewhat impairs the community experience here on meta.discourse.org:

  1. It feels less intimate

  2. the author isn’t notified for replies

These make me far less likely to engage on those topics, and I suspect I’m not alone.

Of note, some original blog articles (such as Behind the Scenes: Our 2025 Prague Meetup) are ‘authored’ by “The Discourse Team”. This is even more offputting!

One of the strengths of CDCK is that you are not a bunch of faceless workers, but real people that fanboys like me can get to know.

To quote that blog post:

This is a core part of the Discourse value system: that as a company and a culture, we believe in human connections. We’re dedicated to recreating those connections online

I’d encourage you to lean in to this more on the blog site and on meta!

14개의 좋아요

Great idea! I wonder, is it possible with Embed Discourse comments on another website via Javascript?

I don’t think it’s easy, and you can tell who the author is if you click the link to the blog. Maybe if you want to know who wrote it, you just have to make one more click. :person_shrugging:

1개의 좋아요

Looks like the change from individual users to using the Discourse user happened about a year ago.

Blog topics created 1 year ago ordered by create date In this list, currently only the newest topic is authored by Discourse; all the others show a user. I wonder why that changed.

1개의 좋아요

Thanks for pointing this out! I hadn’t noticed before, but it appears that the authorship of blog posts and their related topics on meta are not always in sync. We’ll have to go back through and make sure the authors match up, for the reasons @nathank states. Then going forward remember to change the author to match. That is super helpful feedback.

When a post on the blog is authored by “Discourse Team” that is intentional and it makes sense that the Discourse user on meta is the author too. In those cases we are collectively writing as a team. That post represents all of us who were there!

If you scroll through the blog you can see that nearly all posts are authored by specific people.

4개의 좋아요

Thanks for the report, there was a bug in our blog theme, just fixed it so authors will be correct now.

5개의 좋아요

지난해까지 모든 게시물의 저자를 업데이트했습니다. 훨씬 더 보기 좋습니다! 피드백을 주신 모든 분께 감사드립니다.

이것은 "무엇을 보거든, 말하라(See something, say something)!"의 훌륭한 예시입니다. 개선할 수 있는 부분을 발견하시면 알려주세요. 제게 DM으로 보내주셔도 좋고, Contribute > Site feedback 채널에서 말씀해 주셔도 좋습니다. :hugs:

4개의 좋아요

Seems like the author didn’t show up on this one?

1개의 좋아요

Good catch! I fixed it but seems the bug persists, @falco?

2개의 좋아요

It has happened again:

2개의 좋아요

It still happens on most blog topics until someone changes the ownership.

2개의 좋아요

We will have to add it to our process to check these when posting to the blog and fixing them when they happen - I think it has to do with a username or email address mismatch between ghost and discourse. In any case it’s an easy fix when it happens.

If you come across it again, please just flag it.

I am going to close this topic.