Go to file
2023-08-30 13:07:48 -04:00
.cargo wasm fixes 2022-11-29 22:51:51 -05:00
dev-setup Fix setup_linux.sh to use scripts from the parent directory 2023-08-19 12:29:30 -04:00
doc network fixes 2023-07-19 10:07:51 -04:00
docs/guide Initial German translation of the guide document 2023-08-26 21:17:29 +00:00
external update submodules 2023-07-19 14:41:10 -04:00
files Add Test CA and simple certs for testing 2021-11-22 09:02:41 -05:00
package service restart if running, instructs to start if not 2023-07-17 20:55:45 -05:00
scripts Fix minor typos 2023-08-21 20:12:20 -05:00
veilid-cli veilid-server with Clap v4 2023-08-22 21:12:23 +00:00
veilid-core Merge branch 'fix-set-record-data-size-call' into 'main' 2023-08-27 16:07:38 +00:00
veilid-flutter flutter fix 2023-08-24 18:35:37 -04:00
veilid-python veilid-python: update_schema.sh now checks in a few places for veilid-server 2023-08-24 23:30:44 +00:00
veilid-server veilid-server with Clap v4 2023-08-22 21:12:23 +00:00
veilid-tools Version update: v0.1.9 → v0.1.10 2023-08-20 11:37:18 -05:00
veilid-wasm Redact usernames and user project structure from wasm panic messages 2023-08-30 13:07:48 -04:00
.bumpversion.cfg Version update: v0.1.9 → v0.1.10 2023-08-20 11:37:18 -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 Earthly Build Caching in GitLab Container Registry 2023-08-27 17:17:29 +00:00
.gitmodules make submodule path absolute 2023-08-18 01:13:09 -04:00
Cargo.lock flutter fix 2023-08-24 18:35:37 -04:00
Cargo.toml version bump 2023-07-16 14:35:51 -04:00
CHANGELOG.md add more changelog and clean up test output 2023-08-20 12:10:54 -04:00
code_of_conduct.md Add docs and mod version bumping 2023-08-01 21:37:38 -05:00
CONTRIBUTING.md Update CONTRIBUTING.md 2023-08-10 19:32:36 +00:00
DEVELOPMENT.md Update DEVELOPMENT.md to reflect new paths. 2023-08-18 09:27:17 -04:00
Earthfile Earthly Build Caching in GitLab Container Registry 2023-08-27 17:17:29 +00:00
INSTALL.md Update file INSTALL.md 2023-08-24 17:41:35 +00:00
LICENSE Add LICENSE 2023-08-10 19:34:50 +00:00
README-DE.md Initial German translation of the project readme file 2023-08-26 21:41:04 +00:00
README.md fix: README typos 2023-08-12 21:17:31 -07:00
RELEASING.md Revise release process 2023-08-19 17:19:17 -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