# Mini (Inline) Onebox Support RFC **URL:** \ **Category:** Feature\ **Tags:** rfc\ **Created:** [July 18, 2017, 6:51pm UTC](https://meta.discourse.org/t/mini-inline-onebox-support-rfc/66400 "2017-07-18T18:51:46Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\ **Post date:** [July 18, 2017, 9:31pm UTC](https://meta.discourse.org/t/mini-inline-onebox-support-rfc/66400/6 "2017-07-18T21:31:12Z")
Some suggestions: - Always prefer opengraph/etc to title cause stuff like this is bad: [https://www.yelp.com/biz/hummus-kitchen-new-york](https://www.yelp.com/biz/hummus-kitchen-new-york) ```plaintext Hummus Kitchen - Reservations - 340 Photos & 598 Reviews - Middle Eastern - Theater District - New York, NY - Phone Number - Menu - Yelp ``` - If title is too long always truncate and add elipsis at some sane length. (site setting maybe) - To opt out easily use this syntax: `` [https://meta.discourse.org/t/mini-inline-onebox-support-rfc/66400/5](https://meta.discourse.org/t/mini-inline-onebox-support-rfc/66400/5) , very easily detectable in our engine. - We got to protect the Mini Onebox from hammering servers… should only request first N bytes of the page. I like the external link icon, keep in mind some people may want to style it themselves for self owned domains and so on, so a class with the domain name would be nice. I would definitely avoid re-hosting and downloading custom favicons per site in the initial implementation, a default font-awesome icon for off-site is fine for the default. (also consider adding it optionally for any external links, at a minimum add a class on every `A` for internal vs external) --- _[View the full topic](https://meta.discourse.org/t/mini-inline-onebox-support-rfc/66400)._