mirror of
https://gitlab.com/veilid/veilid-dot-com.git
synced 2025-03-23 15:46:31 -04:00
pre vegas site changes
This commit is contained in:
Alice Rhodes
parent
d56fcd4943
commit
31f47294bf
pages-old
chat
contribute
defcon-2023
docs
donate.mddownload.de.mddownload.mdindex.de.mdindex.mdtranslations.mdweb-text.mdpages
staged.mdstatic/img
themes/veilid
25
pages-old/chat/index.md
Normal file
25
pages-old/chat/index.md
Normal file
@ -0,0 +1,25 @@
|
||||
---
|
||||
title: VeilidChat
|
||||
description: VeilidChat is a proof of concept of the Veilid protocol and framework.
|
||||
menu:
|
||||
main:
|
||||
weight: 5
|
||||
weight: 1
|
||||
layout: subpage
|
||||
---
|
||||
|
||||
VeilidChat is a demo of the Veilid framework and protocol working.
|
||||
|
||||
We built it using the [Flutter](https://flutter.dev/) framework and the Veilid core code.
|
||||
|
||||
If you want to try out this proof of concept, please stay tuned for details on how to gain access.
|
||||
|
||||
### Source Code
|
||||
|
||||
VeilidChat is under active development. The source code is available on [Gitlab](https://gitlab.com/veilid/veilidchat), though there are no official builds yet.
|
||||
|
||||
|
||||
### Support
|
||||
|
||||
<p>For app support, please email <a href="mailto:support@veilid.com">support@veilid.com</a></p>
|
||||
|
||||
188
pages-old/chat/privacy-policy.md
Normal file
188
pages-old/chat/privacy-policy.md
Normal file
@ -0,0 +1,188 @@
|
||||
---
|
||||
title: Privacy Policy
|
||||
description: The privacy policy for VeilidChat
|
||||
weight: 2
|
||||
layout: subpage
|
||||
---
|
||||
|
||||
### VeilidChat Privacy Policy
|
||||
|
||||
Last Revised 2023 Aug 3
|
||||
|
||||
This privacy notice for the Veilid Foundation ("Veilid," "we," "us," or "our"), describes how and why we might collect, store, use, and/or share ("process") your information when you use our services ("Services"), such as when you:
|
||||
|
||||
- Download and use our mobile application (VeilidChat), or any other application of ours that links to this privacy notice in the future.
|
||||
|
||||
Reading this privacy notice will help you understand your privacy rights and choices. If you do not agree with our policies and practices, please do not use VeilidChat. If you still have any questions or concerns, please contact us at [support@veilid.com](mailto:support@veilid.com).
|
||||
|
||||
<h4 id="summary">Summary of Key Points</h4>
|
||||
|
||||
- VeilidChat is a messaging application built on a decentralized, distributed, and end-to-end fully encrypted framework.
|
||||
- VeilidChat is a proof-of-concept application in beta-testing and you must receive an invitation to activate the application.
|
||||
- VeilidChat will never ask you for contact information, personal information, or financial information.
|
||||
- When you register and use VeilidChat, any information entered into the app is either stored locally on your device, or encrypted and distributed in a method that is inaccessible and irretrievable by the Veilid Foundation (the creators of the application).
|
||||
- We do not collect or process any personal information, nor do we have the capability to collect or process any personal information from VeilidChat.
|
||||
- We do not collect or process sensitive personal information, nor do we have the capability to collect or process any sensitive information from VeilidChat.
|
||||
- We do not receive or transmit any information to or from third parties.
|
||||
- The Veilid Framework processes encrypted and distributed information to provide and administer services for VeilidChat.
|
||||
- We do not share personal information. Because of the encrypted and distributed nature of information entered into the VeilidChat app, we are unable to access your personal information.
|
||||
- How do we keep your information safe? We have organizational and technical processes and procedures in place to protect your personal information. However, no electronic transmission over the internet or information storage technology can be guaranteed to be 100% secure, so we cannot promise or guarantee that unauthorized third parties will not be able to defeat our security and improperly collect, access, steal, or modify your information.
|
||||
- VeilidChat will provide you with a recovery pass-phrase to use in the event that your app is deleted or your device is no longer available/functional for you. If you cannot access this pass-phrase, you will have to create a new account. The Veilid Foundation is unable to restore your account through any means.
|
||||
- How do you exercise your rights? The easiest way to exercise your rights is to delete VeilidChat. The Veilid Foundation is a non-profit organization that does not collect, process, or use any of your information. You may contact us by visiting https://veilid.com/contact, or by emailing [support@veilid.com](mailto:support@veilid.com). We will consider and act upon any request in accordance with applicable data protection laws.
|
||||
|
||||
<h4 id="table-of-contents">Table of Contents</h4>
|
||||
|
||||
1. [What Information Do We Collect?](#section-1)
|
||||
1. [How Do We Process Your Information?](#section-2)
|
||||
1. [What Legal Bases Do We Rely On To Process Your Personal Information?](#section-3)
|
||||
1. [When And With Whom Do We Share Your Personal Information?](#section-4)
|
||||
1. [How Long Do We Keep Your Information?](#section-5)
|
||||
1. [How Do We Keep Your Information Safe?](#section-6)
|
||||
1. [Do We Collect Information From Minors?](#section-7)
|
||||
1. [What Are Your Privacy Rights?](#section-8)
|
||||
1. [Controls For Do-not-track Features](#section-9)
|
||||
1. [US State-specific Privacy Rights](#section-10)
|
||||
1. [Do We Make Updates To This Notice?](#section-11)
|
||||
1. [How Can You Contact Us About This Notice?](#section-12)
|
||||
1. [How Can You Review, Update, Or Delete The Data We Collect From You?](#section-13)
|
||||
1. [Cookie And Data Analytics Disclosures](#section-14)
|
||||
|
||||
<h4 id="section-1">1. What information do we collect?</h4>
|
||||
|
||||
VeilidChat collects no information from you. VeilidChat is designed to not collect your information and to operate in an encrypted, distributed manner, which means we cannot access your information even if we wanted to (which we don’t). Any information you enter into VeilidChat on your device is inaccessible to us.
|
||||
|
||||
The Veilid Foundation only collects personal information that you voluntarily provide to us when you request an invitation to the beta version of the application. This will only be the contact information necessary for us to send you an invitation. This process is managed by the Apple App Store and the Veilid Foundation only retains this information long enough to provide it to the Apple App Store to generate an invitation.
|
||||
|
||||
<h4 id="section-2">2. How do we process your information?</h4>
|
||||
|
||||
We don’t. VeilidChat does not collect your information, nor are we able to collect it. Administration of, improvements to, and changes to the VeilidChat application will be made without any processing of personal information. The Veilid Foundation will never ask you for personal, sensitive, or financial information.
|
||||
|
||||
If you provide any information to us at [support@veilid.com](mailto:support@veilid.com), though our Discord server, through our website at https://veilid.com/contact, or directly via postal mail to our foundation, we will only process that information to answer your questions or attempt to support your issues, with two major exceptions:
|
||||
|
||||
- Legal Obligations. We may process information sent to us via email, our website, or via postal mail where we believe it is necessary for compliance with our legal obligations, such as to cooperate with a law enforcement body or regulatory agency, exercise or defend our legal rights, or disclose your information as evidence in litigation in which we are involved.
|
||||
- Vital Interests. We may process information sent to us via email, our website, or via postal mail where we believe it is necessary to protect your vital interests or the vital interests of a third party, such as situations involving potential threats to the safety of any person.
|
||||
|
||||
<h4 id="section-3">3. What legal bases do we rely on to process uour information?</h4>
|
||||
|
||||
VeilidChat does not process any personal information. Because the Veilid Foundation cannot access information entered into VeilidChat in any way, shape, or form, the Veilid Foundation does not process your information.
|
||||
|
||||
As for information sent to the Veilid Foundation via email, Discord server, postal mail, or through our website, we only process your personal information when we believe it is necessary and we have a valid legal reason (i.e.,legal obligations) to do so under applicable law, to comply with laws, to protect your rights, or to fulfill our legitimate business interests.
|
||||
|
||||
<strong>If you are located in the EU or UK, this section applies to you.</strong>
|
||||
|
||||
The General Data Protection Regulation (GDPR) and UK GDPR require us to explain the valid legal bases we rely on in order to process your personal information. VeilidChat does not collect or process personal information. For any information that is sent directly to the Veilid Foundation, we may rely on the following legal bases to process your personal information:
|
||||
|
||||
- Consent. The Veilid Foundation may process your information if you have given us specific permission (i.e. consent) to use your personal information for a specific purpose. This is generally limited to contacting us and requesting an invite code to the beta version of the application, however, the Veilid Foundation does not store this information. Apple, through the App Store, will manage the invitation process. Your contact information cannot be linked to your VeilidChat account by the Veilid Foundation. You can withdraw your consent to Apple at any time.
|
||||
- Legal Obligations. We may process your information where we believe it is necessary for compliance with our legal obligations, such as to cooperate with a law enforcement body or regulatory agency, exercise or defend our legal rights, or disclose your information as evidence in litigation in which we are involved.
|
||||
- Vital Interests. We may process your information where we believe it is necessary to protect your vital interests or the vital interests of a third party, such as situations involving potential threats to the safety of any person.
|
||||
|
||||
<strong>If you are located in Canada, this section applies to you.</strong>
|
||||
|
||||
VeilidChat does not collect or process personal information. For any information that is sent directly to the Veilid Foundation, we may rely on the following legal bases to process your personal information:
|
||||
|
||||
We may process your information if you have given us specific permission (i.e., express consent) to use your personal information for a specific purpose, or in situations where your permission can be inferred (i.e., implied consent). This is generally limited to contacting us and requesting an invite code to the beta version of the application. Apple, through the App Store, will manage the invitation process. Your contact information cannot be linked to your VeilidChat account by the Veilid Foundation. You can withdraw your consent to Apple at any time.
|
||||
|
||||
- In some exceptional cases, we may be legally permitted under applicable law to process your information without your consent, including, for example:
|
||||
- If collection is clearly in the interests of an individual and consent cannot be obtained in a timely way
|
||||
- For investigations and fraud detection and prevention
|
||||
- If it is contained in a witness statement and the collection is necessary to assess, process, or settle an insurance claim
|
||||
- For identifying injured, ill, or deceased persons and communicating with next of kin
|
||||
- If we have reasonable grounds to believe an individual has been, is, or may be victim of financial abuse
|
||||
- If it is reasonable to expect collection and use with consent would compromise the availability or the accuracy of the information and the collection is reasonable for purposes related to investigating a breach of an agreement or a contravention of the laws of Canada or a province
|
||||
- If disclosure is required to comply with a subpoena, warrant, court order, or rules of the court relating to the production of records
|
||||
- If it was produced by an individual in the course of their employment, business, or profession and the collection is consistent with the purposes for which the information was produced
|
||||
- If the collection is solely for journalistic, artistic, or literary purposes
|
||||
- If the information is publicly available and is specified by the regulations
|
||||
|
||||
|
||||
<h4 id="section-4">4. When and with whom do we share your personal information?</h4>
|
||||
|
||||
In no way, shape, or form do we ever share your personal information. We cannot share what we do not retain, or what we cannot access.
|
||||
|
||||
- Business Transfers. In the event of any merger, sale, or acquisition of any portion of the Veilid Foundation, the Veilid Foundation will provide updates on our website or through application updates for the VeilidChat application through the App Store. Because the Velid Foundation does not collect any personal information, we have no other methods to provide this information to you.
|
||||
|
||||
<h4 id="section-5">5. How long do we keep your information?</h4>
|
||||
|
||||
We keep your information for as long as necessary to fulfill the purposes outlined in this privacy notice unless otherwise required by law. However, in most cases, we are incapable of retaining information because we do not collect it.
|
||||
|
||||
The Veilid Foundation will only keep your personal information for as long as it is necessary for the purposes set out in this privacy notice, unless a longer retention period is required by law. VeilidChat will retain a local copy of your information (accessible only to your device and the people you directly share information with) for as long as you utilize the application. In future iterations of the application, there will be a “delete messages after a certain period of time” functionality, but for the beta testing proof-of-concept, this functionality has not been introduced.
|
||||
|
||||
<h4 id="section-6">6. How do we keep your information safe?</h4>
|
||||
|
||||
We have implemented appropriate and reasonable technical and organizational security measures designed to protect the security of any personal information we process. However, despite our safeguards and efforts to secure your information, no electronic transmission over the Internet or information storage technology can be guaranteed to be 100% secure, so we cannot promise or guarantee that any unauthorized third parties will not be able to defeat our security and improperly collect, access, steal, or modify your information.
|
||||
|
||||
Although we will do our best to protect your personal information, transmission of personal information to and from Velid Chat is at your own risk. You should only access VeilidChat within a secure environment. If you lose access to your device, the Velid Foundation cannot access or delete information stored there.
|
||||
|
||||
|
||||
<h4 id="section-7">7. Do we collect information from minors?</h4>
|
||||
|
||||
We do not collect information from or market to anyone. If you suspect that someone underage is violating the Apple App Store terms of service by downloading VeilidChat, please contact Apple at Support.Apple.com.
|
||||
|
||||
<h4 id="section-8">8. What are your privacy rights?</h4>
|
||||
|
||||
In some regions (like the EEA, UK, and Canada), you have certain rights under applicable data protection laws. These may include the right (i) to request access and obtain a copy of your personal information, (ii) to request rectification or erasure; (iii) to restrict the processing of your personal information; and (iv) if applicable, to data portability. In certain circumstances, you may also have the right to object to the processing of your personal information.
|
||||
|
||||
However, due to the unique nature of VeilidChat, the only information available is stored locally on the user’s device and is inaccessible by the Veilid Foundation. VeilidChat does not collect or process any personal information. If a user wishes to exercise their data rights, they may copy any data within the VeilidChat application and export it themselves, or delete the application from their device. The Veilid Foundation has no access to any user’s data.
|
||||
|
||||
We will consider and act upon any request in accordance with applicable data protection laws.
|
||||
|
||||
If you are located in the EEA or UK and you believe we are unlawfully processing your personal information, you also have the right to complain to your Member State data protection authority or UK data protection authority.
|
||||
|
||||
If you are located in Switzerland, you may contact the Federal Data Protection and Information Commissioner.
|
||||
|
||||
##### Account Information
|
||||
|
||||
If you would at any time like to review or change the information in your account or terminate your account, you can:
|
||||
|
||||
- Log in to your account settings and update your user account.
|
||||
- Delete the application from your device.
|
||||
|
||||
Upon your decision to delete the application from your device, it will no longer be able to be accessed by anyone, including the creators of the application. Any data still in existence will be encrypted, distributed, and inaccessible by any party.
|
||||
|
||||
However, we may retain some information that is sent directly to the Veilid Foundation via email, our website, our Discord server, or via post mail in our files to prevent fraud, troubleshoot problems, assist with any investigations, enforce our legal terms and/or comply with applicable legal requirements.
|
||||
|
||||
If you have questions or comments about your privacy rights, you may email us at [support@veilid.com](mailto:support@veilid.com).
|
||||
|
||||
|
||||
<h4 id="section-9">9. Controls for Do-Not-track Features</h4>
|
||||
|
||||
Most web browsers and some mobile operating systems and mobile applications include a Do-Not-Track ("DNT") feature or setting you can activate to signal your privacy preference not to have data about your online browsing activities monitored and collected. VeilidChat is compliant with this technology because we do not monitor, track, collect, or process any information.
|
||||
|
||||
|
||||
<h4 id="section-10">10. US State-Specific Privacy Rights</h4>
|
||||
|
||||
- California (knows how to party):
|
||||
- We do not sell, rent, or share information with anyone, including third parties who engage in direct marketing activities. We do not collect or share your information with anyone, for any reason. No marketing, no third party sharing, nothing.
|
||||
- VeilidChat has no ability to post public information. If you are under 18 years of age, reside in California, and have a registered account with VeilidChat, you can delete the application on your device and that will serve to exercise your rights to deletion.
|
||||
- Please note that the Veilid Foundation and the VeilidChat application HAVE NOT collected, rented, shared, or sold any personal information from any individual, and especially not within the past 12 months.
|
||||
- De-identified Data Disclosure (CA, CO, CT, UT, VA and soon to be more)
|
||||
- We may use de-identified data in certain circumstances. In those circumstances, not only do we never attempt to re-identify that data, but we are completely unable to re-identify any data because of our encryption and distributed data frameworks.
|
||||
- Profiling Disclosure (Hi Colorado!)
|
||||
- We do not engage in profiling of consumers in any way, shape, or form. We especially don’t do it in a way that supports automated decisions that might have a legal or significant effect on anyone.
|
||||
|
||||
|
||||
<h4 id="section-11">11. Do we make updates to this notice?</h4>
|
||||
|
||||
We will update this notice as necessary to stay compliant with relevant laws and as it relates to new features or products available.
|
||||
|
||||
The updated version will be indicated by an updated "Revised" date and the updated version will be effective as soon as it is accessible. If we make material changes to this privacy notice, we may notify you either by prominently posting a notice of such changes on the Veilid Foundation’s website, or by providing an updated policy through the Apple App Store as part of any version updates. Because we do not collect your information, we are unable to directly contact you. We encourage you to review this privacy notice frequently to be informed of how we are protecting your information.
|
||||
|
||||
<h4 id="section-12">12. How can you contact us about this notice?</h4>
|
||||
|
||||
If you have questions or comments about this notice, you may email us at [support@veilid.com](mailto:support@veilid.com) or contact us by post at:
|
||||
|
||||
<pre>
|
||||
Veilid Foundation
|
||||
P.O. Box 1917
|
||||
Leesburg, VA 20177
|
||||
</pre>
|
||||
|
||||
|
||||
<h4 id="section-13">13. How can you review, update, or delete the data we collect from you?</h4>
|
||||
|
||||
The only effective method to review, update, or delete any of your data is locally on the VeilidChat application on your device. The Veilid Foundation is unable to collect or access your information through the VeilidChat application and thus does not have the ability to review, update, or delete information that we do not possess.
|
||||
|
||||
|
||||
<h4 id="section-14">14. Cookie and Data Analytics Disclosure</h4>
|
||||
|
||||
We don’t use cookies. We don’t use data analytics. You can check on our website.
|
||||
142
pages-old/contribute/code-of-conduct.md
Normal file
142
pages-old/contribute/code-of-conduct.md
Normal file
@ -0,0 +1,142 @@
|
||||
---
|
||||
title: Code of Conduct
|
||||
description: Veilid community and developer code of conduct
|
||||
weight: 2
|
||||
layout: subpage
|
||||
---
|
||||
|
||||
Our code of conduct on the Contributor Covenant Code of Conduct and will be updated as needed.
|
||||
|
||||
Questions, comments, or concerns about the code of conduct may be sent to
|
||||
<a href="mailto:security@veilid.org">security@veilid.org</a>.
|
||||
|
||||
## Our Pledge
|
||||
|
||||
We as members, contributors, and leaders pledge to make participation in our
|
||||
community a harassment-free experience for everyone, regardless of age, body
|
||||
size, visible or invisible disability, ethnicity, sex characteristics, gender
|
||||
identity and expression, level of experience, education, socio-economic status,
|
||||
nationality, personal appearance, race, caste, color, religion, or sexual
|
||||
identity and orientation.
|
||||
|
||||
We pledge to act and interact in ways that contribute to an open, welcoming,
|
||||
diverse, inclusive, and healthy community.
|
||||
|
||||
## Our Standards
|
||||
|
||||
Examples of behavior that contributes to a positive environment for our
|
||||
community include:
|
||||
|
||||
* Demonstrating empathy and kindness toward other people
|
||||
* Being respectful of differing opinions, viewpoints, and experiences
|
||||
* Giving and gracefully accepting constructive feedback
|
||||
* Accepting responsibility and apologizing to those affected by our mistakes,
|
||||
and learning from the experience
|
||||
* Focusing on what is best not just for us as individuals, but for the overall
|
||||
community
|
||||
|
||||
Examples of unacceptable behavior include:
|
||||
|
||||
* The use of sexualized language or imagery, and sexual attention or advances of
|
||||
any kind
|
||||
* Trolling, insulting or derogatory comments, and personal or political attacks
|
||||
* Public or private harassment
|
||||
* Publishing others' private information, such as a physical or email address,
|
||||
without their explicit permission
|
||||
* Other conduct which could reasonably be considered inappropriate in a
|
||||
professional setting
|
||||
|
||||
## Enforcement Responsibilities
|
||||
|
||||
Community leaders are responsible for clarifying and enforcing our standards of
|
||||
acceptable behavior and will take appropriate and fair corrective action in
|
||||
response to any behavior that they deem inappropriate, threatening, offensive,
|
||||
or harmful.
|
||||
|
||||
Community leaders have the right and responsibility to remove, edit, or reject
|
||||
comments, commits, code, wiki edits, issues, and other contributions that are
|
||||
not aligned to this Code of Conduct, and will communicate reasons for moderation
|
||||
decisions when appropriate.
|
||||
|
||||
## Scope
|
||||
|
||||
This Code of Conduct applies within all community spaces, and also applies when
|
||||
an individual is officially representing the community in public spaces.
|
||||
Examples of representing our community include using an official e-mail address,
|
||||
posting via an official social media account, or acting as an appointed
|
||||
representative at an online or offline event.
|
||||
|
||||
## Enforcement
|
||||
|
||||
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
||||
reported to the community leaders responsible for enforcement at [security@veilid.org](mailto:security@veilid.org).
|
||||
All complaints will be reviewed and investigated promptly and fairly.
|
||||
|
||||
All community leaders are obligated to respect the privacy and security of the
|
||||
reporter of any incident.
|
||||
|
||||
## Enforcement Guidelines
|
||||
|
||||
Community leaders will follow these Community Impact Guidelines in determining
|
||||
the consequences for any action they deem in violation of this Code of Conduct:
|
||||
|
||||
### 1. Correction
|
||||
|
||||
**Community Impact**: Use of inappropriate language or other behavior deemed
|
||||
unprofessional or unwelcome in the community.
|
||||
|
||||
**Consequence**: A private, written warning from community leaders, providing
|
||||
clarity around the nature of the violation and an explanation of why the
|
||||
behavior was inappropriate. A public apology may be requested.
|
||||
|
||||
### 2. Warning
|
||||
|
||||
**Community Impact**: A violation through a single incident or series of
|
||||
actions.
|
||||
|
||||
**Consequence**: A warning with consequences for continued behavior. No
|
||||
interaction with the people involved, including unsolicited interaction with
|
||||
those enforcing the Code of Conduct, for a specified period of time. This
|
||||
includes avoiding interactions in community spaces as well as external channels
|
||||
like social media. Violating these terms may lead to a temporary or permanent
|
||||
ban.
|
||||
|
||||
### 3. Temporary Ban
|
||||
|
||||
**Community Impact**: A serious violation of community standards, including
|
||||
sustained inappropriate behavior.
|
||||
|
||||
**Consequence**: A temporary ban from any sort of interaction or public
|
||||
communication with the community for a specified period of time. No public or
|
||||
private interaction with the people involved, including unsolicited interaction
|
||||
with those enforcing the Code of Conduct, is allowed during this period.
|
||||
Violating these terms may lead to a permanent ban.
|
||||
|
||||
### 4. Permanent Ban
|
||||
|
||||
**Community Impact**: Demonstrating a pattern of violation of community
|
||||
standards, including sustained inappropriate behavior, harassment of an
|
||||
individual, or aggression toward or disparagement of classes of individuals.
|
||||
|
||||
**Consequence**: A permanent ban from any sort of public interaction within the
|
||||
community.
|
||||
|
||||
## Attribution
|
||||
|
||||
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
|
||||
version 2.1, available at
|
||||
[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
|
||||
|
||||
Community Impact Guidelines were inspired by
|
||||
[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
|
||||
|
||||
For answers to common questions about this code of conduct, see the FAQ at
|
||||
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
|
||||
[https://www.contributor-covenant.org/translations][translations].
|
||||
|
||||
[homepage]: https://www.contributor-covenant.org
|
||||
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
|
||||
[Mozilla CoC]: https://github.com/mozilla/diversity
|
||||
[FAQ]: https://www.contributor-covenant.org/faq
|
||||
[translations]: https://www.contributor-covenant.org/translations
|
||||
|
||||
49
pages-old/contribute/index.md
Normal file
49
pages-old/contribute/index.md
Normal file
@ -0,0 +1,49 @@
|
||||
---
|
||||
title: Contribute
|
||||
description: Learn about all the ways you can help Veilid
|
||||
menu:
|
||||
main:
|
||||
weight: 6
|
||||
weight: 1
|
||||
layout: subpage
|
||||
---
|
||||
|
||||
### How You Can Help
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<h4>Coders And Hackers</h4>
|
||||
We can use more low-level programmers and protocol experts. Platform experts.
|
||||
We want this system to work well for everyone and be a strong foundation for
|
||||
general computing and application development.
|
||||
</li>
|
||||
<li>
|
||||
<h4>App Developers</h4>
|
||||
You can get started writing a Veilid app today! Got a game idea? Want to port
|
||||
something from a centralized system to a decentralized one? Let’s make this happen!
|
||||
</li>
|
||||
<li>
|
||||
<h4>Usability Experts</h4>
|
||||
We want to make sure that the framework and apps built with it are accessible to everyone.
|
||||
Everyone should be able to make use of Veilid without even realizing they’re doing it.
|
||||
</li>
|
||||
<li>
|
||||
<h4>Translators</h4>
|
||||
Veilid technology is for everyone. Help us reach more people by helping us make sure as
|
||||
many people as possible can read the documentation and use the applications.
|
||||
</li>
|
||||
<li>
|
||||
<h4>Open Source and Governance</h4>
|
||||
Open source projects deserve to be managed in the open too. We’ve got an open RFC process for our design and an MPL-2.0 license that ensures that free and commercial entities can contribute safely and legally.
|
||||
</li>
|
||||
<li>
|
||||
<h4><span title="Donations, but spell with a dollar sign for the letter s">Donation$</span></h4>
|
||||
Cash works, too. Donations are tax-deductible. <a href="/give">Support Veilid</a>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
### Get Started
|
||||
|
||||
Please read our <a href="/contribute/code-of-conduct/">Code of Conduct</a> and then join us on our discord.
|
||||
|
||||
<a href="/discord" class="btn btn-primary btn-lg">Veilid Discord</a>
|
||||
45
pages-old/donate.md
Normal file
45
pages-old/donate.md
Normal file
@ -0,0 +1,45 @@
|
||||
---
|
||||
title: Donate
|
||||
description: Help support Veilid by gifting a tax-deductible donation
|
||||
menu:
|
||||
main:
|
||||
weight: 10
|
||||
layout: index
|
||||
---
|
||||
|
||||
<div class="row g-5">
|
||||
<div class="col-12 col-md-7">
|
||||
<p>
|
||||
Veilid Foundation was formed to develop, distribute, and maintain a privacy focused
|
||||
communication platform and protocol for the purposes of defending human and civil rights.
|
||||
</p>
|
||||
<p>
|
||||
Supporting us in this mission helps ensure the Veilid framework gets the support and defense
|
||||
it needs to protect your privacy.
|
||||
</p>
|
||||
<p>
|
||||
You have a very real chance at private, secure, and accessible communication tools.
|
||||
</p>
|
||||
<p>
|
||||
You can escape the data economy and help others do the same. You don't have to be the product.
|
||||
</p>
|
||||
</div>
|
||||
<div class="col-12 col-md-5">
|
||||
<div class="focus-text">
|
||||
<p>
|
||||
Veilid Foundation Inc is a registered 501c3 non-profit organization; your donations are tax-deductible.
|
||||
</p>
|
||||
</div>
|
||||
<p>You can learn more at <a href="https://veilid.org">Veilid.org</a></p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="d-flex flex-column mt-5">
|
||||
<p class="small-warning order-2">
|
||||
Donations are collected via Stripe; clicking this link will open a new window or tab.
|
||||
</p>
|
||||
<p class="order-1">
|
||||
<a target="_blank" href="/give" class="btn btn-lg btn-success text-white w-100">Support Veilid Today</a>
|
||||
</p>
|
||||
</div>
|
||||
|
||||
@ -6,6 +6,7 @@ menu:
|
||||
weight: 1
|
||||
layout: index
|
||||
language: de
|
||||
exclude: true
|
||||
---
|
||||
|
||||
|
||||
71
pages-old/index.md
Normal file
71
pages-old/index.md
Normal file
@ -0,0 +1,71 @@
|
||||
---
|
||||
title: Take Back Control
|
||||
description: Veilid is an open-source, distributed application framework.
|
||||
menu:
|
||||
main:
|
||||
weight: 1
|
||||
layout: index
|
||||
---
|
||||
<p class="focus-text highlighted">
|
||||
Veilid is an
|
||||
<span class="highlighter-1">open-source</span>,
|
||||
<span class="highlighter-2">peer-to-peer</span>,
|
||||
<span class="highlighter-3">mobile-first</span>,
|
||||
<span class="highlighter-4">networked</span>
|
||||
application framework.
|
||||
</p>
|
||||
|
||||
<p>Veilid (pronounced Vay-Lid, from 'Valid and Veiled Identification')</p>
|
||||
<p>
|
||||
Veilid allows anyone to build a distributed, private app. Veilid gives users the privacy to opt out of
|
||||
data collection and online tracking. Veilid is being built with user experience, privacy, and safety as our top priorities.
|
||||
It is open source and available to everyone to use and build upon.
|
||||
</p>
|
||||
<p>
|
||||
Veilid goes above and beyond existing privacy technologies and has the potential to completely change the way
|
||||
people use the Internet. Veilid has no profit motive, which puts us in a unique position to promote ideals
|
||||
without the compromise of capitalism.
|
||||
</p>
|
||||
<p class="focus-text">
|
||||
We built Veilid because when the Internet was young and new, we viewed it as an endless and open realm of possibility.
|
||||
</p>
|
||||
<p>
|
||||
Instead, the Internet we know now has been heavily commercialized, with users and their data being the most
|
||||
sought-after commodity. The only ways to opt-out of becoming the product for billionaires to exploit are either
|
||||
too technical for the average user, or to simply not go online.
|
||||
</p>
|
||||
<p>
|
||||
We don't believe that is fair; we still haven't given up our dream for the entire Internet to be free
|
||||
and accessible without trading privacy to use it.
|
||||
</p>
|
||||
<p class="focus-text">
|
||||
We believe that everyone should be able to forge relationships, learn, create, and build online — without being monetized.
|
||||
</p>
|
||||
<p>
|
||||
With Veilid, the user is in control, in a way that is approachable and friendly, regardless of technical
|
||||
ability. We want to give the world the Internet we should have had all along.
|
||||
</p>
|
||||
|
||||
|
||||
|
||||
<div class="row gx-5 gy-3 mt-5">
|
||||
<div class="col-12 col-md-6 col-lg-3">
|
||||
<a class="btn btn-info btn-lg w-100" href="/docs/overview/">Technical Details</a>
|
||||
</div>
|
||||
<div class="col-12 col-md-6 col-lg-3">
|
||||
<a class="btn bgv-fuschia btn-lg w-100" href="/chat">VeilidChat</a>
|
||||
</div>
|
||||
<div class="col-12 col-md-6 col-lg-3">
|
||||
<a class="btn btn-dark btn-lg w-100" href="/code">Code</a>
|
||||
</div>
|
||||
<div class="col-12 col-md-6 col-lg-3">
|
||||
<a class="btn btn-primary btn-lg w-100" href="/discord">Discord</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="row gx-5 gy-3 mt-3 justify-content-center">
|
||||
<div class="col-12 col-md-6">
|
||||
<a class="btn btn-success btn-lg w-100 text-white" href="/donate">Donate</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
30
pages-old/translations.md
Normal file
30
pages-old/translations.md
Normal file
@ -0,0 +1,30 @@
|
||||
---
|
||||
title: Translations
|
||||
description: Help translate documentation and more for the Veilid project
|
||||
layout: index
|
||||
exclude: true
|
||||
---
|
||||
|
||||
|
||||
<div class="row g-5">
|
||||
<div class="col-12 col-md-7">
|
||||
<p>
|
||||
We are very early on in this project and currently only have our text in English.
|
||||
</p>
|
||||
<p>
|
||||
We are seeking volunteers to help with this project's translations.
|
||||
</p>
|
||||
<p>
|
||||
Please join us on our server to talk about how we can expand our reach.
|
||||
</p>
|
||||
</div>
|
||||
<div class="col-12 col-md-5">
|
||||
<h3 class="mt-0 text-center">Help Wanted</h3>
|
||||
<p>
|
||||
<a href="/discord" class="btn btn-primary btn-lg w-100">Veilid Discord</a>
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
71
pages-old/web-text.md
Normal file
71
pages-old/web-text.md
Normal file
@ -0,0 +1,71 @@
|
||||
---
|
||||
title: Web Text
|
||||
description: How to customize your browser text appearance; based on the WAI customize design document.
|
||||
layout: index
|
||||
exclude: true
|
||||
---
|
||||
|
||||
## Change Text Size with Zoom
|
||||
|
||||
<p>Most web browsers let you increase and decrease the size of text, images, and other web page content with "zoom" features. Some browsers let you choose to zoom only the text size.</p>
|
||||
<p>To change the zoom in most browsers, press the following two keys at the same time:</p>
|
||||
<ul>
|
||||
<li>In Windows, Linux, and Chrome OS:
|
||||
<ul>
|
||||
<li>To zoom bigger: "Ctrl" and "+" keys</li>
|
||||
<li>To zoom smaller: "Ctrl" and "-" keys</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>Mac OS:
|
||||
<ul>
|
||||
<li>To zoom bigger: "⌘" and "+" keys</li>
|
||||
<li>To zoom smaller: "⌘" and "-" keys</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
Browsers provide specific guidance on different ways to change the page zoom or text-only zoom:
|
||||
|
||||
* [Google Chrome - Change text, image, and video sizes (zoom)](https://support.google.com/chrome/answer/96810)
|
||||
* [Apple Safari - Zoom in on webpages](https://support.apple.com/guide/safari/zoom-in-on-webpages-ibrw1068/mac)
|
||||
* [Mozilla Firefox - Font size and zoom](https://support.mozilla.org/en-US/kb/font-size-and-zoom-increase-size-of-web-pages)
|
||||
* [Opera - Zoom](https://help.opera.com/en/latest/browser-window/#zoom)
|
||||
* [Internet Explorer - Ease of access options](https://support.microsoft.com/en-us/help/17456/windows-internet-explorer-ease-of-access-options)
|
||||
* [Microsoft Edge - Ease of Access in Microsoft Edge](https://support.microsoft.com/en-gb/help/4000734/windows-10-microsoft-edge-ease-of-access)
|
||||
* [Vivaldi - Zooming options in Vivaldi](https://help.vivaldi.com/article/zooming-options-in-vivaldi/)
|
||||
|
||||
## Other Text and Color Changes
|
||||
|
||||
Some browsers provide functionality to set different aspects of font and color in the default view.
|
||||
|
||||
* [Mozilla Firefox - Change the fonts and colors websites use](https://support.mozilla.org/en-US/kb/change-fonts-and-colors-websites-use)
|
||||
* [Opera - Look and feel > Fonts](https://help.opera.com/en/presto/look-and-feel/#fonts)
|
||||
* [Microsoft Internet Explorer - Ease of Access Options](https://support.microsoft.com/en-us/help/17456/windows-internet-explorer-ease-of-access-options)
|
||||
|
||||
Other text and color settings are available in Reader View.
|
||||
|
||||
## Reader View
|
||||
|
||||
Most browsers offer a "Reader View" or "Reading View" that shows just the main content; it gets rid of navigation, ads, etc. Some browsers let you set the text font, text size, text color, background color, and line spacing in Reader View.
|
||||
|
||||
* [Apple Safari - Hide ads when reading articles](https://support.apple.com/en-ca/guide/safari/hide-ads-when-reading-articles-sfri32632/mac)
|
||||
* [Mozilla Firefox - Reader View for clutter-free web pages](https://support.mozilla.org/en-US/kb/firefox-reader-view-clutter-free-web-pages)
|
||||
* [Microsoft Edge - Change font style and size for Reading view in Microsoft Edge](https://support.microsoft.com/en-us/help/4028023/microsoft-edge-change-font-style-and-size-for-reading-view)
|
||||
* [Vivaldi - Reader View](https://help.vivaldi.com/article/reader-view/)
|
||||
|
||||
## Advanced Options
|
||||
|
||||
There are many browser extensions and add-ons that provide additional control over how the browser displays text and other content.
|
||||
|
||||
While most browsers no long support user style sheets, extensions provide similar advanced user control. For example, the Stylus extension is available for several major browsers.
|
||||
|
||||
### Note: No Endorsement
|
||||
|
||||
We do not endorse specific web browsers or extensions and does not recommend one over another.
|
||||
While some common browsers are included in this page, mention of a specific browser does not imply
|
||||
endorsement or recommendation.
|
||||
|
||||
|
||||
### About This Page
|
||||
|
||||
This page is based off the [WAI customize design document](https://github.com/w3c/wai-customize-design/blob/master/index.md).
|
||||
@ -18,11 +18,18 @@ layout: subpage
|
||||
</li>
|
||||
<li>
|
||||
<h3>Can I install Veilid?</h3>
|
||||
You can help the main Veilid network by, <a href="https://gitlab.com/veilid/veilid/-/blob/main/INSTALL.md">running a node</a>.
|
||||
<ul>
|
||||
<li>
|
||||
You can help the main Veilid network by, learn how to <a href="/contribute/getting-started">getting started</a>.
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<h3>What about VeilidChat?</h3>
|
||||
VeilidChat is under <a href="https://gitlab.com/veilid/veilidchat/-/commits/main">active development</a>. As soon as we have a public test version available, we'll let you know.
|
||||
<li>
|
||||
<h3>Is Veilid looking for funding?</h3>
|
||||
<p>Veilid is not seeking venture capital or investment. We are accepting tax-deductible donations to our non-profit foundation, Veilid Foundation Inc.</p>
|
||||
<p>
|
||||
<a href="/give" class="btn btn-success">Donate to Veilid</a>
|
||||
</p>
|
||||
</li>
|
||||
<li>
|
||||
<h3>If you're so concerned with privacy, why coordinate on Discord?</h3>
|
||||
@ -32,10 +39,6 @@ layout: subpage
|
||||
<h3>So is all your documentation on Discord?</h3>
|
||||
No, official documentation is available in the <a href="https://gitlab.com/veilid">repositories</a>. We also have people working on a <a href="https://veilid.gitlab.io/developer-book/">developer book</a>, a work in progress.
|
||||
</li>
|
||||
<li>
|
||||
<h3>Is Veilid looking for funding?</h3>
|
||||
<p>Veilid is not seeking venture capital or investment. We are accepting tax-deductible donations to our non-profit foundation, Veilid Foundation Inc.</p>
|
||||
</li>
|
||||
<li>
|
||||
<h3>Does Veilid have a cryptocurrency?</h3>
|
||||
Heck no. Veilid does not have a cryptocurrency.
|
||||
|
||||
73
pages/about-veilid/accessibility.md
Normal file
73
pages/about-veilid/accessibility.md
Normal file
@ -0,0 +1,73 @@
|
||||
---
|
||||
title: Accessibility
|
||||
description: An introduction to accessibility concepts and resources
|
||||
weight: 30
|
||||
layout: subpage
|
||||
---
|
||||
|
||||
[toc]
|
||||
|
||||
### General Accessibility Concepts
|
||||
|
||||
For the scope of this document, we are referring to the accessibility of websites, documents, and applications.
|
||||
|
||||
### Types of Accessibility Challenges
|
||||
|
||||
Here is a partial list of capabilities to keep in mind when designing:
|
||||
|
||||
**Fine Motor Control** – The dexterity of one's eyes, hands, and fingers for the ability to examine and manipulate objects. In practical terms, is it easy for someone using a touch screen to easily click interactive elements and can folks with fine motor control issues manage to interact with those elements was well.
|
||||
|
||||
**Sightedness** – Levels of blindness, near sightedness, and far sightedness. Low-vision users tend to need high color contrast and larger sized text and elements.
|
||||
|
||||
**Color Vision** – Color blindness changes how people perceive colors which can reduce color contrast and make differentiating color coded items difficult.
|
||||
|
||||
**Cognitive Capabilities** – Memory, train of thought, following instructions, and judgment are cognitive capabilities that most folks take for granted. Various disabilities can affect these as well as situational conditions such as being tired from working late.
|
||||
|
||||
**Hearing** – Hearing difficulties can make audio cues or videos less effective.
|
||||
|
||||
### Accessibility Guidelines
|
||||
|
||||
Here is a partial list of general accessibility goals you should strive for:
|
||||
|
||||
#### Structure
|
||||
|
||||
- Headers are denoted as headers in the mark-up or code
|
||||
- Sections of a page or screen are visually distinct and easy to identify
|
||||
|
||||
#### Navigation
|
||||
|
||||
- Easy to figure out current location
|
||||
- Easy to figure out where you can go
|
||||
- Consistent navigation structures and styling
|
||||
|
||||
#### Interactions
|
||||
|
||||
- Clickable items are styled consistently as clickable
|
||||
- Clickable items have a generous hit-box size
|
||||
- UI elements can be easily manipulated with assistive technology
|
||||
|
||||
#### Typography
|
||||
|
||||
- Adjustable text size
|
||||
- Adjusting the text size does not breaking the layout or usability
|
||||
- Text customization options such as changing fonts
|
||||
|
||||
#### Colors
|
||||
|
||||
- Good color contrast for text to be readable
|
||||
- Use a secondary indicator (shape, size, pattern, etc) rather than color alone
|
||||
|
||||
#### Video
|
||||
|
||||
- For the audio in videos, provide subtitles of the dialog and sounds
|
||||
- A transcript of all the content conveyed in the video helps a wide audiences
|
||||
|
||||
### Additional Reading
|
||||
|
||||
- [Mozilla's Accessibility Reference Pages](https://developer.mozilla.org/en-US/docs/Web/Accessibility)
|
||||
- [Cognitive Accessibility at W3C ](https://www.w3.org/WAI/cognitive/)
|
||||
|
||||
### Usability Tools
|
||||
|
||||
- [Color Contrast Grid](https://contrastgrid.com/)
|
||||
- [WebAIM WAVE](https://wave.webaim.org/)
|
||||
167
pages/about-veilid/cryptography.md
Normal file
167
pages/about-veilid/cryptography.md
Normal file
@ -0,0 +1,167 @@
|
||||
---
|
||||
title: Cryptography
|
||||
description: An overview of the cryptography used in Veilid
|
||||
weight: 23
|
||||
layout: subpage
|
||||
---
|
||||
|
||||
|
||||
Strong, appropriate, cryptography choices are essential to the functioning of Veilid.
|
||||
|
||||
Veilid provides applications guarantees about how data is handled on the wire and at rest.
|
||||
|
||||
Cryptosystems were chosen that work well together and provide a balance of speed and cryptographic hardness.
|
||||
|
||||
### Current Cryptography Systems
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<h4>Authentication is Ed25519</h4>
|
||||
Elliptic curve25519 was chosen to provide public/private key authentication and signing capabilities
|
||||
</li>
|
||||
<li>
|
||||
<h4>Key Exchange is x25519</h4>
|
||||
Curve25519 has a DH function that allows nodes to generate a symmetric key to communicate privately.
|
||||
</li>
|
||||
<li>
|
||||
<h4>Encryption is XChaCha20-Poly1305</h4>
|
||||
ChaCha20 with a 192-bit extended nonce is a fast authenticated stream cipher with associated data (AEAD).
|
||||
</li>
|
||||
<li>
|
||||
<h4>Message Digest is BLAKE3</h4>
|
||||
BLAKE3 is a extremely fast cryptographic hash that is highly parallelizable and as strong as SHA3-256 and over 17 times faster.
|
||||
</li>
|
||||
<li>
|
||||
<h4>Key Derivation is Argon2</h4>
|
||||
Password hash generation should be slow and resistant to GPU attacks Argon2 was the winner of the 2015 Password Hashing Competition.
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
### Upgrading Cryptography Systems
|
||||
|
||||
Nothing lasts forever and cryptography is no exception. As computing power improves and cryptographic attacks evolve, weaknesses in cryptosystems are inevitable.
|
||||
|
||||
Veilid has ensured that upgrading to newer cryptosystems is streamlined and minimally invasive to app developers, and handled transparently at the node level.
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<h4>Multiple Routing Tables</h4>
|
||||
Because changing cryptosystems changes node ids, there will be different distance measurements between nodes, necessitating a separate routing table per cryptosystem. We support this today.
|
||||
</li>
|
||||
<li>
|
||||
<h4>Typed Keys</h4>
|
||||
Cryptographic keys, signatures, and hashes are all tagged with their cryptosystem to ensure that we know exactly how they were generated and how they should be used and persisted.
|
||||
</li>
|
||||
<li>
|
||||
<h4>Migration Support</h4>
|
||||
Reading persisted data will automatically use the correct cryptosystem and will default to always writing it back using the newest/best cryptosystem. This allows for data to be easily migrated just by reading it and writing it back to storage.
|
||||
</li>
|
||||
<li>
|
||||
<h4>Simultaneous Cryptosystems</h4>
|
||||
While transitioning cryptosystems, nodes can respond to other nodes using either the old system or the new one, or both.
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
### Secure Storage
|
||||
|
||||
|
||||
|
||||
- Device-level secret storage APIs are available for all platforms
|
||||
- Encrypted table store APIs are exposed to applications to make safe data storage easy
|
||||
- Device data keys can also be password protected
|
||||
- Apps never need to write anything to disk unencrypted
|
||||
|
||||
<div class="row g-3 mx-2 card-set">
|
||||
<div class="col-12 col-md-6">
|
||||
<div class="card">
|
||||
<div class="card-header text-bg-light">
|
||||
<h4>ProtectedStore</h4>
|
||||
</div>
|
||||
<div class="card-body">
|
||||
<p>Device-level Secret Storage</p>
|
||||
<ul>
|
||||
<li>MacOS / iOS Keychain</li>
|
||||
<li>Android Keystore</li>
|
||||
<li>Windows Protected Storage</li>
|
||||
<li>Linux Secret Service</li>
|
||||
</ul>
|
||||
Veilid Maintained Rust Crate: <code>keyring-manager</code>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="col-12 col-md-6">
|
||||
<div class="card">
|
||||
<div class="card-header text-bg-light">
|
||||
<h4>TableStore</h4>
|
||||
</div>
|
||||
<div class="card-body">
|
||||
<p>Encrypted Key-Value Database</p>
|
||||
<ul>
|
||||
<li>SQLITE on Native</li>
|
||||
<li>IndexedDB in Browser</li>
|
||||
<li>Device Key can be protected from backup dumping attacks</li>
|
||||
</ul>
|
||||
Veilid Maintained Rust Crate: <code>keyvaluedb</code>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="col-12 col-md-6">
|
||||
<div class="card">
|
||||
<div class="card-header text-bg-light">
|
||||
<h4>RecordStore</h4>
|
||||
</div>
|
||||
<div class="card-body">
|
||||
<p>Distributed Hash Table Storage</p>
|
||||
<ul>
|
||||
<li>Encrypted + Authenticated</li>
|
||||
<li>Subkey support</li>
|
||||
<li>LRU distributed cache</li>
|
||||
<li>Per-key multi-writer schemas</li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="col-12 col-md-6">
|
||||
<div class="card">
|
||||
<div class="card-header text-bg-light">
|
||||
<h4>BlockStore</h4>
|
||||
</div>
|
||||
<div class="card-body">
|
||||
<p>Content-addressable Data Distribution
|
||||
<ul>
|
||||
<li>Take What You Give model</li>
|
||||
<li>Connect and share cloud storage</li>
|
||||
<li>Bittorrent-like sharding</li>
|
||||
</ul>
|
||||
This feature is "coming soon."
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
### On The Wire
|
||||
|
||||
<div class="focus-text">
|
||||
<p>Everything is end-to-end encrypted</p>
|
||||
<p>Data is encrypted at rest and on the wire</p>
|
||||
<p>Your data is protected even if you lose your device</p>
|
||||
</div>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<h4>All Protocols Same Encryption</h4>
|
||||
Each low-level protocol uses the same message and receipt encapsulation. No protocol is special and all protocols offer the same safety guarantees.
|
||||
</li>
|
||||
<li>
|
||||
<h4>Encrypted And Signed</h4>
|
||||
Messages between nodes are signed by the sender and encrypted for only the receiver. Messages can be relayed without decryption and authentication covers the entire contents including headers.
|
||||
</li>
|
||||
<li>
|
||||
<h4>Everything Is Timestamped</h4>
|
||||
Envelopes include timestamps and unique nonces and reject old or replayed messages.
|
||||
</li>
|
||||
<li>
|
||||
<h4>Node Information Is Signed</h4>
|
||||
When a node publishes routing table entries they are signed. No node can lie about another node's dial info, capabilities, availability, or replay old node info when newer info is available.
|
||||
</li>
|
||||
</ul>
|
||||
40
pages/about-veilid/index.md
Normal file
40
pages/about-veilid/index.md
Normal file
@ -0,0 +1,40 @@
|
||||
---
|
||||
title: About Veilid
|
||||
description: Veilid is an open-source, distributed application framework.
|
||||
layout: subpage
|
||||
menu:
|
||||
main:
|
||||
weight: 3
|
||||
---
|
||||
|
||||
<p>Veilid (pronounced Vay-Lid, from 'Valid and Veiled Identification')</p>
|
||||
<p>
|
||||
Veilid allows developers to build a distributed, private app. Veilid gives users the privacy to opt out of
|
||||
data collection and online tracking. Veilid is being built with user experience, privacy, and safety as our top priorities.
|
||||
It is open source and available to everyone to use and build upon.
|
||||
</p>
|
||||
<p>
|
||||
Veilid goes above and beyond existing privacy technologies and has the potential to completely change the way
|
||||
people use the Internet. Veilid has no profit motive, which puts us in a unique position to promote ideals
|
||||
without the compromise of capitalism.
|
||||
</p>
|
||||
<p class="focus-text">
|
||||
We built Veilid because when the Internet was young and new, we viewed it as an endless and open realm of possibility.
|
||||
</p>
|
||||
<p>
|
||||
Instead, the Internet we know now has been heavily commercialized, with users and their data being the most
|
||||
sought-after commodity. The only ways to opt-out of becoming the product for billionaires to exploit are either
|
||||
too technical for the average user, or to simply not go online.
|
||||
</p>
|
||||
<p>
|
||||
We don't believe that is fair; we still haven't given up our dream for the entire Internet to be free
|
||||
and accessible without trading privacy to use it.
|
||||
</p>
|
||||
<p class="focus-text">
|
||||
We believe that everyone should be able to forge relationships, learn, create, and build online — without being monetized.
|
||||
</p>
|
||||
<p>
|
||||
With Veilid, the user is in control, in a way that is approachable and friendly, regardless of technical
|
||||
ability. We want to give the world the Internet we should have had all along.
|
||||
</p>
|
||||
|
||||
63
pages/about-veilid/networking.md
Normal file
63
pages/about-veilid/networking.md
Normal file
@ -0,0 +1,63 @@
|
||||
---
|
||||
title: Networking
|
||||
description: An overview of the networking used in Veilid
|
||||
weight: 22
|
||||
layout: subpage
|
||||
---
|
||||
|
||||
<div class="focus-text">
|
||||
<p>All devices are welcome and treated equally</p>
|
||||
<p>You can use the public Veilid Network or build your own</p>
|
||||
<p>Nodes help each other like mutual aid for connectivity</p>
|
||||
</div>
|
||||
|
||||
All Veilid applications running `veilid-core` are 'nodes', and they are all equal in the eyes of the network. No nodes are 'special'.
|
||||
|
||||
Nodes are only limited by the resources they bring and the configuration of the network they are on.
|
||||
|
||||
DNS is only used one time during ‘bootstrap'; it is not required though.
|
||||
|
||||
SSL is optional and only for HTTPS Websockets for Veilid Webapps.
|
||||
|
||||
### Protocols
|
||||
|
||||
Veilid uses UDP, TCP, and Websockets.
|
||||
|
||||
Low level protocols supported by Veilid are kept simple, to minimize complications. Everything uses framed RPC operations up
|
||||
to 64KB in size. Protocol support is extensible and may add WebRTC and other specialized protocols in the future.
|
||||
|
||||
### Network Topology
|
||||
|
||||
<p><img src="/img/Network-Thumbnail.png" alt="A topology graph for Veilid networks" class="img-fluid"></p>
|
||||
<p>To zoom in on the details, <a href="/img/Network.png">view the full size image directly</a>.</p>
|
||||
|
||||
### Bootstrapping
|
||||
|
||||
Bootstrap nodes not 'special' nodes. Any node can bootstrap a Veilid network. Networks can be 'keyed' to keep nodes off that don't have the key. You can join the ‘big Veilid network' or make your own isolated network.
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<h4>Ask Bootstraps To ‘Find Self'</h4>
|
||||
A single initial DNS TXT record request returns some bootstrap nodes that are known to exist. Those are asked to return nodes that are ‘close' to your own node.
|
||||
</li>
|
||||
<li>
|
||||
<h4>Public Address Detection</h4>
|
||||
Nodes are often behind various forms of NAT. Validating one's own public ‘Dial Info' is essential for publishing one's Node Info and answering Find Node requests.
|
||||
</li>
|
||||
<li>
|
||||
<h4>Relay Configuration</h4>
|
||||
Low-capability network classes may require the use of Inbound or Outbound relays in order to achieve reachability Nodes help each other out to the best of their ability and incur no penalty for not being able to assist other nodes.
|
||||
</li>
|
||||
<li>
|
||||
<h4>Peer Minimum Refresh </h4>
|
||||
Nodes in your routing table are asked to return nodes that are near you as well. Finding nodes close to your own is always harder than finding nodes far away, so we focus on that with our requests.
|
||||
</li>
|
||||
<li>
|
||||
<h4>Network Class Detection</h4>
|
||||
Determining NAT type and what mechanisms can be used to achieve connectivity. Direct connection techniques like reverse connections and UDP hole punching may be inappropriate for some network classes.
|
||||
</li>
|
||||
<li>
|
||||
<h4>Ping Validation</h4>
|
||||
Nodes come and go, change address, and are unreliable. Checking routing table nodes for proof-of-life is done with exponential backoff. Nodes are removed from the routing table on a LIFO basis.
|
||||
</li>
|
||||
</ul>
|
||||
23
pages/about-veilid/overview.md
Normal file
23
pages/about-veilid/overview.md
Normal file
@ -0,0 +1,23 @@
|
||||
---
|
||||
title: Framework Overview
|
||||
description: An overview of the Veilid Framework
|
||||
weight: 20
|
||||
layout: subpage
|
||||
sortby: weight
|
||||
---
|
||||
|
||||
<div class="focus-text">
|
||||
Veilid is an open-source, peer-to-peer, mobile-first, networked application framework.
|
||||
</div>
|
||||
|
||||
The framework is conceptually similar to <a href="https://ipfs.tech/">IPFS</a> and <a href="https://www.torproject.org/">Tor</a>, but faster and designed from the ground-up to provide all
|
||||
services over a privately routed network.
|
||||
|
||||
The framework enables development of fully-distributed applications without a 'blockchain' or
|
||||
a 'transactional layer' at their base.
|
||||
|
||||
The framework can be included as part of user-facing applications or run as a 'headless node'
|
||||
for power users who wish to help build the network.
|
||||
|
||||
Download the PDF [Slides from Defcon 31](/Launch-Slides-Veilid.pdf)
|
||||
|
||||
84
pages/about-veilid/private-routing.md
Normal file
84
pages/about-veilid/private-routing.md
Normal file
@ -0,0 +1,84 @@
|
||||
---
|
||||
title: Private Routing
|
||||
description: An overview of how private routing works in Veilid
|
||||
weight: 25
|
||||
layout: subpage
|
||||
---
|
||||
|
||||
### Private and Safety Routes
|
||||
|
||||
<figure>
|
||||
<img src="/img/private-and-safety-routes.png" alt="a diagram of routes between points a and b" class="img-fluid">
|
||||
<figcaption>
|
||||
Veilid Routes are a combination of source and destination private routing.
|
||||
Because no node can trust any other node to pick the whole route, both source and destination must participate.
|
||||
</figcaption>
|
||||
</figure>
|
||||
|
||||
### Compiled Routes
|
||||
|
||||
<figure>
|
||||
<img src="/img/compiled-routes.png" alt="a diagram of routes between points a and b, shown with components" class="img-fluid">
|
||||
<figcaption>
|
||||
Private Routes are published as a ‘private destination’ and Safety Routes are allocated locally and combined
|
||||
together with a Private Route to form a Compiled Route.
|
||||
</figcaption>
|
||||
</figure>
|
||||
|
||||
### Secure Envelopes
|
||||
|
||||
<figure>
|
||||
<img src="/img/secure-envelopes.png" alt="a diagram how a message is passed from B to A" class="img-fluid">
|
||||
<figcaption>
|
||||
<p>
|
||||
Each node hop only knows about the next one This is similar to onion routing, but assumes that
|
||||
the source is fully in control of the Safety Route and the destination is fully in control of
|
||||
the Private Route.
|
||||
</p>
|
||||
<p>To zoom in on the details, <a href="/img/secure-envelopes.png">view the image directly</a>.</p>
|
||||
</figcaption>
|
||||
</figure>
|
||||
|
||||
|
||||
### Toward The Future
|
||||
|
||||
<div class="focus-text">
|
||||
<p>Private routing is a balance of performance and security</p>
|
||||
<p>Applications can make use of higher node hop counts if they desire</p>
|
||||
<p>Future private routing advancements will be transparent to users</p>
|
||||
</div>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<h4>Per-Hop Payload Keying</h4>
|
||||
Ensuring that there is nothing common between packets at each hop will reduce the risk of mass data collection
|
||||
being able to deanonymize routes.
|
||||
</li>
|
||||
<li>
|
||||
<h4>Simplify Directionality</h4>
|
||||
Routes are currently bidirectional, but are allocated directionally.
|
||||
We may be able to simplify our allocation mechanism by enforcing bidirectionality.
|
||||
Bidirectional routes are faster, but directional routes could provide more anonymity.
|
||||
</li>
|
||||
<li>
|
||||
<h4>Elimination of Hop Counting</h4>
|
||||
Currently the protocol keeps an internal hop count that is not necessary.
|
||||
Efforts should be made to ensure that individual nodes don’t know how far along in a route they are.
|
||||
</li>
|
||||
<li>
|
||||
<h4>Hop Caching</h4>
|
||||
Route hop NodeInfo could be cached to save on-the-wire size as well as speed things up.
|
||||
</li>
|
||||
<li>
|
||||
<h4>Increasing Hop Count</h4>
|
||||
<p>Currently the default is one hop chosen by the Safety Route, and one hop chosen by the Private Route, which leads to three hops total once compiled.</p>
|
||||
<p>It may be important to increase hop count to 2 for users with critical safety needs and to protect from nation-state-level deanonymization where appropriate.</p>
|
||||
<p>Existing research (on Tor) suggests that our existing hop count should be sufficient and provide comparable anonymity, but this should be revisited.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="focus-text">
|
||||
<p>IP Privacy means your location is safe too</p>
|
||||
<p>Users don’t have to do anything to use it</p>
|
||||
<p>No IP address means no tracking, collection, or correlation</p>
|
||||
</div>
|
||||
85
pages/about-veilid/rpc.md
Normal file
85
pages/about-veilid/rpc.md
Normal file
@ -0,0 +1,85 @@
|
||||
---
|
||||
title: RPC Protocol
|
||||
description: An overview of the RPC protocol used in Veilid
|
||||
weight: 24
|
||||
layout: subpage
|
||||
---
|
||||
|
||||
### RPC Summary
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<h4>Schema Language is Cap'n Proto</h4>
|
||||
<a href="https://capnproto.org/">Cap’n Proto</a> is designed for deserialization speed and schema evolution. Flexible and well supported in Rust.
|
||||
</li>
|
||||
<li>
|
||||
<h4>RPC is fully in-schema and documented</h4>
|
||||
Both ‘Question/Answer’ and ‘Statement’ RPC modes are supported. All schema fields are documented.
|
||||
</li>
|
||||
<li>
|
||||
<h4>RPC fully supports Private Routing</h4>
|
||||
All private routing structures are expressed in the RPC schema itself, no magic encrypted blobs.
|
||||
</li>
|
||||
<li>
|
||||
<h4>Schema Evolution is built-in</h4>
|
||||
Fields can be added and removed with full backward and forward compatibility. New features won’t break older Veilid nodes.
|
||||
</li>
|
||||
<li>
|
||||
<h4>RPC Schema is cryptography-independent</h4>
|
||||
As cryptosystems change, the language spoken by Veilid nodes remains the same.
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
### Distributed Hash Table
|
||||
|
||||
Distributed Hash Tables are a way of storing data in records that have keys that are close to nodes in the network.
|
||||
|
||||
#### DHT Is Just ‘Search’
|
||||
It may look complicated, but all the DHT algorithms out there are just ‘search’ algorithms. Finding data that is stored on some node somewhere out there.
|
||||
|
||||
#### Improving Search
|
||||
We built a better DHT by making both search and data locality more relevant. Veilid synchronizes popular data when nodes come and go from the network.
|
||||
|
||||
<img src="/img/dht-diagram.png" alt="a tree diagram for the search ability" class="img-fluid lightbox">
|
||||
|
||||
Locating a node by its ID. Here the node with the prefix 0011 finds the node with the prefix 1110 by
|
||||
successively learning of and querying closer and closer nodes. The line segment on top represents the
|
||||
space of 160-bit IDs, and shows how the lookups coverge to the target node. Below we illustrate RPC messages
|
||||
made by 1110. The first RPC is to node 101, already known to 1110. Subsequent RPCs are to nodes returned by the
|
||||
previous RPC.
|
||||
|
||||
#### DHT Schema
|
||||
Veilid DHT is built using GetValue and SetValue RPC operations. Nodes can opt out of DHT storage if they do not want to participate.
|
||||
|
||||
Veilid DHT records have schemas that define subkeys that are individually addressable and can have multiple writers.
|
||||
|
||||
DHT record subkeys have sequence numbers and are eventually consistent across multiple writes and background synchronizations.
|
||||
|
||||
<div class="row gx-5 gy-3 mb-3">
|
||||
<div class="col-12 col-lg-6">
|
||||
<figure class="h-100">
|
||||
<img src="/img/dht-dflt-framed.png" alt="a diagram showing key-value pairs" class="img-fluid lightbox">
|
||||
<figcaption>
|
||||
<p>Veilid Default DHT Schema - DFLT</p>
|
||||
<p>To zoom in on the details, <a href="/img/dht-dflt-framed.png">view the image directly</a>.</p>
|
||||
</figcaption>
|
||||
</figure>
|
||||
</div>
|
||||
<div class="col-12 col-lg-6">
|
||||
<figure class="h-100">
|
||||
<img src="/img/dht-smpl.png" alt="a diagram showing key-value pairs, but with more fields" class="img-fluid lightbox">
|
||||
<figcaption>
|
||||
<p>Veild Simple DHT Schema - SMPL</p>
|
||||
<p>To zoom in on the details, <a href="/img/dht-smpl.png">view the image directly</a>.</p>
|
||||
</figcaption>
|
||||
</figure>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<div class="focus-text">
|
||||
<p>The DHT gives you full control over your data</p>
|
||||
<p>Our DHT is not based on a blockchain or a coin </p>
|
||||
<p>Popular data becomes more available automatically </p>
|
||||
</div>
|
||||
11
pages/chat/beta.md
Normal file
11
pages/chat/beta.md
Normal file
@ -0,0 +1,11 @@
|
||||
---
|
||||
title: Beta Testing
|
||||
description: Help us beta test VeilidChat
|
||||
weight: 2
|
||||
layout: subpage
|
||||
---
|
||||
|
||||
|
||||
<p>
|
||||
<img src="/img/noun-construction-6606547.png" alt="a construction barrier">
|
||||
<p>
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Code of Conduct
|
||||
description: Veilid community and developer code of conduct
|
||||
weight: 2
|
||||
weight: 3
|
||||
layout: subpage
|
||||
---
|
||||
|
||||
|
||||
29
pages/contribute/getting-started.md
Normal file
29
pages/contribute/getting-started.md
Normal file
@ -0,0 +1,29 @@
|
||||
---
|
||||
title: Getting Started
|
||||
description: The code base for the different parts and tools of Veilid
|
||||
layout: subpage
|
||||
weight: 2
|
||||
---
|
||||
|
||||
### Running a Node
|
||||
|
||||
To install the Veilid node software, please follow the instructions available in the [repository](https://gitlab.com/veilid/veilid/-/blob/main/INSTALL.md).
|
||||
|
||||
### Starting Development
|
||||
|
||||
Please recursively check out the project using this command
|
||||
|
||||
`git clone git@gitlab.com:veilid/veilid.git`
|
||||
|
||||
Then read the [development](https://gitlab.com/veilid/veilid/-/blob/main/DEVELOPMENT.md) guide to get started.
|
||||
|
||||
There is also a [Veilid Book](https://veilid.gitlab.io/developer-book/).
|
||||
|
||||
### About the Code Repo
|
||||
|
||||
The main repository is located at https://gitlab.com/veilid/veilid and includes several components
|
||||
- `veilid-core` - the main Veilid crate: https://crates.io/crates/veilid-core
|
||||
- `veilid-tools` - misc functions for veilid and friends: https://crates.io/crates/veilid-tools
|
||||
- `veilid-wasm` - Veilid bindings for webassembly: https://crates.io/crates/veilid-wasm
|
||||
- `veilid-flutter` - Veilid bindings for Flutter/Dart. Comes with an example program: https://crates.io/crates/veilid-flutter
|
||||
- Also `veilid-server` and `veilid-cli` source are also in this repo for building headless nodes
|
||||
41
pages/events/index.md
Normal file
41
pages/events/index.md
Normal file
@ -0,0 +1,41 @@
|
||||
---
|
||||
title: Events
|
||||
description: Come meet Team Veilid!
|
||||
layout: index
|
||||
menu:
|
||||
main:
|
||||
weight: 2
|
||||
---
|
||||
|
||||
|
||||
|
||||
We'll be at B-Sides Las Vegas and Def Con 32 for Hacker Summer Camp 2024!
|
||||
|
||||
|
||||
|
||||
<div class="row my-5">
|
||||
<div class="col-12 col-md-4">
|
||||
<img src="/img/veilid-bsides-2024.png" class="w-100 d-block" alt="a map of the conference with the Veilid booth circled">
|
||||
</div>
|
||||
<div class="col-12 col-md-8">
|
||||
<h3 class="mt-3">B-Sides Las Vegas 2024</h3>
|
||||
<p>If you're at B-Sides Las Vegas this year, please come visit us.<p>
|
||||
<p>Veilid is a charity partner for <a href="https://bsideslv.org/raffle">B-Sides Las Vegas 2024</a>.</p>
|
||||
<p>You can find us front and center in the Middle Ground.</p>
|
||||
</div>
|
||||
|
||||
<div class="row my-5">
|
||||
<div class="col-12 col-md-4">
|
||||
<img src="/img/def-con-32-theme.png" alt="def con 32 theme logo. the theme is 'engage'. a large robot gently holds a femme figure as if to speak to her." class="d-block w-100">
|
||||
</div>
|
||||
<div class="col-12 col-md-8">
|
||||
<h3 class="mt-3">DefCon 32: Veilid Dev and Community Meetup</h3>
|
||||
<p>Friday: 12:00 - 13:30 in the Warstories Track</p>
|
||||
<p>Cult of the Dead Cow and Hackers.Town are bringing you a meet and greet and chat session about Veilid Framework. Come by, say hi, talk shop, let’s see each other in person and have a little fun! Veilid Foundation directors and many of the primary contributors will be there to share progress over the last year. Come by and help us to restore the future and ensure the privacy of the internet for generations to come!</p>
|
||||
<h4>Links</h4>
|
||||
<ul>
|
||||
<li><a href="https://forum.defcon.org/node/249522">Official Forum Post</a></li>
|
||||
<li><a href="https://defcon.org/html/defcon-32/dc-32-index.html">Official DefCon 32 Website</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
@ -15,57 +15,19 @@ layout: index
|
||||
application framework.
|
||||
</p>
|
||||
|
||||
<p>Veilid (pronounced Vay-Lid, from 'Valid and Veiled Identification')</p>
|
||||
<p>
|
||||
Veilid allows anyone to build a distributed, private app. Veilid gives users the privacy to opt out of
|
||||
data collection and online tracking. Veilid is being built with user experience, privacy, and safety as our top priorities.
|
||||
It is open source and available to everyone to use and build upon.
|
||||
</p>
|
||||
<p>
|
||||
Veilid goes above and beyond existing privacy technologies and has the potential to completely change the way
|
||||
people use the Internet. Veilid has no profit motive, which puts us in a unique position to promote ideals
|
||||
without the compromise of capitalism.
|
||||
</p>
|
||||
<p class="focus-text">
|
||||
We built Veilid because when the Internet was young and new, we viewed it as an endless and open realm of possibility.
|
||||
</p>
|
||||
<p>
|
||||
Instead, the Internet we know now has been heavily commercialized, with users and their data being the most
|
||||
sought-after commodity. The only ways to opt-out of becoming the product for billionaires to exploit are either
|
||||
too technical for the average user, or to simply not go online.
|
||||
</p>
|
||||
<p>
|
||||
We don't believe that is fair; we still haven't given up our dream for the entire Internet to be free
|
||||
and accessible without trading privacy to use it.
|
||||
</p>
|
||||
<p class="focus-text">
|
||||
We believe that everyone should be able to forge relationships, learn, create, and build online — without being monetized.
|
||||
</p>
|
||||
<p>
|
||||
With Veilid, the user is in control, in a way that is approachable and friendly, regardless of technical
|
||||
ability. We want to give the world the Internet we should have had all along.
|
||||
</p>
|
||||
|
||||
|
||||
|
||||
<div class="row gx-5 gy-3 mt-5">
|
||||
<div class="col-12 col-md-6 col-lg-3">
|
||||
<a class="btn btn-info btn-lg w-100" href="/docs/overview/">Technical Details</a>
|
||||
</div>
|
||||
<div class="col-12 col-md-6 col-lg-3">
|
||||
<a class="btn bgv-fuschia btn-lg w-100" href="/chat">VeilidChat</a>
|
||||
</div>
|
||||
<div class="col-12 col-md-6 col-lg-3">
|
||||
<a class="btn btn-dark btn-lg w-100" href="/code">Code</a>
|
||||
</div>
|
||||
<div class="col-12 col-md-6 col-lg-3">
|
||||
<a class="btn btn-primary btn-lg w-100" href="/discord">Discord</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="row gx-5 gy-3 mt-3 justify-content-center">
|
||||
<div class="row">
|
||||
<div class="col-12 col-md-6">
|
||||
<a class="btn btn-success btn-lg w-100 text-white" href="/donate">Donate</a>
|
||||
<a href="/events"><img class="d-block" style="max-height: 350px; margin: auto;" src="/img/veilid-events-vegas.svg" alt="an simple line icon version of the famous Las Vegas sign"></a>
|
||||
</div>
|
||||
<div class="col-12 col-md-6">
|
||||
<h3>Way to Help</h3>
|
||||
<p>There a so many ways to join the community and help out:</p>
|
||||
<ul class="list-style-none">
|
||||
<li><a class="btn btn-primary btn-lg w-100" href="/discord">Discord</a></li>
|
||||
<li><a class="btn btn-dark btn-lg w-100" href="/contribute">Contribute</a></li>
|
||||
<li><a class="btn btn-secondary btn-lg w-100" href="/contribute/download">Download</a></li>
|
||||
<li><a class="btn btn-success btn-lg w-100 text-white" href="/donate">Donate</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
12
staged.md
Normal file
12
staged.md
Normal file
@ -0,0 +1,12 @@
|
||||
<div class="col-12 col-md-6">
|
||||
<h3>Are there Apps yet?</h3>
|
||||
<p>Help us beta test our proof-of-concept app:</p>
|
||||
<p><a class="btn bgv-fuschia btn-lg w-100" href="/chat/beta">VeilidChat</a></p>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
|
||||
<li>
|
||||
You can help beta test <a href="/chat/beta">VeilidChat</a>.
|
||||
</li>
|
||||
BIN
static/img/def-con-32-theme.png
Normal file
BIN
static/img/def-con-32-theme.png
Normal file
Binary file not shown.
|
After 
(image error) Size: 198 KiB |
BIN
static/img/noun-construction-6606547.png
Normal file
BIN
static/img/noun-construction-6606547.png
Normal file
Binary file not shown.
|
After 
(image error) Size: 5.9 KiB |
BIN
static/img/veilid-bsides-2024.png
Normal file
BIN
static/img/veilid-bsides-2024.png
Normal file
Binary file not shown.
|
After 
(image error) Size: 134 KiB |
26
static/img/veilid-events-vegas.svg
Normal file
26
static/img/veilid-events-vegas.svg
Normal file
@ -0,0 +1,26 @@
|
||||
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
|
||||
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
|
||||
<svg width="100%" height="100%" viewBox="0 0 450 350" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" xmlns:serif="http://www.serif.com/" style="fill-rule:evenodd;clip-rule:evenodd;stroke-linejoin:round;stroke-miterlimit:2;">
|
||||
<g transform="matrix(0.891664,0,0,0.891664,-1.87262,-2.7406)">
|
||||
<g transform="matrix(1,0,0,1,-1.50684,-10.9904)">
|
||||
<path d="M98.98,99.469L157.742,108.481L137.691,135.801C136.339,137.652 138.64,139.949 140.492,138.602L167.812,118.551L176.824,177.313C177.175,179.574 180.433,179.574 180.773,177.313L189.784,118.551L217.104,138.61C218.944,139.961 221.253,137.66 219.905,135.809L199.854,108.489L258.616,99.477C260.878,99.125 260.878,95.868 258.616,95.528L199.854,86.516L219.905,59.196C221.257,57.344 218.956,55.048 217.104,56.395L189.784,76.454L180.773,17.692C180.421,15.431 177.163,15.431 176.824,17.692L167.812,76.454L140.48,56.399C138.64,55.048 136.331,57.349 137.679,59.2L157.73,86.52L98.968,95.532C96.718,95.872 96.718,99.129 98.98,99.469L98.98,99.469Z" style="fill:rgb(142,0,150);fill-rule:nonzero;"/>
|
||||
</g>
|
||||
<g transform="matrix(1,0,0,1,-1.50684,-10.9904)">
|
||||
<path d="M475.97,244.96L429.181,225.769C433.712,220.66 436.47,213.941 436.47,206.589C436.47,190.62 423.482,177.628 407.509,177.628C396.529,177.628 386.958,183.769 382.048,192.8C377.138,183.769 367.568,177.628 356.587,177.628C345.607,177.628 336.036,183.769 331.126,192.8C326.216,183.769 316.646,177.628 305.665,177.628C294.685,177.628 285.114,183.769 280.204,192.8C275.294,183.769 265.724,177.628 254.743,177.628C243.763,177.628 234.192,183.769 229.282,192.8C224.372,183.769 214.802,177.628 203.821,177.628C192.841,177.628 183.27,183.769 178.36,192.8C173.45,183.769 163.88,177.628 152.899,177.628C148.719,177.628 144.739,178.526 141.137,180.128L141.137,152.937C141.137,151.007 139.567,149.437 137.637,149.437C135.707,149.437 134.137,151.007 134.137,152.937L134.137,184.546C131.375,186.898 129.067,189.745 127.348,192.968C125.227,189.23 122.27,186.019 118.719,183.609L118.719,118.717C118.719,116.788 117.149,115.217 115.219,115.217C113.289,115.217 111.719,116.788 111.719,118.717L111.719,180.187C109.039,179.315 106.18,178.847 103.207,178.847C87.918,178.847 75.477,191.288 75.477,206.577C75.477,213.948 78.376,220.647 83.079,225.628L35.97,244.956C21.38,250.936 12.322,264.456 12.322,280.226C12.322,295.996 21.381,309.507 35.97,315.496L111.708,346.566L118.72,349.436L134.142,355.764L141.142,358.624L216.333,389.464L223.329,392.344L238.751,398.672L245.751,401.543L250.872,403.645C252.513,404.316 254.231,404.656 255.95,404.656C257.669,404.656 259.391,404.316 261.028,403.645L475.918,315.496C490.508,309.516 499.566,295.996 499.566,280.227C499.57,264.453 490.558,250.942 475.968,244.954L475.97,244.96ZM407.513,184.64C419.622,184.64 429.474,194.492 429.474,206.601C429.474,218.71 419.622,228.562 407.513,228.562C395.404,228.562 385.552,218.71 385.552,206.601C385.552,194.488 395.411,184.64 407.513,184.64ZM356.603,184.64C363.232,184.64 369.181,187.601 373.212,192.261C371.2,191.749 369.11,191.48 366.943,191.48C352.884,191.48 341.482,202.878 341.482,216.941C341.482,219.101 341.751,221.203 342.263,223.21C337.603,219.179 334.642,213.23 334.642,206.601C334.642,194.488 344.489,184.64 356.603,184.64L356.603,184.64ZM305.693,184.64C317.802,184.64 327.654,194.492 327.654,206.601C327.654,218.71 317.802,228.562 305.693,228.562C293.584,228.562 283.732,218.71 283.732,206.601C283.732,194.488 293.58,184.64 305.693,184.64ZM254.771,184.64C261.4,184.64 267.349,187.601 271.38,192.261C269.368,191.749 267.271,191.48 265.111,191.48C251.052,191.48 239.65,202.878 239.65,216.941C239.65,219.101 239.919,221.203 240.431,223.21C235.771,219.179 232.81,213.23 232.81,206.601C232.81,194.488 242.661,184.64 254.771,184.64L254.771,184.64ZM203.861,184.64C215.97,184.64 225.822,194.492 225.822,206.601C225.822,218.71 215.97,228.562 203.861,228.562C191.752,228.562 181.9,218.71 181.9,206.601C181.9,194.488 191.752,184.64 203.861,184.64ZM152.943,184.64C159.572,184.64 165.521,187.601 169.552,192.261C167.54,191.749 165.443,191.48 163.283,191.48C149.224,191.48 137.822,202.878 137.822,216.941C137.822,219.101 138.091,221.203 138.603,223.21C133.943,219.179 130.982,213.23 130.982,206.601C130.989,194.488 140.841,184.64 152.943,184.64L152.943,184.64ZM82.533,206.589C82.533,195.159 91.834,185.859 103.263,185.859C114.693,185.859 123.993,195.16 123.993,206.589C123.993,218.019 114.692,227.319 103.263,227.319C91.829,227.319 82.533,218.018 82.533,206.589ZM473.323,309.019L258.433,397.167C256.874,397.808 255.144,397.808 253.581,397.167L38.681,309.019C26.771,304.128 19.372,293.097 19.372,280.23C19.372,267.359 26.771,256.332 38.681,251.441L89.443,230.621C93.514,232.973 98.233,234.32 103.263,234.32C113.603,234.32 122.634,228.621 127.404,220.211C132.283,229.332 141.904,235.551 152.955,235.551C163.935,235.551 173.506,229.411 178.416,220.379C183.327,229.41 192.896,235.551 203.877,235.551C214.858,235.551 224.428,229.411 229.338,220.379C234.249,229.41 243.818,235.551 254.799,235.551C265.78,235.551 275.35,229.411 280.26,220.379C285.171,229.41 294.74,235.551 305.721,235.551C316.702,235.551 326.272,229.411 331.182,220.379C336.093,229.41 345.662,235.551 356.643,235.551C367.624,235.551 377.194,229.411 382.104,220.379C387.015,229.41 396.584,235.551 407.565,235.551C413.355,235.551 418.756,233.832 423.284,230.891L473.374,251.442C485.284,256.333 492.683,267.364 492.683,280.231C492.676,293.102 485.234,304.129 473.324,309.02L473.323,309.019Z" style="fill:rgb(142,0,150);fill-rule:nonzero;"/>
|
||||
</g>
|
||||
<g transform="matrix(1,0,0,1,-1.50684,-10.9904)">
|
||||
<path d="M250.92,156.81L245.799,158.912L245.799,118.732C245.799,116.802 244.229,115.232 242.299,115.232C240.369,115.232 238.799,116.802 238.799,118.732L238.799,161.783L223.377,168.111L223.377,152.951C223.377,151.021 221.807,149.451 219.877,149.451C217.947,149.451 216.377,151.021 216.377,152.951L216.377,173.33C216.377,174.502 216.955,175.591 217.928,176.24C218.506,176.631 219.189,176.83 219.877,176.83C220.326,176.83 220.775,176.74 221.205,176.568L253.576,163.287C255.135,162.646 256.865,162.646 258.428,163.287L288.479,175.615C290.268,176.345 292.307,175.494 293.049,173.705C293.779,171.916 292.928,169.877 291.139,169.135L261.088,156.807C257.799,155.463 254.197,155.463 250.92,156.81L250.92,156.81Z" style="fill:rgb(142,0,150);fill-rule:nonzero;"/>
|
||||
</g>
|
||||
<g transform="matrix(1,0,0,1,-1.50684,-10.9904)">
|
||||
<path d="M198.11,36.52L235.301,36.52C237.231,36.52 238.801,38.09 238.801,40.02L238.801,78.54C238.801,80.47 240.371,82.04 242.301,82.04C244.231,82.04 245.801,80.47 245.801,78.54L245.801,40.02C245.801,34.231 241.09,29.52 235.301,29.52L198.11,29.52C196.18,29.52 194.61,31.09 194.61,33.02C194.61,34.95 196.18,36.52 198.11,36.52Z" style="fill:rgb(142,0,150);fill-rule:nonzero;"/>
|
||||
</g>
|
||||
<g transform="matrix(1,0,0,1,-1.50684,-10.9904)">
|
||||
<path d="M115.27,82.039C117.2,82.039 118.77,80.469 118.77,78.539L118.77,40.019C118.77,38.089 120.34,36.519 122.27,36.519L159.461,36.519C161.391,36.519 162.961,34.949 162.961,33.019C162.961,31.089 161.391,29.519 159.461,29.519L122.27,29.519C116.481,29.519 111.77,34.23 111.77,40.019L111.77,78.539C111.77,80.469 113.34,82.039 115.27,82.039Z" style="fill:rgb(142,0,150);fill-rule:nonzero;"/>
|
||||
</g>
|
||||
<g transform="matrix(0.759418,0,0,0.759418,19.2308,44.2562)">
|
||||
<g transform="matrix(76.5574,0,0,76.5574,524,332.429)">
|
||||
</g>
|
||||
<text x="97.116px" y="332.429px" style="font-family:'AtkinsonHyperlegible-Regular', 'Atkinson Hyperlegible';font-size:76.557px;fill:rgb(142,0,150);">V<tspan x="138.611px " y="332.429px ">e</tspan>il<tspan x="218.001px " y="332.429px ">i</tspan>d Even<tspan x="463.137px " y="332.429px ">t</tspan>s</text>
|
||||
</g>
|
||||
</g>
|
||||
</svg>
|
||||
|
After 
(image error) Size: 7.8 KiB |
@ -79,3 +79,8 @@ figure {
|
||||
color: black;
|
||||
}
|
||||
|
||||
|
||||
|
||||
.list-style-none {
|
||||
list-style: none;
|
||||
}
|
||||
@ -172,3 +172,5 @@
|
||||
@extend .rounded;
|
||||
text-align: center;
|
||||
}
|
||||
|
||||
|
||||
|
||||
@ -25,8 +25,8 @@ Component: header
|
||||
{%- for menu in site.menus.main|sort_by_weight ~%}
|
||||
{% if loop.index0 > 0 %}
|
||||
<li class="nav-item">
|
||||
<a class="nav-link{% if url(menu.url) in url(page) %} active" aria-current="page{% else %}" href="{{ url(menu.url) }}{% endif %}">
|
||||
{% if menu.name == "Documentation" %}Docs{% else %}{{ menu.name }}{% endif %}
|
||||
<a class="{% if menu.name == "Donate" %}btn btn-success{% else %}nav-link{% endif %}{% if url(menu.url) in url(page) %} active" aria-current="page{% else %}" href="{{ url(menu.url) }}{% endif %}">
|
||||
{{ menu.name }}
|
||||
</a>
|
||||
</li>
|
||||
{% endif %}
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user