Padclaws is a Web client for the Nostr protocol. Specifically, the "Padclaws" name may refer to, either:
- The Padclaws software.
- The official public instance of the Padclaws software hosted at https://padclaws.org/.
The Padclaws software is implemented as a single-page static website using Vue. It's a simple folder of files. Hosting it requires nothing more than placing it behind any Web server. If hosting a public instance, make sure to set an appropriate privacy policy.
Padclaws is still in a rather messy stage of early development. Sometimes it might even work a bit. It's to be considered an individual project: it should match the preferences of one person: Valentino Giudice.
Padclaws is a client for Nostr. Censorship-resistant social networking through the decentralized publishing of text notes is the main goal of both and NIP-01 is their core specification.
Some additional functionalities are implemented, including:
- Follow lists (but without local petnames).
- Encoded entities and Nostr URIs.
- Basic interactions, such as reposts, replies and mentions.
The following functionalities are planned or to be considered:
- Direct messages.
- Reactions on notes.
- Autocomplete for mentions.
- Reddit-style moderated communities.
- Modifiable Markdown articles.
- Option to hide others' name.
- Manifest file to make Padclaws into a progressive Web application.
- Event signing delegation.
- Support for browser extensions (but login trough one's private key will still be allowed).
- Outbox model, but the inbox model of using a static relay list set by the user will still be the default.
The following functionalities will not be implemented:
- Anything that requires communicating with any server without being authorized to do so by the user. This includes DNS-based identifiers embedded images (including custom emojis).
- Anything to do with money or payments. This includes anything Bitcoin-related. It also includes marketplaces.
- Anything which, generally, significantly breaks the design or is out of scope in a social client.
In general, the design and development of Padcalws should follow the following guidelines:
- Robustness: Padclaws should comply with the latest version of the Nostr protocol in full and avoid deprecated practices, but expect that relays and other clients might not.
- Accessibility: Padclaws should be accessible to a wide range of people with disabilities, as well as usable in general. WCAG conformance at the AA level should be achieved.
- Privacy: Padclaws should not communicate with any server without being expressly instructed to do so by the user. No informations should be unexpectedly shared with any party.
- Security: Padclaws should be secure. Cryptographic libraries should be indepedently audited.
This software incorporates, in whole or in part, the following third-party assets:
- Vue, version 3.4.32, from unpkg.
- Vue Router, version 4.4.0, from unpkg.
- noble-curves, version 1.4.2, from GitHub releases.
- scure-base, version 1.1.7, bundled manually using esbuild.
- Regular Expression for URL validation, from the GitHub gist.
- Tabler Icons, version 3.11.0, extracted from official download.
- Atkinson Hyperlegible, from Google Fonts.
- Noto Color Emoji, from the GitHub repository.
- Programma, from the GitHub repository.
Check the projects above for their licensing information.
Excluding third-party assets (which are released under their repsective licenses), licenses and logos, this project is released under the MIT license.
All rights to icons, logos and the "Padclaws" name are reserved to Valentino Giudice.
This software is provided without warranty of any kind, see the license for more information. Use at your own risk.