# Blacklist vs whitelist onebox

**URL:** <https://meta.discourse.org/t/blacklist-vs-whitelist-onebox/21811>\
**Category:** Feature\
**Created:** [Novembre 4, 2014, 11:48 UTC](https://meta.discourse.org/t/blacklist-vs-whitelist-onebox/21811 "2014-11-04T11:48:57Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![evantill](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/evantill/32/116219_2.png) [@evantill](https://meta.discourse.org/u/evantill)\
**Post date:** [Novembre 4, 2014, 11:48 UTC](https://meta.discourse.org/t/blacklist-vs-whitelist-onebox/21811/1 "2014-11-04T11:48:57Z")

</div>

Continuing the discussion from [Auto-discoverable oneboxer-able links based on whitelist configurable by admin](https://meta.discourse.org/t/auto-discoverable-oneboxer-able-links-based-on-whitelist-configurable-by-admin/9068/5):

> [@krainboltgreene](#):
>
> Hey, onebox gem “team lead” here. I’ve got an open issue for whitelist/blacklist functionality here: [Whitelist/blacklist certain domains · Issue #124 · discourse/onebox · GitHub](https://github.com/dysania/onebox/issues/124)

I would like to enable onebox for every site that support `oEmbed` or `Open Graph` and be able to blacklist some sites in case of improper usage.

---

_[View the full topic](https://meta.discourse.org/t/blacklist-vs-whitelist-onebox/21811)._