Co-Pilot
Updated a month ago

amethyst

Vvitorpamplona
1.3k
vitorpamplona/amethyst
80
Agent Score

💡 Summary

Amethyst is a Nostr client for Android that enables users to control their social networking experience.

🎯 Target Audience

Android developers looking for a Nostr clientPrivacy-conscious users wanting to control their social interactionsTech enthusiasts exploring decentralized social networksUsers seeking an alternative to mainstream social media platforms

🤖 AI Roast:A social network app that promises privacy but still needs a VPN to keep your secrets safe.

Security AnalysisMedium Risk

The app stores sensitive user data, including private keys, which could be compromised if the device is lost or hacked. Implementing encryption and secure storage practices, such as using the Android KeyStore, can mitigate these risks.

Amethyst

Nostr Client for Android

Join the social network you control.

GitHub downloads PlayStore downloads

Last Version JitPack version CI License: Apache-2.0 Ask DeepWiki

Download and Install

Supported Features

  • [x] Events / Relay Subscriptions (NIP-01)
  • [x] Follow List (NIP-02)
  • [x] OpenTimestamps Attestations (NIP-03)
  • [x] Private Messages (NIP-04)
  • [x] DNS Address (NIP-05)
  • [x] Mnemonic seed phrase (NIP-06)
  • [ ] WebBrowser Signer (NIP-07, Not applicable)
  • [x] Old-style mentions (NIP-08)
  • [x] Event Deletion (NIP-09)
  • [x] Replies, mentions, Threads, and Notifications (NIP-10)
  • [x] Relay Information Document (NIP-11)
  • [x] Generic Tag Queries (NIP-12)
  • [x] Proof of Work Display (NIP-13)
  • [ ] Proof of Work Calculations (NIP-13)
  • [x] Events with a Subject (NIP-14)
  • [ ] Marketplace (NIP-15)
  • [x] Event Treatment (NIP-16)
  • [x] Private Direct Messages (NIP-17)
  • [x] Image/Video/Url/LnInvoice Previews
  • [x] Reposts, Quotes, Generic Reposts (NIP-18)
  • [x] Bech Encoding support (NIP-19)
  • [x] Command Results (NIP-20)
  • [x] URI Support (NIP-21)
  • [x] Long-form Content (NIP-23) (view only)
  • [x] User Profile Fields / Relay list (NIP-24)
  • [x] Reactions (NIP-25)
  • [ ] Delegated Event Signing (NIP-26, Will not implement)
  • [x] Text Note References (NIP-27)
  • [x] Public Chats (NIP-28)
  • [ ] Relay-based Groups (NIP-29)
  • [x] Custom Emoji (NIP-30)
  • [x] Event kind summaries (NIP-31)
  • [ ] Labeling (NIP-32)
  • [x] Parameterized Replaceable Events (NIP-33)
  • [x] Git Stuff (NIP-34)
  • [ ] Torrents (NIP-35)
  • [x] Sensitive Content (NIP-36)
  • [x] Edits (NIP-37/Draft)
  • [x] User Status Event (NIP-38)
  • [x] External Identities (NIP-39)
  • [x] Expiration Support (NIP-40)
  • [x] Relay Authentication (NIP-42)
  • [x] Versioned Encrypted Payloads (NIP-44)
  • [ ] Event Counts (NIP-45, Will not implement)
  • [ ] Nostr Connect (NIP-46)
  • [x] Wallet Connect API (NIP-47)
  • [ ] Proxy Tags (NIP-48, Not applicable)
  • [x] Private key encryption for import/export (NIP-49)
  • [x] Online Relay Search (NIP-50)
  • [x] Lists (NIP-51)
  • [ ] Calendar Events (NIP-52)
  • [x] Live Activities & Live Chats (NIP-53)
  • [x] Wiki (NIP-54)
  • [x] Inline Metadata (NIP-55 - Draft)
  • [x] Reporting (NIP-56)
  • [x] Lightning Tips
  • [x] Zaps (NIP-57)
  • [x] Private Zaps
  • [x] Zap Splits (NIP-57)
  • [x] Badges (NIP-58)
  • [x] Gift Wraps & Seals (NIP-59)
  • [x] Zapraiser (NIP-TBD)
  • [ ] Relay List Metadata (NIP-65)
  • [x] Polls (NIP-69)
  • [x] Video Events (NIP-71)
  • [x] Moderated Communities (NIP-72)
  • [ ] Zap Goals (NIP-75)
  • [x] Arbitrary Custom App Data (NIP-78)
  • [x] Highlights (NIP-84)
  • [x] Notify Request (NIP-88/Draft)
  • [x] Recommended Application Handlers (NIP-89)
  • [x] Data Vending Machine (NIP-90)
  • [x] Inline Metadata (NIP-92)
  • [x] Verifiable file URLs (NIP-94)
  • [x] Binary Blobs (NIP-95/Draft)
  • [x] HTTP File Storage Integration (NIP-96)
  • [x] HTTP Auth (NIP-98)
  • [x] Classifieds (NIP-99)
  • [x] Audio Tracks (zapstr.live) (kind:31337)
  • [x] Push Notifications (Google and Unified Push)
  • [x] In-Device Automatic Translations
  • [x] Hashtag Following and Custom Hashtags
  • [x] Login with QR
  • [x] Bounty support (nostrbounties.com)
  • [x] De-googled F-Droid flavor
  • [x] Multiple Accounts
  • [x] Markdown Support
  • [x] Medical Data (NIP-xx/Draft)
  • [x] Embed events (NIP-xx/Draft)
  • [x] Draft Events (NIP-xx/Draft)
  • [ ] Event Sets (NIP-xx/Draft)
  • [ ] Topical Notes (NIP-xx/Draft)
  • [ ] Relationship Status (NIP-xx/Draft)
  • [ ] Signed Filters (NIP-xx/Draft)
  • [ ] Key Migration (NIP-xx/Draft)
  • [ ] Time-based Sync (NIP-xx/Draft)
  • [x] Image Capture in the app
  • [x] Video Capture in the app
  • [ ] Local Database
  • [ ] Workspaces
  • [ ] Infinity Scroll

Privacy and Information Permanence

Relays know your IP address, your name, your location (guessed from IP), your pub key, all your contacts, and other relays, and can read every action you do (post, like, boost, quote, report, etc) except for Private Zaps and Private DMs. While the content of direct messages (DMs) is only visible to you and your DM counterparty, everyone can see when you and your counterparty DM each other.

If you want to improve your privacy, consider utilizing a service that masks your IP address (e.g. a VPN or Tor) from trackers online.

The relay also learns which public keys you are requesting, meaning your public key will be tied to your IP address.

Information shared on Nostr can be re-broadcasted to other servers and should be assumed permanent for privacy purposes. There is no way to guarantee the deletion of any content once posted.

Development Overview

This repository is split between Amethyst, Quartz, Commons, and DesktopApp:

  • Amethyst - Native Android app with Kotlin and Jetpack Compose
  • Quartz - Nostr-commons KMP library for protocol classes shared across platforms
  • Commons - Kotlin Multiplatform module with shared UI components (icons, robohash, blurhash, composables)
  • DesktopApp - Compose Multiplatform Desktop application reusing commons and quartz

The app architecture consists of the UI, which uses the usual State/ViewModel/Composition, the service layer that connects with Nostr relays, and the model/repository layer, which keeps all Nostr objects in memory, in a full OO graph.

The repository layer stores Nostr Events as Notes and Users separately. Those classes use LiveData and Flow objects to allow the UI and other parts of the app to subscribe to each Note/User and receive updates when they happen. They are also responsible for updating viewModels when needed. As the user scrolls through Events, the Datasource classes are updated to receive more information about those particular Events.

Most of the UI is reactive to changes in the repository classes. The service layer assembles Nostr filters for each need of the app, receives the data from the Relay, and sends it to the repository. Connection with relays is never closed during the use of the app. The UI receives a notification that objects have been updated. Instances of User and Notes are mutable directly. There will never be two Notes with the same ID or two User instances with the same pubkey.

Lastly, the user's account information (private key/pub key) is stored in the Android KeyStore for security.

Setup

Make sure to have the following pre-requisites installed:

  1. Java 21+
  2. Android Studio
  3. Android 8.0+ Phone or Emulation setup

Fork and clone this repository and import it into Android Studio

git clone https://github.com/vitorpamplona/amethyst.git

Use an Android Studio build action to install and run the app on your device or a simulator.

Building

Build the Android app:

./gradlew assembleDebug

Build and run the Desktop app (requires Java 21+):

./gradlew :desktopApp:run

Testing

./gradlew test ./gradlew connectedAndroidTest

Linting

./gradlew spotlessCheck ./gradlew spotlessApply

Installing on device

For the F-Droid build:

./gradlew installFdroidDebug

For the Play build:

./gradlew installPlayDebug

Deploying

  1. Generate a new signing key
keytool -genkey -v -keystore <my-release-key.keystore> -alias <alias_name> -keyalg RSA -keysize 2048 -validity 10000
openssl base64 < <my-release-key.keystore> | tr -d '\n' | tee some_signing_key.jks.base64.txt
  1. Create four Secret Key variables on your GitHub repository and fill in the signing key information
    • KEY_ALIAS <- <alias_name>
    • KEY_PASSWORD <- <your password>
    • KEY_STORE_PASSWORD <- <your key store password>
    • SIGNING_KEY <- the data from <my-release-key.keystore>
  2. Change the versionCode and versionName on amethyst/build.gradle
  3. Commit and push.
  4. Tag the commit with v{x.x.x}
  5. Let the [Create Release GitHub Action](https://github.com/vitorpamplona/amethyst/actions/workflows/create-re
5-Dim Analysis
Clarity8/10
Novelty8/10
Utility9/10
Completeness8/10
Maintainability7/10
Pros & Cons

Pros

  • Supports a wide range of Nostr features
  • Focus on user privacy and control
  • Active development and community support

Cons

  • Requires technical knowledge for setup
  • Privacy features depend on user actions
  • Limited documentation for advanced features

Related Skills

pytorch

S
toolCode Lib
92/ 100

“It's the Swiss Army knife of deep learning, but good luck figuring out which of the 47 installation methods is the one that won't break your system.”

agno

S
toolCode Lib
90/ 100

“It promises to be the Kubernetes for agents, but let's see if developers have the patience to learn yet another orchestration layer.”

nuxt-skills

S
toolCo-Pilot
90/ 100

“It's essentially a well-organized cheat sheet that turns your AI assistant into a Nuxt framework parrot.”

Disclaimer: This content is sourced from GitHub open source projects for display and rating purposes only.

Copyright belongs to the original author vitorpamplona.