dstillr — A new Google Chrome extension that protects your Steemit.com wallet from memo spam. Get it now from the Chrome Web Store
Source Repository
https://github.com/tdreid/dstillr
What is the project about?
dstillr is a free, open source Chrome browser extension that helps you control the messages in your wallet on Steemit.com.
Filter messages and accounts from your wallet page with dstillr and focus on the transactions that matter to you.
Technology Stack
Like any Chrome extension dstillr boils down to pure HTML, JavaScript and CSS. The Chrome Extension API naturally plays an essential role.
Beyond that these dependencies facilitate development and bundling:
❱ babelify, babel-core and babel-preset-env
❱ browserify
❱ jest (test coverage anticipated in the roadmap)
❱ uglify-js
Roadmap
This is an extension that I use myself every day and I am constantly adding to the list of features that would make my Steemit.com transfers page easier to manage. Some of the features at the top of my list include:
❱ Support more platforms (e.g. Busy)
❱ Provide a badge indicating how many transactions were blocked
❱ Create a handy way to make temporary exceptions on a case-by-case basis
❱ Additional options for blocking messages, for example:
- by message length
- by amount (e.g. 0.001 )
- by keyword, phrase, or spam detection algorithm
❱ Provide an option to sort the list of blocked accounts
❱ Catch up on automated test coverage
❱ For additional planned fixes and enhancements please see the issues list on Github
In addition I am very open to suggestions from those who find this useful and would like to make it better. You can make suggestions either on Github or via the feedback form in the Chrome Web Store.
How to contribute?
This project welcomes Pull Requests and Issues on Github.
Please submit an Issue to:
- Report a bug
- Request a feature
Proposing a change
Please fork the dstillrrepo and submit a Pull Request.. Include a bit of a summary and follow the guidelines in GitHub documentation.
If your change addresses an existing issue please reference your PR in the Issue discussion.
Refer to the README.md file for instructions to build and test in your environment.
Coding conventions
Per the 
New source files require the license header. Follow the pattern in existing source files.
Please run prettier --write --single-quote or an equivalent on all new or changed Javascript before submitting.
There's no need to include bundler build output in your Pull Request unless you want to as I will build these as part of the code review in any case.
