Rewrite of a lot of text content, fix navbar
This commit is contained in:
parent
00231a24cc
commit
53a2fea13e
9 changed files with 246 additions and 174 deletions
|
@ -5,7 +5,7 @@
|
|||
<div class="footer-container">
|
||||
<FemtoStarLogo height={42} width={33} color="#FFFFFF75" />
|
||||
<div class="footer-text">
|
||||
Copyright 2024 - <a href="https://matrix.to/#/!COEHOXujBzfAHAVzPG:matrix.org">Matrix</a> / <a href="https://git.femtostar.com">GitLab</a> / <a href="https://twitter.com/FemtoStar">X</a>
|
||||
Copyright 2024 - <a href="https://matrix.to/#/!COEHOXujBzfAHAVzPG:matrix.org">Matrix</a> / <a href="https://git.femtostar.com">Git</a> / <a href="https://twitter.com/FemtoStar">X</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
|
|
@ -25,9 +25,9 @@
|
|||
<div class="dropdown">
|
||||
<div
|
||||
class="dropdown-name"
|
||||
class:bold={segment === "global-open-infrastructure" ||
|
||||
segment === "privacy-by-design" ||
|
||||
segment === "free-open-source"}
|
||||
class:bold={$page.url.pathname === "/global-open-infrastructure" ||
|
||||
$page.url.pathname === "/privacy-by-design" ||
|
||||
$page.url.pathname === "/free-open-source"}
|
||||
>
|
||||
more
|
||||
</div>
|
||||
|
@ -41,16 +41,16 @@
|
|||
|
||||
<NavItem
|
||||
{segment}
|
||||
href="./privacy-by-design"
|
||||
matchingSegment="/privacy-by-design"
|
||||
humanName="privacy by design"
|
||||
href="./free-open-source"
|
||||
matchingSegment="/free-open-source"
|
||||
humanName="free and open-source"
|
||||
/>
|
||||
|
||||
<NavItem
|
||||
{segment}
|
||||
href="./free-open-source"
|
||||
matchingSegment="/free-open-source"
|
||||
humanName="free and open-source"
|
||||
href="./privacy-by-design"
|
||||
matchingSegment="/privacy-by-design"
|
||||
humanName="privacy by design"
|
||||
/>
|
||||
</div>
|
||||
</div>
|
||||
|
@ -82,6 +82,7 @@
|
|||
justify-content: center;
|
||||
align-items: center;
|
||||
cursor: default;
|
||||
/*font-weight: bold;*/
|
||||
}
|
||||
|
||||
.bold {
|
||||
|
|
|
@ -33,7 +33,7 @@
|
|||
<TalkingPointName text="Global Open Infrastructure" />
|
||||
<TalkingPointContent>
|
||||
<p>
|
||||
Our satellites are open infrastructure - that means anyone can use them
|
||||
FemtoStar satellites are open infrastructure - that means anyone can use them
|
||||
without needing to go through an official gateway. This makes FemtoStar
|
||||
a flexible, open, and inherently net-neutral network, able not just to
|
||||
connect users to the services we provide, but to serve as a platform for
|
||||
|
@ -45,21 +45,6 @@
|
|||
</TalkingPointContent>
|
||||
</TalkingPointContainer>
|
||||
|
||||
<TalkingPointContainer>
|
||||
<TalkingPointName text="Privacy by design, not just by promise" />
|
||||
<TalkingPointContent>
|
||||
<p>
|
||||
Many products only promise privacy. FemtoStar is different. Privacy and
|
||||
security are verifiably baked into every part of the system, all the way
|
||||
down to the lowest level details. We couldn't violate your privacy even
|
||||
if we wanted to.
|
||||
</p>
|
||||
<p>
|
||||
<a rel="prefetch" href="./privacy-by-design">Learn more →</a>
|
||||
</p>
|
||||
</TalkingPointContent>
|
||||
</TalkingPointContainer>
|
||||
|
||||
<TalkingPointContainer>
|
||||
<TalkingPointName
|
||||
text="Free and open-source technology, built by a global community"
|
||||
|
@ -78,6 +63,22 @@
|
|||
</TalkingPointContent>
|
||||
</TalkingPointContainer>
|
||||
|
||||
<TalkingPointContainer>
|
||||
<TalkingPointName text="Privacy by design, not just by promise" />
|
||||
<TalkingPointContent>
|
||||
<p>
|
||||
Many products merely promise privacy. FemtoStar is different. Privacy and
|
||||
security are baked into every part of the system, all the way
|
||||
down to the lowest level details. Unlike any other wide-area telecommunications network,
|
||||
FemtoStar offers verifiable guarantees that user privacy is unconditionally
|
||||
protected.
|
||||
</p>
|
||||
<p>
|
||||
<a rel="prefetch" href="./privacy-by-design">Learn more →</a>
|
||||
</p>
|
||||
</TalkingPointContent>
|
||||
</TalkingPointContainer>
|
||||
|
||||
<PartnerContainer />
|
||||
</div>
|
||||
|
||||
|
|
|
@ -15,11 +15,11 @@
|
|||
<p>
|
||||
The FemtoStar Project is a global community of developers working
|
||||
towards one common goal - better, more open, and more private
|
||||
communications, anywhere on earth. At the core of the FemtoStar Project
|
||||
is FemtoStar Inc., a Canadian corporation wholly owned by FemtoStar
|
||||
Project members and tasked with ownership and operation of the FemtoStar
|
||||
communications, anywhere on earth. FemtoStar Project members own and
|
||||
operate FemtoStar Inc., a Canadian corporation tasked with the ownership,
|
||||
maintenance, and operation of the FemtoStar
|
||||
satellite constellation. However, development of the hardware and
|
||||
software that make FemtoStar possible is undertaken by a global
|
||||
software that make FemtoStar possible is undertaken by our global
|
||||
community of volunteer developers with experience ranging from embedded
|
||||
hardware, to secure telecommunications, to software development, to
|
||||
aerospace.
|
||||
|
@ -46,28 +46,34 @@
|
|||
website or of our satellite, then dot com. </span>h<span class="c">
|
||||
</span>e<span class="c">Lorem</span>l<span class="j">ipsum</span>l<span class="c">dolor</span>o<span class="c">sit</span> а<span class="c">amet</span>t
|
||||
f<span class="c">consectetur</span>e<span class="j">adipiscing</span>m<span class="c">elit</span>t<span class="c">Sed</span>o<span class="j">dolor</span>s<span class="c">sem</span>t<span class="c">lacinia</span>a<span class="c">ac</span>r
|
||||
d<span class="c">euismod</span>о<span class="j">vitae</span>t c<span class="c">hendrerit</span>o<span class="j">sit</span>m (if you have Tutanota, you can send end-to-end encrypted mail here too).
|
||||
d<span class="c">euismod</span>о<span class="j">vitae</span>t c<span class="c">hendrerit</span>o<span class="j">sit</span>m.
|
||||
</p>
|
||||
</TalkingPointContent>
|
||||
</TalkingPointContainer>
|
||||
|
||||
<!--
|
||||
|
||||
this section was severely out-of-date and is now entirely duplicative of information also
|
||||
on the FAQ page - it's been commented out for now, but could return if someone cares
|
||||
to rewrite it
|
||||
|
||||
<TalkingPointContainer>
|
||||
<TalkingPointName text="History" />
|
||||
<TalkingPointContent>
|
||||
<p>
|
||||
Development of what is now FemtoStar began with a project named Private
|
||||
Development of what is now FemtoStar began with a concept named Private
|
||||
Mobile Data Protocol (PMDP). While PMDP was intended to be a terrestrial
|
||||
network, many of the design elements now used in the FemtoStar Protocol
|
||||
were initially designed for this project. A series of tests in
|
||||
real-world urban and suburban environments throughout 2019 led to the
|
||||
conclusion that, without a dense network and an impractically large
|
||||
number of towers, reasonable coverage, even only at low speeds and only
|
||||
number of towers, providing reasonable coverage, even if only at low speeds and only
|
||||
within city centers, was impractical with a license-free terrestrial
|
||||
network.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
In early 2020, the decision was made to research the implementation of a
|
||||
In early 2020, we decided to research the implementation of a
|
||||
PMDP-like network in a Mobile Satellite Service (MSS) system. While
|
||||
Mobile Satellite Service hardware (such as satellite phones, portable
|
||||
satellite internet terminals, and machine-to-machine/IoT satellite data
|
||||
|
@ -79,21 +85,21 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
Within a month, a basic plan had been developed, and many of the
|
||||
remaining problems of the PMDP protocol (such as its lack of any
|
||||
mechanism for payment for service) had been solved. The core of the
|
||||
proposed network was a constellation of very small communications
|
||||
satellites - a design we named FemtoStar.
|
||||
By mid-2020, a plan had been developed, and many of the
|
||||
remaining problems of PMDP (such as its lack of any mechanism for payment
|
||||
for service, without which "free" DDoS attacks on the network would have
|
||||
been possible) had been solved. The core of the proposed network was now
|
||||
a constellation of very small communications satellites - a design we
|
||||
named FemtoStar.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
As the FemtoStar Project grew, development continued throughout 2020. In
|
||||
2021, FemtoStar Inc. was incorporated in Canada as an entity to own and
|
||||
In 2021, FemtoStar Inc. was incorporated in Canada as an entity to own and
|
||||
operate the FemtoStar satellite constellation on behalf of the FemtoStar
|
||||
Project.
|
||||
Project.
|
||||
</p>
|
||||
</TalkingPointContent>
|
||||
</TalkingPointContainer>
|
||||
</TalkingPointContainer>-->
|
||||
</div>
|
||||
|
||||
<style>
|
||||
|
|
|
@ -13,8 +13,8 @@
|
|||
<TalkingPointName text="Donations" />
|
||||
<TalkingPointContent>
|
||||
<p>
|
||||
The FemtoStar Project is a community of volunteers funded by a grant from our partner NLnet,
|
||||
out-of-pocket by some of our members, and from donations by our community. Nobody is required
|
||||
The FemtoStar Project is a community of volunteers, to date funded primarily out-of-pocket by some of our members,
|
||||
and from donations by our community. Nobody is required
|
||||
to donate, and we currently don't have much in terms of perks for donors, but if you'd like to see
|
||||
this project succeed and are able to, consider throwing a few dollars our way or setting up
|
||||
a recurring donation through Liberapay.
|
||||
|
@ -31,9 +31,16 @@
|
|||
<TalkingPointName text="Donate via PayPal" />
|
||||
<TalkingPointContent>
|
||||
<p>
|
||||
Via PayPal, we accept both one-time donations directly via PayPal, and recurring donations via Liberapay
|
||||
We accept both one-time donations directly via PayPal, and recurring donations via Liberapay
|
||||
(processed using PayPal).
|
||||
</p>
|
||||
<p>
|
||||
Since PayPal required our account to belong to a specific legal entity, PayPal
|
||||
donations go to FemtoStar Inc., and are used to purchase components and produce prototype hardware for
|
||||
use by the FemtoStar Project. FemtoStar Inc. is owned and operated entirely by FemtoStar Project volunteers,
|
||||
and exists to assist the FemtoStar Project in production of hardware, and in ownership and operation of the
|
||||
FemtoStar Network (see <a href="/faq">our FAQ</a> for further details).
|
||||
</p>
|
||||
<p>
|
||||
<b>PayPal (one-time donation):</b> <a href="https://www.paypal.com/donate/?hosted_button_id=M2N5N2B624CNQ&source=url">Click Here</a>
|
||||
</p>
|
||||
|
@ -51,10 +58,15 @@
|
|||
one of the following addresses.
|
||||
</p>
|
||||
<p>
|
||||
<b>Bitcoin:</b> <span class="crypto-address">bc1qnytm8arpuz247622yef070nvxx56qp6dqwl80s</span>
|
||||
These addresses go to wallets controlled by a group of core FemtoStar Project volunteers. Donations to them are used to cover
|
||||
hosting and domain costs, purchase hardware and tools, and otherwise support FemtoStar Project development
|
||||
directly.
|
||||
</p>
|
||||
<p>
|
||||
<b>Monero:</b> <span class="crypto-address">83YcY9dsxARYkS4AaKVNkEJTLMQnuvuzSSij9vC7SqU7eriCpHHBsrs2ijKE6MQjobUShY4D2kjQTZ3XXp7WMtR7PdjKrx9</span>
|
||||
<b>Bitcoin:</b> <span class="crypto-address"><a target="_blank" href="bitcoin:bc1qnytm8arpuz247622yef070nvxx56qp6dqwl80s?label=FemtoStar%20Donation">bc1qnytm8arpuz247622yef070nvxx56qp6dqwl80s</a></span>
|
||||
</p>
|
||||
<p>
|
||||
<b>Monero:</b> <span class="crypto-address"><a target="_blank" href="monero:86EMaQV5nfKMZ8HowG9RTugLdu7tV8MqgHvTvV2qwXEsXAMBMVZMQ2AgwsKhxqZEiM8nTruWPrp6YcdvAv4WveiXFSTbRnu?tx_description=FemtoStar%20Donation">86EMaQV5nfKMZ8HowG9RTugLdu7tV8MqgHvTvV2qwXEsXAMBMVZMQ2AgwsKhxqZEiM8nTruWPrp6YcdvAv4WveiXFSTbRnu</a></span>
|
||||
</p>
|
||||
</TalkingPointContent>
|
||||
</TalkingPointContainer>
|
||||
|
@ -64,8 +76,9 @@
|
|||
<TalkingPointContent>
|
||||
<p>
|
||||
If you would like to donate via a method not listed above (such as via
|
||||
a different payment processor or in a different cryptocurrency), please
|
||||
<a href="about-contact/">contact us</a> and we'd be glad to help set something up.
|
||||
a different payment processor or in a different cryptocurrency), or if you
|
||||
want more information before you donate, please
|
||||
<a href="about-contact/">contact us</a> and we'd be glad to help you.
|
||||
</p>
|
||||
</TalkingPointContent>
|
||||
</TalkingPointContainer>
|
||||
|
|
|
@ -56,14 +56,14 @@
|
|||
</FAQItem>
|
||||
|
||||
<FAQItem title="Who makes FemtoStar terminals?">
|
||||
FemtoStar plans to take a hybrid approach to manufacturing and selling
|
||||
terminals. FemtoStar's higher-sales-volume "core" user terminals will be
|
||||
The FemtoStar Project intends to take a hybrid approach to terminal
|
||||
manufacturing and sales. Higher-volume "core" user terminals will be
|
||||
manufactured and sold primarily by hardware partners, allowing us to
|
||||
leverage existing manufacturing and sales infrastructure. Meanwhile,
|
||||
development and reference hardware, as well as more specialized
|
||||
terminals will be made in Canada by FemtoStar, at the same facility
|
||||
where we build our satellites. Every FemtoStar terminal is based on
|
||||
FemtoStar-developed reference designs.
|
||||
terminals will be made in Canada by FemtoStar Inc., at the same facility
|
||||
where build our satellites. Every FemtoStar terminal is based on
|
||||
FemtoStar Project-developed reference designs.
|
||||
</FAQItem>
|
||||
|
||||
<FAQItem title="What speeds do you anticipate being available?">
|
||||
|
@ -84,7 +84,7 @@
|
|||
BGAN, Iridium Certus, or Thuraya IP. In these services, as in
|
||||
FemtoStar, designing for this middle category means that users can
|
||||
expect performance much better than a narrowband system, while still
|
||||
having a portable terminal much smaller than those needed for
|
||||
having a truly-portable terminal much smaller than those needed for
|
||||
broadband systems. Like the aforementioned MSS options, a typical
|
||||
FemtoStar terminal should provide in the mid-hundreds of kbps, using a
|
||||
terminal roughly the size of a tablet or small laptop.
|
||||
|
@ -94,7 +94,7 @@
|
|||
Of course, FemtoStar's design still allows for flexibility on the size
|
||||
and speed of terminals - users should be able to choose their own
|
||||
balance between speed, cost, and portability. As such, depending on
|
||||
the size of the terminal, FemtoStar should be able to accomodate
|
||||
the size of the terminal, the FemtoStar network should be able to accomodate
|
||||
larger terminals in the megabits-per-second range, or smaller
|
||||
terminals with reduced (if still better than typical narrowband
|
||||
offerings) speeds in a pocket-sized form factor.
|
||||
|
@ -103,29 +103,58 @@
|
|||
|
||||
<FAQItem title="Is the FemtoStar Credit Token a cryptocurrency?">
|
||||
<p>
|
||||
No, at least not by any usual definition of the term. While they are a
|
||||
No, at least not by any usual definition of the term. While the Credit Token system is a
|
||||
digital system used to pay for service, and while they do make use of
|
||||
cryptographic signatures for security, FemtoStar Credit Tokens are not
|
||||
transacted on a blockchain, cannot be mined, and are not intended for
|
||||
use as anything other than payment for FemtoStar service. While
|
||||
third-party users are free to buy and sell Credit Tokens at any price
|
||||
they are able to, their value in FemtoStar service is fixed.
|
||||
use as anything other than payment for FemtoStar service.
|
||||
</p>
|
||||
</FAQItem>
|
||||
|
||||
<FAQItem title="How do I buy FemtoStar tokens? Are they available yet?">
|
||||
<p>
|
||||
Once our network is operational, you will be able to purchase
|
||||
FemtoStar tokens from FemtoStar via a retail token sales portal, from
|
||||
a third-party reseller, in bulk from FemtoStar via a wholesale
|
||||
agreement, or from anyone else willing to sell them to you. While the
|
||||
FemtoStar Project is capable of pre-issuing tokens that will be usable
|
||||
once the network is operational, we do not currently offer pre-issued
|
||||
retail tokens to the general public, due to the inherent risk to
|
||||
FemtoStar tokens from FemtoStar Inc. via a retail token sales portal, from
|
||||
a third-party reseller, or in bulk via a wholesale
|
||||
agreement. While FemtoStar Inc. would be capable of pre-issuing tokens that would be usable
|
||||
once the network was operational, they are not yet available for sale, due to the inherent risk to
|
||||
consumers of purchasing a service before it is available. If you are
|
||||
interested in working with us to purchase wholesale tokens, for resale
|
||||
interested in working with FemtoStar Inc.
|
||||
as a token reseller or for a large deployment of FemtoStar hardware as
|
||||
an enterprise user, please <a href="./about-contact">contact us</a>.
|
||||
an enterprise user, please contact
|
||||
|
||||
<span class="j">This address has been hidden to prevent spam being received. If you are reading this website as plain text or through a screen reader, the correct address is the word inc, that's I. N. C., then the symbol spelled with the letter before B and then the letter after S, then the name of this
|
||||
website or of our satellite, then dot com. </span>i<span class="c">
|
||||
</span><span class="c">Lorem</span>n<span class="j">ipsum</span><span class="c">dolor</span>c<span class="c">sit</span> а<span class="c">amet</span>t
|
||||
f<span class="c">consectetur</span>e<span class="j">adipiscing</span>m<span class="c">elit</span>t<span class="c">Sed</span>o<span class="j">dolor</span>s<span class="c">sem</span>t<span class="c">lacinia</span>a<span class="c">ac</span>r
|
||||
d<span class="c">euismod</span>о<span class="j">vitae</span>t c<span class="c">hendrerit</span>o<span class="j">sit</span>m.
|
||||
|
||||
</p>
|
||||
</FAQItem>
|
||||
|
||||
<FAQItem title="Who is the FemtoStar Project? Who is FemtoStar Inc.?">
|
||||
<p>
|
||||
The FemtoStar Project is a global volunteer community of developers, working on
|
||||
technology for global, open communications infrastructure. For more
|
||||
information about the FemtoStar Project, or to contact us, see
|
||||
<a href="./about-contact">about & contact</a>.
|
||||
</p>
|
||||
<p>
|
||||
FemtoStar Inc., located in Canada, is the company tasked with the manufacturing
|
||||
and operation of the FemtoStar satellite constellation, based on the free and
|
||||
open-source designs and specifications developed and published by the FemtoStar
|
||||
Project.
|
||||
</p>
|
||||
<p>
|
||||
FemtoStar Inc. exists to provide the FemtoStar Project with an entity which
|
||||
can manufacture the satellites, hold licenses for the constellation, purchase
|
||||
services such as satellite launch or component fabrication, and can handle
|
||||
the day-to-day operation of the constellation once operational. While
|
||||
FemtoStar Inc. consists entirely of FemtoStar Project members, and exists
|
||||
to manufacture and operate the system developed by the FemtoStar Project,
|
||||
the FemtoStar Project is entirely independent of FemtoStar Inc., and its developments
|
||||
are freely usable, even outside the context of the network operated by
|
||||
FemtoStar Inc.
|
||||
</p>
|
||||
</FAQItem>
|
||||
</TalkingPointContent>
|
||||
|
@ -139,11 +168,11 @@
|
|||
<a href="https://starlink.com">Starlink</a> is a low-earth-orbit communications
|
||||
constellation developed by SpaceX. While we have a tremendous amount of
|
||||
respect for the engineering accomplishments of the Starlink network, its
|
||||
goals and those of FemtoStar are almost entirely separate. While both intend
|
||||
goals and those of FemtoStar are largely separate. While both intend
|
||||
to provide satellite communications service using low-earth orbit constellations,
|
||||
Starlink is designed to provide consumer broadband services to large, fixed
|
||||
Starlink is designed primarily to provide consumer broadband services to large, fixed
|
||||
terminals (in the satellite industry, this is known as Fixed Satellite
|
||||
Service). FemtoStar, on the other hand, is designed for midband services
|
||||
Service). FemtoStar, on the other hand, is designed for truly-mobile midband services
|
||||
to small and medium, portable or in-motion terminals (also known as Mobile
|
||||
Satellite Service).
|
||||
</p>
|
||||
|
@ -164,16 +193,16 @@
|
|||
|
||||
<p>
|
||||
Starlink terminals are uniquely identified on the network, and can be
|
||||
easily geolocated by the network (whether they report their GPS
|
||||
location is currently unknown, but the network is certainly able to
|
||||
geolocate them accurately, as they are disallowed from accessing the
|
||||
readily geolocated by the network, as they are often disallowed from accessing the
|
||||
network outside of the small region, or "cell", where their user's
|
||||
address is registered). Starlink users are required to provide a
|
||||
substantial amount of personal information in order to purchase
|
||||
service. Payments are handled on ground infrastructure, based on user
|
||||
accounts. FemtoStar does not require any user account whatsoever, is
|
||||
not restricted to use in a small cell, and handles payments on the
|
||||
satellite itself using FemtoStar Credit Tokens.
|
||||
address is registered. Starlink users are required to provide a
|
||||
significant amount of personal information in order to purchase
|
||||
service, in line with traditional telecommunications services. Payments for service
|
||||
are handled on ground infrastructure, based on user accounts, and generally
|
||||
are not possible using privacy-respecting payment methods. FemtoStar users
|
||||
do not require any user account whatsoever, and payments are handled on the satellite
|
||||
itself using FemtoStar Credit Tokens. Geolocation of FemtoStar users by the FemtoStar
|
||||
network is, by design, infeasible.
|
||||
</p>
|
||||
</FAQItem>
|
||||
|
||||
|
@ -222,9 +251,9 @@
|
|||
>
|
||||
<p>
|
||||
We're big fans of a number of the terrestrial privacy-respecting
|
||||
communications projects currently in development - in fact, FemtoStar <a
|
||||
href="./about-contact">began as a terrestrial network</a
|
||||
>, named Private Mobile Data Protocol (PMDP).
|
||||
communications projects currently in development - in fact, what is now FemtoStar
|
||||
<a href="./about-contact">began in concept as a terrestrial system</a>,
|
||||
which we then called Private Mobile Data Protocol (PMDP).
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
@ -237,11 +266,12 @@
|
|||
> to build mainstream cellular networks out to their current coverage,
|
||||
and even with this it's likely you still sometimes have problems getting
|
||||
cellular service. We began with the assumption that a terrestrial network
|
||||
would be the only practical solution, and extensively tested PMDP hardware
|
||||
in real-world urban and suburban environments. Eventually, even we - the
|
||||
developers of the technology - were forced to admit that it was impractical
|
||||
without an impractically dense network, even for a small, urban implementation
|
||||
- letalone regional or global coverage.
|
||||
would be the only practical solution, and extensively tested a variety of
|
||||
popular license-free radio hardware - including LoRa, 802.11, and 802.15.4 transceivers -
|
||||
in real-world urban and suburban environments. Eventually, we were forced to
|
||||
admit that a workable community-operated mobile telecommunications network would be impractical
|
||||
in all but the most densely-populated areas, and even there only with the
|
||||
right combination of ideally-situated transceivers and minimal obstruction by structures.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
@ -250,10 +280,11 @@
|
|||
kilometer (3200 feet) away from somewhere a mesh node or base station
|
||||
in a community-run terrestrial network could be installed without
|
||||
being removed, stolen, or tampered with, and if anyone nearby would be
|
||||
willing to pay for, install, and maintain such a device. We tried
|
||||
this, with real hardware, in a real city, in 2019, and came to the
|
||||
conclusion that that, in contrast to being an easier solution, it was
|
||||
likely outright impossible in most circumstances.
|
||||
willing to purchase, install, and maintain such a device. We installed a
|
||||
series of LoRa transceivers in a real city in 2019 as a test of our PMDP
|
||||
concept, mapped their coverage under a variety of conditions, and came to
|
||||
the conclusion that that, rather than being an easier solution, such a
|
||||
network was likely outright impossible in most circumstances.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
@ -276,7 +307,7 @@
|
|||
extend coverage, this still does not allow for coverage where there
|
||||
are no nodes. The same thought experiment applies - are you always
|
||||
within a kilometer of someone else who might have a node in the mesh?
|
||||
If you have your own node in the mesh, is there ever another node
|
||||
If you have your own node in the mesh, is there often another node
|
||||
nearby for it to mesh with? If not, a mesh network may not be
|
||||
practical in your situation. Even where mesh networks are practical,
|
||||
FemtoStar could still be used to interconnect regions where the mesh
|
||||
|
@ -289,28 +320,43 @@
|
|||
title="I've used satellite internet, and the latency is pretty bad - is this true of FemtoStar too?"
|
||||
>
|
||||
<p>
|
||||
Not to nearly the same degree. While the distance to the satellite
|
||||
If the service you have used was via a geostationary network, then
|
||||
not to nearly the same degree. While the distance to the satellite
|
||||
does add some amount of latency due to the time taken for the signal
|
||||
to reach the satellite, the round-trip propagation time to a low-earth
|
||||
orbit satellite is a handful of milliseconds, not the hundreds of
|
||||
milliseconds familiar to users of geostationary satellite networks.
|
||||
Ping time on FemtoStar should be less than a tenth of that which a
|
||||
geostationary satellite user would experience, if even that.
|
||||
</p>
|
||||
<p>
|
||||
In general, latency via low-earth orbit satellite networks, with the possible
|
||||
exception of some narrowband services, is comparable to that of terrestrial
|
||||
mobile networks, and is generally unproblematic for most applications. This
|
||||
goes for FemtoStar as well.
|
||||
</p>
|
||||
</FAQItem>
|
||||
|
||||
<FAQItem title="How do you plan to mitigate orbital debris?">
|
||||
<p>
|
||||
In contrast to the vast majority of small satellites, FemtoStar plans
|
||||
to include electric propulsion onboard our satellites, allowing them
|
||||
to be repositioned as needed and cleanly deorbited at end-of-life. The
|
||||
FemtoStar Project is working closely with Applied Ion Systems, a
|
||||
leading developer of open-hardware smallsat propulsion hardware, to
|
||||
develop a specialized implementation of their technology for use
|
||||
onboard the FemtoStar space vehicle. Even in the event of a thruster
|
||||
failure, the solar panel can be positioned to drastically increase
|
||||
atmospheric drag on the satellite, rapidly increasing orbital decay
|
||||
and deorbiting the satellite.
|
||||
to include electric propulsion onboard the satellites used in our
|
||||
constellation, allowing them to be repositioned as needed and cleanly
|
||||
deorbited at end-of-life. The FemtoStar Project is working closely with
|
||||
Applied Ion Systems, a leading developer of open-hardware smallsat
|
||||
propulsion hardware, to develop a specialized implementation of their
|
||||
technology for use onboard our satellite.
|
||||
</p>
|
||||
<p>
|
||||
In addition to this, while the exact orbital parameters of the final
|
||||
constellation are undecided at this time, the requirement to launch
|
||||
via typical rideshare missions usually entails deployment at orbits generally
|
||||
considered sufficiently self-cleaning to accomodate satellites without
|
||||
any onboard propulsion at all, causing them to eventually re-enter simply
|
||||
due to atmospheric drag. While satellites used in the constellation may
|
||||
raise their orbits somewhat after deployment, any satellites not intended
|
||||
to station-keep within the final constellation and so possibly deployed
|
||||
without onboard propulsion (such as possible early test versions) would
|
||||
simply remain at their deployed altitude and re-enter due to atmospheric
|
||||
drag like a typical smallsat.
|
||||
</p>
|
||||
</FAQItem>
|
||||
|
||||
|
@ -323,7 +369,7 @@
|
|||
continuous coverage. Practical constellation layouts begin at around
|
||||
48 satellites (and include the layout shown on our <a href="./"
|
||||
>homepage</a
|
||||
>. We have also considered the possibility of starting with a larger
|
||||
>). We have also considered the possibility of starting with a larger
|
||||
constellation of up to 96 satellites, however we believe the most
|
||||
reasonable approach would be to begin with the minimum practical
|
||||
number of satellites (likely 48) and then scale up the constellation
|
||||
|
@ -343,15 +389,15 @@
|
|||
far larger satellites, and is designed with longevity in mind. The
|
||||
network as a whole also protects against network-wide failure as a
|
||||
result of the failure of a single satellite - most regions, especially
|
||||
those with a latitude near the inclination of the satellites such as
|
||||
North America Europe, and Oceania, and much of Asia and South America
|
||||
- are covered redundantly, and even elsewhere, the "gap" caused when
|
||||
those with a latitude near the inclination of the satellites (such as
|
||||
North America, Europe, Oceania, and much of Asia and South America)
|
||||
are covered redundantly, and even elsewhere, the "gap" caused when
|
||||
the only satellite visible to a user has failed is short - lasting
|
||||
only minutes or less before working satellites come into view.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
For most 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
|
||||
aforementioned near-inclination regions, it might not be noticeable at
|
||||
all. Finally, FemtoStar would be able to rapidly and inexpensively
|
||||
|
@ -388,19 +434,18 @@
|
|||
that could be used for privacy-respecting communications, FemtoStar
|
||||
still does substantially better than just about any other
|
||||
privacy-respecting communications network. For one thing, it uses a
|
||||
substantially more directional antenna than any terrestrial mobile,
|
||||
substantially more directional antenna than any terrestrial mobile network,
|
||||
which means its transmitted signal is very weak in any direction but
|
||||
that of the satellite.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Its connection to the satellite is also is encrypted, and even to the
|
||||
satellite, it does not contain a location, terminal identifier, user
|
||||
account, or any other identifying details. The terminal never
|
||||
transmits when it has no session open with the satellite, and, unlike
|
||||
mesh network nodes, it cannot be made to transmit by the traffic of
|
||||
another user unless the terminal's owner has chosen to operate their
|
||||
own service over the network.
|
||||
A user's traffic to the satellite is also is encrypted, and never includes
|
||||
a location, terminal identifier, user account, or any other identifying
|
||||
details about the user. The terminal never transmits when it has no session open with
|
||||
the satellite, and, unlike mesh network nodes, it cannot be made to transmit
|
||||
by the traffic of another user unless the terminal's owner has chosen to
|
||||
operate their own service over the network.
|
||||
</p>
|
||||
</FAQItem>
|
||||
|
||||
|
@ -408,20 +453,16 @@
|
|||
title="Don't FemtoStar's satellites have to know where I am, based on which beam I use?"
|
||||
>
|
||||
<p>
|
||||
In theory, to some extent, but in practice, not meaningfully. In
|
||||
contrast to traditional communications satellites, a FemtoStar
|
||||
satellite, at least for transmit, does not have a consistent beam
|
||||
pattern. Instead, electronic beamforming is used to point each of only
|
||||
a handful of beams, rapidly switching beam patterns as the satellite
|
||||
jumps between active sessions. The footprints within which these beams
|
||||
are usable are hundreds of kilometers across, even at their narrowest,
|
||||
and more than 2000 kilometers long. In addition, knowing where "you"
|
||||
are, as opposed to just knowing the rough area in which one of the
|
||||
network's users is located, requires knowing who you are. As such, the
|
||||
satellite could determine that an anonymous session is within, for
|
||||
example, northern Europe, western North America, or eastern Asia, but
|
||||
not that it is in a particular country or city, and certainly not who
|
||||
that session belongs to.
|
||||
In theory, to some extent, but in practice, not meaningfully. A FemtoStar
|
||||
satellite has only a handful of beams in use at any given moment, and
|
||||
the footprints within which these beams are usable are between 1000
|
||||
and 4000 kilometers across each, depending on your coverage angle. In addition,
|
||||
knowing where "you" are, as opposed to just knowing the rough area in which
|
||||
one of the network's users is located, requires knowing who you are.
|
||||
As such, the satellite could determine that an anonymous session is
|
||||
within, for example, northern Europe, western North America, or eastern
|
||||
Asia, but not that it is in a particular country or city, and certainly not
|
||||
who that session belongs to.
|
||||
</p>
|
||||
</FAQItem>
|
||||
|
||||
|
@ -452,7 +493,7 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
A FemtoStar terminal can even be used as a receive-only device if this
|
||||
A FemtoStar terminal could theoretically as a receive-only device if this
|
||||
is acceptable for the user's use case - in this configuration, it
|
||||
would likely be nearly impossible to geolocate, even with this sort of
|
||||
attack.
|
||||
|
@ -491,15 +532,14 @@
|
|||
</FAQItem>
|
||||
|
||||
<FAQItem
|
||||
title="FemtoStar Inc. is Canadian - what if I don't trust Canada?"
|
||||
title="What if I don't trust whatever place the FemtoStar Project is run from?"
|
||||
>
|
||||
<p>
|
||||
See the above point. Even if a malicious government were to take over
|
||||
the FemtoStar Project and attempt to surveil its users, they would be
|
||||
FemtoStar Inc., or some part of the development work under the FemtoStar
|
||||
Project, and attempt to surveil the network's users, they would be
|
||||
incapable of doing so without making changes that would be immediately
|
||||
obvious to users, and to our own developers in other countries.
|
||||
Additionally FemtoStar Inc. in Canada is only one part of the
|
||||
overarching FemtoStar Project - we have developers all over the world.
|
||||
</p>
|
||||
</FAQItem>
|
||||
|
||||
|
@ -515,18 +555,17 @@
|
|||
The most important point here is that FemtoStar satellites are not
|
||||
especially useful targets to an attacker. Due to not being a trusted
|
||||
part of the network, even if they themselves are fully compromised,
|
||||
they cannot be used to compromise FemtoStar users, nor would they be
|
||||
much use as part of a botnet, nor would they provide an attacker with
|
||||
any additional utility in their intended purpose (communications) than
|
||||
is available officially.
|
||||
they cannot be used to compromise the security of FemtoStar users,
|
||||
nor would they be much use as part of a botnet, nor would they provide
|
||||
an attacker with any additional utility in their intended purpose
|
||||
(communications) than would be available officially.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
With regards to compromising the satellites from the ground, the
|
||||
satellite's onboard software is subject to intense scrutiny, including
|
||||
through formal proofs, makes extensive use of sandboxing, and, given
|
||||
the relative simplicity of the FemtoStar protocol, presents a small
|
||||
attack surface.
|
||||
through formal proofs of critical components, and, given the relative
|
||||
simplicity of the FemtoStar protocol, presents a small attack surface.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
@ -534,7 +573,7 @@
|
|||
infrastructure in orbit certainly grants it a degree of
|
||||
inaccessibility compared to terrestrial infrastructure, there are of
|
||||
course spacecraft which could conceivably reach a FemtoStar satellite,
|
||||
and could hypothetically either tamper with or replace it. However,
|
||||
and an attack could be imagined which might either tamper with or replace it. However,
|
||||
tampering would require physical capture and substantial disassembly
|
||||
of the satellite, which is detectable and would result in the deletion
|
||||
of onboard keys, resulting in a tampered-with satellite being easily
|
||||
|
@ -544,15 +583,14 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
An attacker could opt to attempt to disable, capture, or destroy a
|
||||
satellite altogether - after all, if you want to assume that truly no
|
||||
adversary is off the table, you could choose to consider even the use
|
||||
of anti-satellite weapons. However, an attacker trying to make the
|
||||
If you truly want to assume that <i>no</i> attacker is off the table, then
|
||||
an attacker could opt to attempt to disable, capture, or destroy a
|
||||
satellite altogether. However, an attacker trying to make the
|
||||
network truly unusable would need to destroy or disable not just one
|
||||
satellite, but the entire constellation, and any replacement
|
||||
satellites, and to do so in a way which obscured their involvement, a
|
||||
daunting task even for the largest possible adversaries. This type of
|
||||
attack is also immediately obvious (especially if the satellite is
|
||||
satellite, but the bulk of the constellation, and any replacement
|
||||
satellites, and, presumably, would wish to do so in a way which obscured
|
||||
their involvement, a daunting task even for the largest possible adversaries.
|
||||
This type of attack is also immediately obvious (especially if the satellite is
|
||||
physically destroyed, resulting in the generation of orbital debris),
|
||||
and even this still does not result in an actual compromise
|
||||
(geolocation, identification, etc.) of FemtoStar users.
|
||||
|
@ -572,4 +610,16 @@
|
|||
padding-left: 2em;
|
||||
padding-right: 2em;
|
||||
}
|
||||
.c{
|
||||
overflow: hidden;
|
||||
height: 0px;
|
||||
width: 0px;
|
||||
position: absolute;
|
||||
}
|
||||
.j{
|
||||
overflow: hidden;
|
||||
height: 0px;
|
||||
width: 0px;
|
||||
position: absolute;
|
||||
}
|
||||
</style>
|
||||
|
|
|
@ -17,9 +17,9 @@
|
|||
<p>
|
||||
From the user terminal, to the spacecraft, to the ground station,
|
||||
FemtoStar is powered by free and open-source hardware and software, and
|
||||
we don't just mean the high-level stuff. Notably, in a world first for
|
||||
wide-area communications networks, even the FemtoStar air interface and
|
||||
the low-level radio firmware implementing it will be free and
|
||||
we don't just mean the high-level stuff. Notably, in what we believe to be
|
||||
a world first for wide-area communications networks, even the FemtoStar
|
||||
air interface and the low-level radio firmware implementing it will be free and
|
||||
open-source software.
|
||||
</p>
|
||||
<p>
|
||||
|
@ -33,8 +33,8 @@
|
|||
effective as a piece of open infrastructure - you can build on top of
|
||||
it, or integrate it into your own products and services. It's what gives
|
||||
FemtoStar the flexibility to work just as well as an internal backup
|
||||
network for a business as it does as a portable mobile internet
|
||||
terminal.
|
||||
network for a business or a low-data-rate M2M service as it does as a
|
||||
mobile internet hotspot service.
|
||||
</p>
|
||||
<p>
|
||||
It also allows our users to verify our claims about privacy and
|
||||
|
|
|
@ -14,7 +14,7 @@
|
|||
<TalkingPointContent>
|
||||
<p>
|
||||
Like any satellite communications system, FemtoStar uses a network of
|
||||
satellites to allow communications between terminals on earth.
|
||||
satellites to allow communications between terminals on Earth.
|
||||
Traditional communications satellites - both those that act as simple
|
||||
repeaters, and those with onboard routing - fundamentally work by
|
||||
shuffling data to and from user terminals via a separate,
|
||||
|
@ -25,23 +25,23 @@
|
|||
FemtoStar breaks this distinction. All user hardware can be used both to
|
||||
connect to and to operate services, directly via the satellites. There
|
||||
are no special "feeder" links, and no prior arrangement with FemtoStar
|
||||
is required to operate a service. Credit processing takes place
|
||||
is required to operate a service. Credit Token processing takes place
|
||||
on-satellite, and works even when no official ground station is
|
||||
available.
|
||||
</p>
|
||||
<p>
|
||||
FemtoStar is also developing FemtoStar Real-Time Core Services (RTCS),
|
||||
The FemtoStar Project is also developing FemtoStar Real-Time Core Services (RTCS),
|
||||
an open standard for basic communications services such as internet
|
||||
access over the FemtoStar network. RTCS is intended to provide a global
|
||||
baseline in FemtoStar-based service, and will be supported by all of our
|
||||
own ground stations. We encourage RTCS adoption at third-party ground
|
||||
stations
|
||||
baseline in FemtoStar-based service, and will be supported by every ground
|
||||
station operated by FemtoStar Inc. We encourage RTCS adoption at all third-party ground
|
||||
stations.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
It's not just services either - the FemtoStar terminal will be released
|
||||
as an open standard, with an open-hardware reference design, and
|
||||
FemtoStar will work with third-party terminal manufacturers to license
|
||||
FemtoStar Inc. will work with third-party terminal manufacturers to license
|
||||
third-party terminals for use on the FemtoStar network.
|
||||
</p>
|
||||
</TalkingPointContent>
|
||||
|
|
|
@ -40,15 +40,15 @@
|
|||
up the connection or handling a moving user. FemtoStar takes advantage
|
||||
of a unique combination of cautious protocol design, low-level terminal-side
|
||||
mitigations, and the inherent properties of satellites to ensure that the
|
||||
location of terminals cannot be determined accurately.
|
||||
location of user terminals never needs to be, and in fact cannot be, determined accurately.
|
||||
</li>
|
||||
<li>
|
||||
<b>End-to-end encrypted</b> - While most modern communications systems
|
||||
encrypt traffic over the air, FemtoStar goes a step further. FemtoStar
|
||||
user traffic is end-to-end encrypted, meaning not even the satellite itself
|
||||
can decrypt it. What's more, connections are direct - from user, to satellite,
|
||||
to service. Unless you're connecting to a service we provide, our ground
|
||||
infrastructure never handles your data even in an encrypted form. This
|
||||
to service. If you're not connecting to a service we provide, our ground
|
||||
infrastructure never handles your data at all - encrypted or not. This
|
||||
also makes FemtoStar inherently net-neutral - after all, if we can't even
|
||||
decrypt your traffic, we can't selectively limit or throttle it either.
|
||||
</li>
|
||||
|
@ -56,11 +56,12 @@
|
|||
<b>Private payments</b> - An anonymous system isn't truly anonymous if
|
||||
users must still provide identifying information in order to pay for service.
|
||||
FemtoStar's payment system is simple, flexible, and above all, private.
|
||||
User terminals provide service tokens as they consume service. These tokens
|
||||
can be bought, stored, sold, used, or transferred freely by the user. They
|
||||
are not tied to any account or identity, they do not need to be purchased
|
||||
directly from FemtoStar, and they never expire. Service is priced by satellite
|
||||
resources consumed, not by time or data usage, so you won't be charged
|
||||
User terminals provide cryptographic Credit Tokens to the satellite as they consume service. These tokens
|
||||
can be bought, stored, used, or transferred freely by the user. They
|
||||
are not linked to any form of user identity, they do not need to be purchased
|
||||
directly from FemtoStar, and they never expire (when a satellite validates one,
|
||||
it doesn't even know when it was generated!). Service is priced by satellite
|
||||
resources (beam time) consumed, not by connection duration or data usage, so you won't be charged
|
||||
more for staying connected for longer or for connecting with a faster terminal.
|
||||
</li>
|
||||
</ul>
|
||||
|
|
Loading…
Reference in a new issue