# Embeddings are in BETA I've tested embedding a post into another post yesterday. Would love to hear suggestions on how to improve it. On a surface it looks like a quote repost, but's more than that. Composability of BOS enables us to embed anything into a post. By anything, I mean any other app/widget/component directly into the post. And it will be live and interactive. This brings security challenges similar to custom notifications, that if not carefully implemented can lead to phishing and other concerns. That's why we'll start with a whitelist of widgets that can be embedded in a post. In BETA mode, you have to create a named link in a markdown using the following syntax: ```md [EMBED](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=mob.near&blockHeight=103529805) ``` The link should point to a live widget that can be displayed in standalone way. This way legacy or different gateways have a fallback. The text of the link in BETA should be `EMBED`. Otherwise it will be treated as a simple link. Currently there is only one widget approved and this is a `mob.near/widget/MainPage.N.Post.Page`. Note, the link doesn't have to include the full path, e.g. it can be relative to the domain `/mob.near/widget/MainPage.N.Post.Page?accountId=mob.near&blockHeight=103529805` and it would still work. If you include this named link, the Post will use the widget `mob.near/widget/MainPage.N.Post.Embed` and pass all props to the widget. This is effectively a redirect from a standalone page to an embedded page. It allows a widget to be displayed in slightly different format (in this case hiding comments, buttons and the menu). Here is how it would look: [EMBED](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=mob.near&blockHeight=103529805) The logic behind this is stored in the widget [mob.near/widget/N.Embed](https://near.social/mob.near/widget/WidgetSource?src=mob.near/widget/N.Embed) I'm looking for suggestions on how to improve it. Here is my ideas: - Replace exact `EMBED` match with some prefix that triggers embedding. E.g. start text with `+` character: `[+My GM post](...)`. It would allow displaying reasonable text. - Alternative is how it's displayed during a fallback. Instead of `EMBED` it would display shortened link version - Open embeddings to a community, so long as the widget is secure, doesn't bleed CSS or privacy and locked by a blockheight version. - Get this standardize between near.social and near.org - Support short links. E.g. near.org has short links for posts, but near.social doesn't (for now). Please share you feedback and suggestions.