Cross-Discourse Quoting

It would be useful if I could quote posts from external discourse instances. Something like

[quote=“member, post:3, topic:275, source:meta.discourse.org”]

Where source:meta.discourse.org would provide a similar level of context as internal quotes.

My primary use case is that I’m currently training my Staff to rely on flags instead of manual moderation, and wanted to show them this:

I copied/quoted that from the topic here on meta, and pasted it into my forum, not really thinking about what I was doing. It of course linked to a topic on my forum with the same id, which makes perfect sense, but isn’t what I want.

I could link to the post directly, which works nicely with the onebox, but I really just want to call out the relevant piece.

Aside from staff-training, I also run a few different sites that could benefit from occasionally sharing parts of conversations between them. As an added bonus, this would show users that there’s a larger Discourse world out there by bridging conversations between communities.

5 个赞

errr isn’t this called “oneboxing an external URL”? I mean, it already works…

https://community.letsencrypt.org/t/how-to-stop-using-tls-sni-01-with-certbot/83210

1 个赞

Yes that works, but that’s not what I’m describing. That’s a link to the entire post, I’m wondering about the possibility of linking to a quote:

The idea is to load a quote like the one above, so that readers can see a specific part of an external post instead of a link to the full thing, but also with a link back to the source.

It would be quicker than onebox to get specific info to readers, while still letting them get all the context if they want it.


edit: update with example from the link you posted

If you’ve configured Certbot to use a directory other than /etc/letsencrypt, you should use that directory in the commands instead.

The reference post in its entirety would be too much info if I just wanted to quote the piece above, and would cause more friction for the user than is ideal. Focusing on the quote instead is more useful, but now it is somewhat orphaned. Quoting parts of posts between instances would be the best of both features.

3 个赞

Right but in that case I’d just quote the remote site and provide the URL at the top… like so?


As it says in https://community.letsencrypt.org/t/how-to-stop-using-tls-sni-01-with-certbot/83210

All most users need to do is make sure your Certbot installation is up-to-date and test and configure automatic renewal for the updated version of Certbot. You can find instructions for how to do this at https://certbot.eff.org . You need Certbot version 0.28.0 or newer. You can check which version you have installed by running Certbot with the --version flag.

2 个赞

The reason oneboxing exists is you can’t assume what other servers are running in terms of version or platform. Not to mention that just because a site is running a particular platform today, that the same will be true tomorrow.

Create a dependency on Discourse now and if anyone ever does move away any platform-specific embedding would break. It’s one of the reasons oneboxing is so damn useful.

4 个赞

@codinghorror that does work yeah, but it doesn’t have the same slickness as the regular copy/quote feature. Regardless, this isn’t a common enough of a case to be bothersome, but it does have me curious about what is possible. :thinking:

@Stephen I hear ya, that does make sense. Though, would it not be within Discourse’s control to send information about itself to another Discourse instance if it recognized the request? There’s no assumption if a response says: “Hey, I’m a Discourse site too! Here’s the author name and post url to render alongside that quote you requested.”.

That’s a good point though about platform-specific embeds and migration issues. :grimacing:

Perhaps I’m envisioning something too grand here, but a Discourse instance recognizing its siblings across the web seems so cool as a concept, as does users being able to directly quote/converse with each other across communities.

Maybe one day!

4 个赞

Discourse 引用(从其他 Discourse 实例引用)

十年前曾有过类似的讨论,但没有取得任何进展。现在,我们有了更多的经验和工具……

想象一下,你是 Discourse 团队,你正在使用一个公共 Discourse 实例和一个私有 Discourse 实例。通常你会将公共实例中的引用复制到私有实例中,但这样会丢失上下文:你无法展开引用或点击跳转到原文,而必须同时提供源 URL。现在,如果你的读者已通过身份验证,并且 source URL 是引用的一部分,你就可以_无缝地_从一个实例跳转到另一个实例。

非常适合Discourse-connect 网站,以及使用 ActivityPub Plugin 的网站。

3 个赞

我非常喜欢这个主意!您描述的正是我们在 Meta 和内部实例之间所做的。

我认为最显而易见的地方就是从帖子中选择文本时弹出的“复制引用”按钮。

4 个赞

我建议添加一个站点设置,用于切换复制的引用是否包含域名。我在教育领域有一个用例,不希望复制粘贴的内容显示其来源域名🙂

3 个赞

2023年也有 Include the forum's URL in quotes :face_with_tongue:

如果这个话题在其他话题中出现过,我不会感到惊讶。

4 个赞

你能详细说明一下吗?

如果我们通过复制引用添加域名,我认为我们可以方便地在同一站点的编辑器中粘贴时将其删除,这样在这种情况下,用户体验将保持不变。它不会在另一个实例或任何其他地方粘贴时被删除。

2 个赞

我的情况更实际:当我使用 复制引用 时,它会保留原始的 LaTeX 源代码,这正是我在其他地方重新使用数学公式时需要的。如果我只是突出显示并复制,我通常只会得到渲染后的 MathJax,而不是源代码。问题是 复制引用 还会附加带有域名的归属行,而我不需要它。所以这里的需求是:保留保留 LaTeX 的行为,但不要自动添加链接。