xcf-babble/babble

说都不会话了。

babble's Issues

Add continuous integration

Continuous integration can be used for these 23 purposes:

• Check lint and code generation issues.
• Produce release artifacts.
• Add a shiny passed badge to the README.md file and make the project look professional.

Support Diffie Hellman Key Exchange

by crypto_scalarmult.

Have the background script keep state of the last message.

Have the background script maintain a light dictionary -- domain to last unsent message. This way if the popup is closed, users won't lose their content. Create a listener in the background script that will send the message for each page. When the popup opens, make a request to the background script for last unsent message.

The new linter doesn't wrap long lines

Create a YouTube video showing how to use the extension

Include steps for:

• Adding a key to the keystore
• Creating custom base
• Encryption on supported site
• Encryption on unsupported site
• Decryption picker
• Show how to cancel decryption picker, and how to click makes the aside stay up
• Show keybindings (screenkeys)

We can link this video from the Chrome webstore and Firefox AMO

Discord is broken

They changed the input box from a textarea to a div that tries to be like a textarea... Similar to Twitter and Facebook. Sad.

Remove jquery

It was good for prototyping but it should not be part of the project.

Add support for encryption/decrypt from HTML Textareas.

It would be neat and useful to be able to use Babble to arbitrarily encrypt and decrypt from HTML textareas located on various web pages.

Add descriptions to icons in babble popup

• Please add descriptive popup to each icon to explain what it does.

Suggested by Yuki2718

Support Input Boxes on More Websites

More default bases in different languages

This thread is to discuss and propose new default bases.

Create custom response interface

Document hidden features

such as keyboard shortcuts.

Add import and export functionality

This will make it easy for users to transfer keys that use custom bases to friends. Recommend magic-wormhole for transport

Remove redundant entries in webpack and manifest

Element picker is broken on OSX

Make hyperlinks in decrypted text clickable!

Look into using chrome.runtime.connect for talking to iframe

Right now, the way we send messages to the iframe is to proxy them through the background script. See if it's possible to use chrome.runtime.connect and using the Port object to set up two-way communication between these pages.

https://developer.chrome.com/apps/runtime#type-Port

Excessively long decryption key name makes UI unusable

Decryption picker can flicker

Maybe we add a delay of some sort?

Support multiple platforms without manual npm run <browser>

Change Alt+Shift+Z to Alt+Shift+E

Add keyboard shortcut to start decryption picker

Add links to Chrome webstore and AMO in README

avoid callback hell with chrome.sendMessage

The Firefox sendMessage implementation is much more sane than Chrome's. Instead of using a callback when the listener returns, it instead returns a Promise. For chained messages (which we will need to do for context menu decryption), it keeps us from entering the depths of callback hell.

We can either pull in https://github.com/mozilla/webextension-polyfill that will polyfill the mozilla sendMessage for chrome, or we could write a wrapper around the chrome API.

Notify on iFrame tampering

If any of the iFrame attributes are modified (specifically z-index), the iFrame is deleted, or it is not in the viewport, send a notification to the user so they are aware the page is hostile.

Don't show password in babble keystore

I think it's better to hide passphrase on Babble Keystore by asterisk to prevent shoulder surfing (click-to-open).

Suggested by Yuki2718

Add option to encrypt keystore

Like a password manager, give users the option to have the keystore encrypted at rest. This means that, for every new browser session, the user will need to enter their decryption password before it can be used. We can put a nice lock UI on the popup.

Only spawn document observer when babble popup is open

The plugin does not work with CalNet ID SSO

Add context menu decryption.

Clean up webpack

• webpack and its dependencies are vendoring themselves. Figure out how to not do this if possible since one of its dependencies, bluebird, runs eval 3 times!

• split vendor.js into multiple files so we can split up dev dependencies our project files to lighten the load on some pages that don't need to pull in everything

Replace `loader` with `matches` in content_script manifest

Improve performance by loading fewer scripts, and add listener in content script to get an object handle.

Use less technical language in the extension

It would be too difficult to use for common people - they don't know what the public key is and why they need to exchange it - it's okay if your tool targets only those who know how it works, but if not, UI need to be improved, tho I can't comment on it much.

Make the extension more friendly to nontechnical people.

Suggested by Yuki2718

Make Argon parameters tweakable

Suggested here. This would be for advanced users that have higher memory devices. Since we aren't targeting mobile, we could also bump the memory usage to be higher than 64MB. We would want some advanced options menu for this.

Convenient debabbling outside of browser

Currently babble'd text can be copied by simply clicking the copy bottun, then be pasted to other places. But debabbling can only work on web pages, by selecting elements containing babble'd text.

There can be a encrypt/decrypt switch on the addon dialog. When the switch is on 'encrypt', everything works as it is now; when it is on 'decrypt', do what 'debabble page elements' basically do.

Though it is not babble's primary use case to handle communications outside the browser, supporting that can also enable potential users to try it out (possibly on non-web IMs).

Investigate obfuscating ciphertext

A paper was released recently that describes novel methods for encoding text inside of a language model. The example implementation can be found here. Babble could give users the option to hide their text this way.

Because this requires mountains of work, this is mostly here as a reminder and will not be worked on anytime soon.

Detailed instructions for adding support to a new website

Explain, in detail, how the website.ts API works, give a run through of an existing website that we support (Slack), add common tips and tricks for finding input boxes.

We should wait until the website.ts API matures more before doing this. Some users have already suggested we add the capability for site-specific decryption.

Add a button in the iframe to switch the encryption key to the decryption key

Would be useful but requires some API re-engineering.