Berty is a full-stack, privacy-focused, peer-to-peer messaging application. The system consists of a Go backend implementing the Wesh protocol (based on IPFS, libp2p, and OrbitDB) that provides core messaging, push notifications, authentication, replication, and directory services. The backend is exposed via gRPC and consumed by multiple clients: a React Native mobile app (with both a legacy JS variant and a newer Expo-based variant), a Go CLI with a terminal UI (mini) and a desktop GUI (Fyne), and native bridges for iOS and Android. The architecture is modular, with separate packages for error handling, authentication, push relay, and bot framework. Key entry points include the `berty daemon` CLI command, the mobile app entry points (`App.tsx` in both `js/packages` and `berty-bridge-expo/mobile`), and the bridge framework (`go/framework/bertybridge`). Data flows involve gRPC streams from the Go backend to the mobile clients, with event-driven state management and local encrypted storage via SQLCipher. External dependencies include libp2p, OrbitDB, gRPC, protobuf, and various platform-specific native modules for BLE, mDNS, and push notifications. The repository also contains auxiliary tools for infrastructure testing, rendezvous servers, and debugging (Tyber).
This repository hosts the GFWList, a community-maintained blocklist of domains and URLs blocked by the Great Firewall of China. The primary data asset is `list.txt`, a plain-text file in AutoProxy format containing thousands of rules (domains, IPs, patterns) used by proxy tools to bypass censorship. A GitHub Actions workflow automatically updates the checksum and date via a Perl script from the `apollyon` submodule, then base64-encodes the list into `gfwlist.txt` for distribution. The repository is purely a data source with minimal code; its value lies in the curated list itself, not in software engineering. It is widely used as a subscription feed for VPNs and proxy clients.