Packages for building web applications in the Status ecosystem. https://status-components.vercel.app
Go to file
Felicio Mununga 181faba3a6
[*] prepare packages for release (#432)
* upgrade changeset

* fix eslint config name

* remove publishConfig

* remove changesets

* tmp: scope

* Revert "remove publishConfig"

This reverts commit 3a085e3f85.

* add publishConfig

* v0.0.0

* remove private flag

* tmp: scope

* docs(changeset): changeset config

* changeset commit config

* docs(changeset): changeset config

* RELEASING: Releasing 6 package(s)

Releases:
  @felicio/eslint-config@0.1.3
  @felicio/components@0.0.4
  @felicio/js@0.2.3
  @felicio/colors@0.0.4
  @felicio/icons@0.0.4
  website@0.1.3

[skip ci]

* rm changeset

* fix eslint config deps

* docs(changeset): fix lint config deps

* RELEASING: Releasing 1 package(s)

Releases:
  @felicio/eslint-config@0.1.4

[skip ci]

* upgrade @tamagui

* upgrade react-native-web

* update yarn.lock

* use Presable instead of Stack for styled button

* fix defaultVariants.blurred after upgrade

* update changeset config

* release

* add tamagui deps

* release

* release

* export popover

* release

* revert @status-im scope

* rm version from root package.json

* rm changelogs

* revet package versions

* add changeset
2023-06-29 11:04:52 +01:00
.changeset [*] prepare packages for release (#432) 2023-06-29 11:04:52 +01:00
.github/workflows [website] use demo ghost for blog in dev (#428) 2023-06-28 17:41:35 +01:00
.husky Add pre-commit git hooks (#229) 2022-02-24 23:27:22 +01:00
.vscode [website] Add blog (#417) 2023-06-21 11:35:48 +01:00
apps [*] prepare packages for release (#432) 2023-06-29 11:04:52 +01:00
examples [website] Add link previews (#407) 2023-05-29 17:11:02 +02:00
packages [*] prepare packages for release (#432) 2023-06-29 11:04:52 +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
.gitignore [website] Add documentation (#403) 2023-06-27 21:30:11 +01: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 [*] prepare packages for release (#432) 2023-06-29 11:04:52 +01: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 [*] prepare packages for release (#432) 2023-06-29 11:04:52 +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