Fix link color weirdness, wording tweaks
This commit is contained in:
parent
08e930df62
commit
7de6dd9c7d
4 changed files with 35 additions and 33 deletions
|
@ -34,6 +34,7 @@
|
||||||
|
|
||||||
a {
|
a {
|
||||||
text-decoration: none;
|
text-decoration: none;
|
||||||
|
color: #fff;
|
||||||
}
|
}
|
||||||
|
|
||||||
.navItem[aria-current] {
|
.navItem[aria-current] {
|
||||||
|
|
|
@ -18,7 +18,7 @@
|
||||||
communications, anywhere on earth. FemtoStar Project members own and
|
communications, anywhere on earth. FemtoStar Project members own and
|
||||||
operate FemtoStar Inc., a Canadian corporation tasked with the ownership,
|
operate FemtoStar Inc., a Canadian corporation tasked with the ownership,
|
||||||
maintenance, and operation of the FemtoStar
|
maintenance, and operation of the FemtoStar
|
||||||
satellite constellation. However, development of the hardware and
|
satellite constellation. The FemtoStar Project's development of the hardware and
|
||||||
software that make FemtoStar possible is undertaken by our global
|
software that make FemtoStar possible is undertaken by our global
|
||||||
community of volunteer developers with experience ranging from embedded
|
community of volunteer developers with experience ranging from embedded
|
||||||
hardware, to secure telecommunications, to software development, to
|
hardware, to secure telecommunications, to software development, to
|
||||||
|
|
|
@ -221,9 +221,9 @@
|
||||||
transmit your own short pieces of data over the network, with payment
|
transmit your own short pieces of data over the network, with payment
|
||||||
in Bitcoin. While Blockstream does allow for remote access to the
|
in Bitcoin. While Blockstream does allow for remote access to the
|
||||||
Bitcoin blockchain, it is a one-way system - it cannot be used for
|
Bitcoin blockchain, it is a one-way system - it cannot be used for
|
||||||
two-way communications, or to make online cryptocurrency transactions,
|
two-way communications, or even to send (as opposed to simply observe)
|
||||||
unless you already have an internet connection and can connect to its
|
cryptocurrency transactions, unless you already have an internet connection
|
||||||
API.
|
and can connect to its API.
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
|
@ -252,7 +252,7 @@
|
||||||
<p>
|
<p>
|
||||||
We're big fans of a number of the terrestrial privacy-respecting
|
We're big fans of a number of the terrestrial privacy-respecting
|
||||||
communications projects currently in development - in fact, what is now FemtoStar
|
communications projects currently in development - in fact, what is now FemtoStar
|
||||||
<a href="./about-contact">began in concept as a terrestrial system</a>,
|
began in concept as a terrestrial system,
|
||||||
which we then called Private Mobile Data Protocol (PMDP).
|
which we then called Private Mobile Data Protocol (PMDP).
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
|
@ -328,10 +328,9 @@
|
||||||
milliseconds familiar to users of geostationary satellite networks.
|
milliseconds familiar to users of geostationary satellite networks.
|
||||||
</p>
|
</p>
|
||||||
<p>
|
<p>
|
||||||
In general, latency via low-earth orbit satellite networks, with the possible
|
In general, latency via low-earth orbit satellite networks, including FemtoStar,
|
||||||
exception of some narrowband services, is comparable to that of terrestrial
|
is comparable to that of terrestrial mobile networks, and is generally
|
||||||
mobile networks, and is generally unproblematic for most applications. This
|
unproblematic for most applications.
|
||||||
goes for FemtoStar as well.
|
|
||||||
</p>
|
</p>
|
||||||
</FAQItem>
|
</FAQItem>
|
||||||
|
|
||||||
|
@ -348,15 +347,15 @@
|
||||||
<p>
|
<p>
|
||||||
In addition to this, while the exact orbital parameters of the final
|
In addition to this, while the exact orbital parameters of the final
|
||||||
constellation are undecided at this time, the requirement to launch
|
constellation are undecided at this time, the requirement to launch
|
||||||
via typical rideshare missions usually entails deployment at orbits generally
|
via typical rideshare missions generally entails deployment at orbits typically
|
||||||
considered sufficiently self-cleaning to accomodate satellites without
|
considered sufficiently self-cleaning to accomodate satellites without
|
||||||
any onboard propulsion at all, causing them to eventually re-enter simply
|
any onboard propulsion at all, causing them to eventually re-enter simply
|
||||||
due to atmospheric drag. While satellites used in the constellation may
|
due to atmospheric drag. While satellites used in the constellation are likely to
|
||||||
raise their orbits somewhat after deployment, any satellites not intended
|
raise their orbits somewhat after deployment, any satellites not raising
|
||||||
to station-keep within the final constellation and so possibly deployed
|
their orbit into the final constellation (such a satellite that
|
||||||
without onboard propulsion (such as possible early test versions) would
|
experienced a propulsion failure during launch, or an early test satellite
|
||||||
simply remain at their deployed altitude and re-enter due to atmospheric
|
without propulsion) would simply remain at their deployed altitude and,
|
||||||
drag like a typical smallsat.
|
at end-of-life, re-enter due to atmospheric drag like a typical smallsat.
|
||||||
</p>
|
</p>
|
||||||
</FAQItem>
|
</FAQItem>
|
||||||
|
|
||||||
|
@ -365,12 +364,13 @@
|
||||||
>
|
>
|
||||||
<p>
|
<p>
|
||||||
The network can theoretically work with as little as a single
|
The network can theoretically work with as little as a single
|
||||||
satellite, however of course this configuration does not allow for
|
satellite, however of course this configuration does not allow for a
|
||||||
|
stationary user to receive
|
||||||
continuous coverage. Practical constellation layouts begin at around
|
continuous coverage. Practical constellation layouts begin at around
|
||||||
48 satellites (and include the layout shown on our <a href="./"
|
48 satellites (and include the layout shown on our <a href="./"
|
||||||
>homepage</a
|
>homepage</a
|
||||||
>). We have also considered the possibility of starting with a larger
|
>). We have considered the possibility of a larger
|
||||||
constellation of up to 96 satellites, however we believe the most
|
constellation of up to 96 satellites, however we believe that the most
|
||||||
reasonable approach would be to begin with the minimum practical
|
reasonable approach would be to begin with the minimum practical
|
||||||
number of satellites (likely 48) and then scale up the constellation
|
number of satellites (likely 48) and then scale up the constellation
|
||||||
with new satellites as needed.
|
with new satellites as needed.
|
||||||
|
@ -381,18 +381,18 @@
|
||||||
title="What if a satellite fails? Will the network become unreliable?"
|
title="What if a satellite fails? Will the network become unreliable?"
|
||||||
>
|
>
|
||||||
<p>
|
<p>
|
||||||
The FemtoStar network provides multiple levels of protection against
|
The FemtoStar network is designed to provide multiple levels of protection against
|
||||||
failure of spacecraft, and against failure of the network due to
|
failure of spacecraft, and against failure of the network due to the
|
||||||
failure of a spacecraft, resulting in a resilient network able to
|
failure of a spacecraft, resulting in a resilient network able to
|
||||||
mitigate and work around hardware failures onboard satellites. Each
|
mitigate and work around hardware failures onboard satellites. Each
|
||||||
satellite incorporates a degree of redundancy previously seen only on
|
satellite incorporates a degree of redundancy previously seen only on
|
||||||
far larger satellites, and is designed with longevity in mind. The
|
far larger satellites, and is designed with longevity in mind. The
|
||||||
network as a whole also protects against network-wide failure as a
|
network as a whole also protects against network-wide unreliability as a
|
||||||
result of the failure of a single satellite - most regions, especially
|
result of the failure of a single satellite - in the intended constellation, most regions, especially
|
||||||
those with a latitude near the inclination of the satellites (such as
|
those with a latitude near the inclination of the satellites (such as
|
||||||
North America, Europe, Oceania, and much of Asia and South America)
|
North America, Europe, Oceania, and much of Asia and South America)
|
||||||
are covered redundantly, and even elsewhere, the "gap" caused when
|
are covered redundantly, and even elsewhere, the "gap" caused when
|
||||||
the only satellite visible to a user has failed is short - lasting
|
the only satellite visible to a user has failed is usually short - lasting
|
||||||
only minutes or less before working satellites come into view.
|
only minutes or less before working satellites come into view.
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
|
@ -400,8 +400,8 @@
|
||||||
For many users, a satellite failure would likely be noticeable only as
|
For many users, a satellite failure would likely be noticeable only as
|
||||||
a decrease in the network's coverage angle, while for those in the
|
a decrease in the network's coverage angle, while for those in the
|
||||||
aforementioned near-inclination regions, it might not be noticeable at
|
aforementioned near-inclination regions, it might not be noticeable at
|
||||||
all. Finally, FemtoStar would be able to rapidly and inexpensively
|
all. Finally, we would be able to rapidly and inexpensively
|
||||||
replenish its network with new satellites, either newly-launched or
|
replenish the network with new satellites, either newly-launched or
|
||||||
simply moved into place if already available in a storage orbit.
|
simply moved into place if already available in a storage orbit.
|
||||||
</p>
|
</p>
|
||||||
</FAQItem>
|
</FAQItem>
|
||||||
|
@ -422,18 +422,19 @@
|
||||||
be a number of FemtoStar terminals installed as a part of
|
be a number of FemtoStar terminals installed as a part of
|
||||||
machine-to-machine data installations, as backup connections for
|
machine-to-machine data installations, as backup connections for
|
||||||
enterprise networks, or as backhaul to community-run terrestrial
|
enterprise networks, or as backhaul to community-run terrestrial
|
||||||
networks. A user using it for privacy reasons is indistinguishable
|
networks. A user using it because of its privacy features is indistinguishable
|
||||||
from any of these users.
|
from any of these users.
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
Additionally, by this rationale, any privacy-respecting product,
|
Additionally, by this logic, using any privacy-respecting product,
|
||||||
service, or system is bad for your privacy, as its use demonstrates
|
service, or system is counterproductive, as its use might indicate
|
||||||
that you are looking for privacy. Even if your threat model truly does
|
that you are looking for privacy. This isn't how nearly anyone actually
|
||||||
|
thinks about protecting their privacy. Even if your threat model truly does
|
||||||
require that you obscure even the fact that someone is using a system
|
require that you obscure even the fact that someone is using a system
|
||||||
that could be used for privacy-respecting communications, FemtoStar
|
that could be used for privacy-respecting communications, FemtoStar
|
||||||
still does substantially better than just about any other
|
still does substantially better than just about any other
|
||||||
privacy-respecting communications network. For one thing, it uses a
|
privacy-respecting communications network. For one thing, a FemtoStar terminal uses a
|
||||||
substantially more directional antenna than any terrestrial mobile network,
|
substantially more directional antenna than any terrestrial mobile network,
|
||||||
which means its transmitted signal is very weak in any direction but
|
which means its transmitted signal is very weak in any direction but
|
||||||
that of the satellite.
|
that of the satellite.
|
||||||
|
@ -493,7 +494,7 @@
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
A FemtoStar terminal could theoretically as a receive-only device if this
|
A FemtoStar terminal could theoretically function as a receive-only device if this
|
||||||
is acceptable for the user's use case - in this configuration, it
|
is acceptable for the user's use case - in this configuration, it
|
||||||
would likely be nearly impossible to geolocate, even with this sort of
|
would likely be nearly impossible to geolocate, even with this sort of
|
||||||
attack.
|
attack.
|
||||||
|
|
|
@ -17,7 +17,7 @@ h1 {
|
||||||
}
|
}
|
||||||
|
|
||||||
a {
|
a {
|
||||||
color: inherit;
|
color: #72bbd9;
|
||||||
}
|
}
|
||||||
|
|
||||||
code {
|
code {
|
||||||
|
|
Loading…
Reference in a new issue