Go to file
2023-09-16 19:58:04 -04:00
.cargo wasm fixes 2022-11-29 22:51:51 -05:00
dev-setup ensure setup_linux.sh isn't run as root 2023-09-11 10:12:26 -04:00
doc network fixes 2023-07-19 10:07:51 -04:00
docs/guide Fixed three typos. (Very minor, as the meaning was clear in any case.) 2023-08-28 05:26:54 +00:00
files Add Test CA and simple certs for testing 2021-11-22 09:02:41 -05:00
package Fix packaging version parsing 2023-09-02 10:50:58 -05:00
scripts android fixes 2023-09-01 15:36:43 -04:00
veilid-cli Version update: v0.2.0 → v0.2.1 2023-09-03 19:45:12 -05:00
veilid-core connection fix 2023-09-14 15:51:09 -04:00
veilid-flutter oops config 2023-09-14 14:21:54 -04:00
veilid-python Make Python README a bit more descriptive 2023-09-04 11:07:50 -05:00
veilid-server Version update: v0.2.0 → v0.2.1 2023-09-03 19:45:12 -05:00
veilid-tools dht fixes 2023-09-09 21:44:16 -04:00
veilid-wasm Replace .unwrap() with ? operator 2023-09-12 08:06:49 -04:00
.bumpversion.cfg Version update: v0.2.0 → v0.2.1 2023-09-03 19:45:12 -05:00
.earthlyignore add eartly build 2022-01-09 15:17:36 -05:00
.gitignore Ignore emacs backup files 2023-08-12 18:10:32 +02:00
.gitlab-ci.yml Switch unit tests back to manual execution 2023-09-04 14:41:34 +00:00
build_docs.bat Add Windows build_docs script 2023-09-10 16:15:50 -04:00
build_docs.sh doc work 2023-08-27 16:39:50 -05:00
Cargo.lock (wasm) basic working unit tests 2023-09-04 22:13:58 -04:00
Cargo.toml ensure resolver version is set for workspace for newer rust to suppress warnings 2023-09-16 19:58:04 -04:00
CHANGELOG.md CI config and Changelog tweaks 2023-09-03 19:43:46 -05:00
code_of_conduct.md Fix a couple markdownlint issues, no change to content. 2023-09-10 16:32:38 -04:00
CONTRIBUTING.md fix markdownlint warnings in CONTRIBUTING.md 2023-09-12 13:06:11 +00:00
DEVELOPMENT.md Cleaned up .md files syntax 2023-09-12 08:43:09 -05:00
Earthfile Merge branch 'fix-earthfile' into 'main' 2023-09-03 00:28:17 +00:00
INSTALL.md Cleaned up .md files syntax 2023-09-12 08:43:09 -05:00
LICENSE Add LICENSE 2023-08-10 19:34:50 +00:00
README-DE.md Cleaned up .md files syntax 2023-09-12 08:43:09 -05:00
README.md Cleaned up .md files syntax 2023-09-12 08:43:09 -05:00
RELEASING.md Cleaned up .md files syntax 2023-09-12 08:43:09 -05:00
version_bump.sh version 2023-07-19 13:01:55 -04:00

Welcome to Veilid

From Orbit

The first matter to address is the question "What is Veilid?" The highest-level description is that Veilid is a peer-to-peer network for easily sharing various kinds of data.

Veilid is designed with a social dimension in mind, so that each user can have their personal content stored on the network, but also can share that content with other people of their choosing, or with the entire world if they want.

The primary purpose of the Veilid network is to provide the infrastructure for a specific kind of shared data: social media in various forms. That includes light-weight content such as Twitter's tweets or Mastodon's toots, medium-weight content like images and songs, and heavy-weight content like videos. Meta-content such as personal feeds, replies, private messages, and so forth are also intended to run atop Veilid.

Run a Node

The easiest way to help grow the Veilid network is to run your own node. Every user of Veilid is a node, but some nodes help the network more than others. These network support nodes are heavier than the node a user would establish on their phone in the form of a chat or social media application. A cloud based virtual private server (VPS), such as Digital Ocean Droplets or AWS EC2, with high bandwidth, processing resources, and up time availability is crucial for building the fast, secure, and private routing that Veilid is built to provide.

To run such a node, establish a Debian or Fedora based VPS and install the veilid-server service. To make this process simple we are hosting package manager repositories for .deb and .rpm packages. See the installing guide for more information.

Development

If you're inclined to get involved in code and non-code development, please check out the contributing guide. We're striving for this project to be developed in the open and by people for people. Specific areas in which we are looking for help include:

  • Rust
  • Flutter/Dart
  • Python
  • Gitlab DevOps and CI/CD
  • Documentation
  • Security reviews
  • Linux packaging