repost Node-api team meeting recording post

[mhdawson]

No description provided.

[jasnell]

I think it would be ideal if we could have these be original posts rather than reposts from other accounts.

[jasnell]

Per my comment, I think it would be best if this were not a repost but a direct post.

[joyeecheung]

Suggested change

	"action": "repost",
	"account": "NODEJS_ORG",
	"repostURL": "https://bsky.app/profile/mhdawson.bsky.social/post/3ls2faw4f2s24"
	"action": "post",
	"account": "NODEJS_ORG",
	"richText": "Recording from the #nodejs Node-api team meeting today in case you want to catch up https://www.youtube.com/watch?v=_eCD-T1DZsU"

@jasnell In case you didn't notice, this is how the suggestion is supposed to work in this repository. See https://github.com/nodejs/bluesky/blob/main/automation.md#perform-actions-with-a-pull-request

[joyeecheung]

Somewhat related to this action request - according to the survey results so far (only published for less than 24 hours so please take it with a grain of salt), it seems many respondents would prefer to see less posts about meeting recordings. I wonder if there is a way to make these posts more palatable: we can collect recordings of meetings in one post per week to reduce the volume of this. It might also serve as a base of a comeback of https://nodejs.org/en/blog/weekly - but we can start small with just meetings in a weekly post. (Personally, I don't mind whether it's a repost or not, a repost of weekly digest of meetings seem to be an equal improvement to me, and I think it's important to give some recognition to the work invested in putting them together)

[RaisinTen]

Why is a direct post preferred over a repost in this case?

[jasnell]

I believe it's more professional, and ensures that the post is more representative of the project as a whole, rather than highlighting one individual too much. It's less likely, for instance, that the node.js account has been blocked by potential subscribers as opposed to individual people, etc.

[aduh95]

I disagree with James, I think it makes more sense for us to retweet Micheal than to make a new post – that way, if e.g. someone just hates meeting recording for whatever reason, they can block Micheal.
That being said, as Joyee pointed out, we should reconsider whether posting about meeting recordings makes sense, it would probably be more useful if we only post about the ones we want to highlight.

[jasnell]

Well, done correctly such posts would include words/tags that could be easily muted, allowing the posts to be hidden based on more granular preferences, which is much more effective in my opinion. But on the point of value, I agree these posts have exceedingly little value and I'd prefer they weren't reposted via this channel. I just ask that if they are, they be original posts and not reposts.

[RaisinTen]

The review guidelines still say:

• Reposts of posts sharing information on project meetings.

Going by that, this PR qualifies and should be allowed to land. It's fine to discontinue posts of this category if the review guidelines are updated with something that doesn't allow these.

So LGTM.