status in the browser
Go to file
Iuri Matias 187348bbd1 update readme & info 2019-02-07 20:55:34 -04:00
build update dapp, add disclaimer 2019-02-07 20:55:34 -04:00
public add status branding 2019-01-31 15:41:40 -05:00
src update readme & info 2019-02-07 20:55:34 -04:00
.env initial add status-js + Murmur + ui components 2019-01-30 16:20:04 -05:00
.gitignore add build with relative paths 2019-02-07 20:55:33 -04:00
README.md update readme & info 2019-02-07 20:55:34 -04:00
package-lock.json initial add status-js + Murmur + ui components 2019-01-30 16:20:04 -05:00
package.json add build with relative paths 2019-02-07 20:55:33 -04:00
yarn.lock update murmur-client version 2019-02-07 20:55:04 -04:00

README.md

Status Web Chat

Click here to access status-web. note that no plugins are required, just a compatible browser. Currently recommended are Chrome and Firefox.

Note: This is a proof of concept, and an alpha version. There will be bugs. If you you're looking for something more stable try the status desktop app.

known issues:

  • Only tested in CHrome & Firefox. Reportedly works on android mobile browsers but not on ios (to be confirmed). In theory it should work on any webrtc enabled browser.
  • Direct chats and chat history is currently disabled.

what you can do:

  • Join other status channels, this bridges with devp2p network.
  • see who is online in the channel (applicable to other status-web users)
  • see who is typing in the channel (applicable to other status-web users)
  • see previews for images, spotify (e.g spotify:track:0vnfZAVW1Suiet6wtUMdg9)
  • code formatting(e.g js` var a = 3;)
  • upload files
  • emojis support

Available Scripts

In the project directory, you can run:

npm start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

npm test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

npm run build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

npm run eject

Note: this is a one-way operation. Once you eject, you cant go back!

If you arent satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point youre on your own.

You dont have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldnt feel obligated to use this feature. However we understand that this tool wouldnt be useful if you couldnt customize it when you are ready for it.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

Code Splitting

This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting

Analyzing the Bundle Size

This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size

Making a Progressive Web App

This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app

Advanced Configuration

This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration

Deployment

This section has moved here: https://facebook.github.io/create-react-app/docs/deployment

npm run build fails to minify

This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify