Packages for building web applications in the Status ecosystem. https://status-components.vercel.app
Go to file
Pavel 820eafadde
[icons]: Sync icons, add social (#420)
* regenrate icons

* add social icons
2023-06-20 18:13:39 +01:00
.changeset Use built-in PBKDF2 implementation for browsers (#295) 2022-07-19 17:45:29 +02:00
.github/workflows Setup apps/website (#383) 2023-04-26 12:06:18 +02:00
.husky Add pre-commit git hooks (#229) 2022-02-24 23:27:22 +01:00
.vscode [website] Add link previews (#407) 2023-05-29 17:11:02 +02:00
apps [website] resolve ENS public key (#415) 2023-06-20 12:05:59 +01:00
examples [website] Add link previews (#407) 2023-05-29 17:11:02 +02:00
packages [icons]: Sync icons, add social (#420) 2023-06-20 18:13:39 +01:00
patches Setup apps/website (#383) 2023-04-26 12:06:18 +02:00
.editorconfig Add editorconfig 2022-02-25 14:56:28 +01:00
.eslintignore fix more incorrectly resolved conflicts 2023-05-16 11:53:43 +02:00
.eslintrc Add initial insights implementation (#388) 2023-05-03 14:25:17 +02:00
.gitignore fix more incorrectly resolved conflicts 2023-05-16 11:53:43 +02:00
.prettierrc Improve Prettier monorepo configuration (#225) 2022-02-23 15:49:00 +01:00
LICENSE-APACHE-v2 Update packages to @status-im (#223) 2022-02-23 15:03:14 +01:00
LICENSE-MIT Update packages to @status-im (#223) 2022-02-23 15:03:14 +01:00
README.md use yarn in readme 2022-11-17 18:44:25 +01:00
eas.json Add blur and IconButton variants (#340) 2023-02-10 17:25:13 +01:00
package.json Add website layouts and nav menus (#400) 2023-05-16 11:57:15 +02:00
tsconfig.base.json fix more incorrectly resolved conflicts 2023-05-16 11:53:43 +02:00
turbo.json Update turbo.json (#404) 2023-05-16 14:41:24 +02:00
vercel.json Set up website deployment (#391) 2023-05-12 15:06:04 +02:00
yarn.lock [website] resolve ENS public key (#415) 2023-06-20 12:05:59 +01:00

README.md

Status Web 🌐

CI

About

Embeddable, customizable and themable component for your Status Community.

Who

  • For community leaders
  • online content creators
  • and their followers

What

  • It is 100% open source
  • 100% decentralized
  • Peer-to-peer
  • Private
  • Pseudoanonymous
  • End-to-end encrypted
  • Free
  • Permissionless
  • Serverless
  • Group chat platform
  • And a virtual space outside the jurisdiction of any government

Why

  • To communicate and collaborate freely without worrying about
    • Censorship
    • Persecution
    • Chilling effects
    • Interference
    • Oppression
    • Being deplatformed, or shut down
  • Support
    • Autonomy
    • Free speech
    • Freedom of association
    • Freedom to transact
    • Right to privacy
    • Crypto native and frictionless integration
    • Monetization
    • Facilitation of sharing of common interests, needs, desires and values
  • Be trusted alternative to centralized group chat application

Usage

For Community owners 👥

Get public key to your pre-existing Community:

  1. Open Status Desktop
  2. Select Community
  3. Click on its overview in upper left corner
  4. Invite new people
  5. Share community
  6. Get only the public key from the URL (e.g. 0x033c88c950480493e2e759923bd38f9aad88e1b36295757a598679a569e6a96801)

Or create new one first:

  1. Get Status Desktop at https://status.im/get
  2. Go to Chat
  3. Click on plus icon
  4. Click on Communities

Use the Community component:

In your project,

Install package:

npm install @status-im/react

Import component:

import { Community } from '@status-im/react'

Set component props:

<Community
  publicKey="0x033c88c950480493e2e759923bd38f9aad88e1b36295757a598679a569e6a96801"
  theme="light"
/>

For an example, see examples/with-vite/src/app.tsx.

For User 👤

Simply visit your Community's URL from the browser:

If the Community doesn't require a joining request, that would be it. So look around and get the feel for the space.

Once ready to chat, create a throwaway profile:

Use Throwaway Profile > wait for your request to be approved and the chat input enabled > react to and write messages

Optionally, you could even run the application locally yourself.

Get the source ready:

git clone https://github.com/status-im/status-web.git
cd ./status-web
yarn install
yarn run build

Add your Community's public key to your environment:

echo 'PUBLIC_KEY="0x033c88c950480493e2e759923bd38f9aad88e1b36295757a598679a569e6a96801"' >> examples/with-vite/.env

And run it:

yarn workspace with-vite run dev