Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

https://github.com/tessalt/echo-chamber-js

Commenting without the comments
https://github.com/tessalt/echo-chamber-js

Last synced: about 2 months ago
JSON representation

Commenting without the comments

Lists

README

        

# Echochamber.js

## All of the commenting, none of the comments.

_alpha af_

Echochamber.js is a third-party script you can install to add a simple comment
form to your blog post or website.

_why not just use disqus?_

Because then there'd be a chance that someone would read the comments. _You_
might have to read those comments. You don't want that.

When a user submits a comment, echochamber.js will save the comment to the user's
LocalStorage, so when they return to the page, they can be confident that their
voice is being heard, and feel _engaged_ with your very engaging content. It does
not make any HTTP requests. Since LocalStorage is only local, you and your database
need not be burdened with other people's opinions.

## Features

- No server required!
- 100% spam-proof!
- Compatible with most blog and static site software
- Styles itself nicely to match your site's colours and fonts

## Installation

Copy and paste the following code where you want your comments to appear:

```html

var EchoChamber = window.EchoChamber || {};
(function() {
EchoChamber.discussionURL = window.location;
var script = document.createElement('script');
script.src = 'https://s3.amazonaws.com/echochamberjs/dist/main.js';
script.async = true;
var entry = document.getElementById('echochamber');
entry.parentNode.insertBefore(script, entry);
})();

```

## Screenshot

![screenshot](https://s3.amazonaws.com/f.cl.ly/items/1C2d1h3E2D07432A1W2Q/Screen%20Shot%202015-07-14%20at%206.19.28%20PM.png)

## Contributing

Requirements: [node](https://nodejs.org/)

1.Fork the repo
* clone the fork
* run `npm install`

### Local dev:

If you want to work with the iframe environment, there are some steps:

So you want the widget running on one server, and the host on another. I do this
locally by messing with /etc/hosts like so:
```
127.0.0.1 publisher.dev
127.0.0.1 widget.dev
```

* modify your httpd.conf file (in /etc/apache2)
```

ServerName publisher.dev
DocumentRoot "/Users/username/directory-of-widget"

ServerName widget.dev
DocumentRoot "/Users/username/directory-of-page"

```
* restart apache
* run `./script/watch.sh` during dev (unix only)
* run `./script/build.sh` before making a pull request
* make a pull request against the main repo referencing an issue if possible