►
From YouTube: orbit Chat - Q4 Roadmap
Description
This is the October 10th sprint chat for Orbit, talking mainly about Q4 Roadmaps. Take a look at https://github.com/ipfs/pm/issues/217.
A
Hello,
everyone,
this
is
the
weekly
call
for
an
orbit.
The
goal
today
is
to
figure
out
what
we
wanted
you
in
the
next
few
months
with
orbit.
If
you
open
the
etherpad
I'm
gonna
put
that
on
IRC-
oh
it's
already
there.
Thank
you.
So
let's
just
go
through
kind
of
what's
there
at
the
moment
and
see
what
that
means.
Basically,
my
wish
and
idea
for
the
next
quarter
is
to
make
orbit
usable
for
other
than
prototyping
purposes,
so
people
can
actually
use
it.
A
We
just
managed
to
get
orbit
to
a
state
where
is
completely
servantless
completely
distributed
completely
on
IPs,
and
that's
that
has
been
a
goal
for
for
that
project
for
about
a
year
now
and
so
we're.
Finally,
at
a
point
where
we
can
start
making
it
a
real
thing.
Okay,
so
all
the
issues
are
goals
that
I've
I've
listed
on
my
wish
list
is,
or
all
of
them
are
basically
work
towards
making
orbit
usable
for
a
small
team
which
is
the
first
goal.
A
This
is
an
overarching
goal
for
pretty
much
everything
and
we
yeah
that's
kind
of
like
the
mango.
What
that
entails
is
it
would
be
really
nice
to
have
a
place
where
people
can
download
orbit
and
start
using
it
right
right
now
you
have
to
do
a
lot
of
NPM,
poops
and
loops
and
install
seven
and
slow
and
things
who
might
be
broken
every
now
and
then
and
so
on.
A
What
would
be
much
better
is
that
you,
or
we
have
a
URL
where
you
can
download
a
build
that
is
already
compiled
and
includes
all
all
that
stuff
that
you
would
normally
do
with
the
re4
right
now.
So
that's
one
thing:
there
has
been
requests
for
making
a
simple
website
for
it,
so
that
we
can
put
the
actual,
build
links
to
it
and
kind
of
point
people
to
you
somewhere
where
they
can
start
digging
deeper
into
the
code
or
or
just
basically
downloaded,
and
then
on
orbit
side
itself.
A
A
A
A
Basically,
the
orbit
chat
protocol
in
itself
so
that
we
have
a
module
that
you
can
use
to
build
other
you
guys
so,
for
example,
detects
you
ID
that
the
terminal
UI
that
one
showed
earlier
or
the
different
kind
of
sub
BOTS
that
do
you
stuff
on
the
network
and
so
on
and
now
they're
all
together,
like
the
electron
version,
the
J's
I've
hit
this
version,
the
coracle
code
of
it
and
so
on.
That's
basically
why
they
need
to
be
separate
any
cool
and
then
recently
we
got
more
people
actually
interested
in
orbit.
A
So
thank
you
for
everyone
who
has
tested
orbit
in
the
last
few
weeks
and
reporting
issues.
It's
been
fantastic
to
see
how
it
breaks
everywhere,
but
one
of
the
key
things
is
Windows.
I
think
it's
time
to
give
some
love
to
the
window.
Studs
things
we
haven't
done
anything
to
make
it
work,
and
so
we're
basically
shooting
in
a
dark
here
at
the
moment
and
I
would
like
to
make
it
so
that
it
actually
works
for
Windows
users
as
well.
A
That
might
come
with
some
work
to
other
JavaScript
ecosystem
packages
and
mainly
go
wipe
FSG
pendency,
and
then
you
know,
maybe
we
get
some
work
to
go.
I
have
s
in
a
cell
from
this
I
don't
know,
but
like
heads
up
what
else,
then
I
would
like
to
add
more
testing
more
kind
of
fixing
little
annoyances
here
and
there
and
make
the
user
experience
really
smooth
in
a
way
that
you
don't
have
to
guess
whether
it's
working
or
not.
A
You
know
whether
you
can
connect
to
other
people
when
they
clearly
sit
next
to
you
and
you're
chatting
on
the
same
channel,
one
of
these
a
performance
related
to
the
data
transfer.
So
with
the
pumps
that
we're
now
sending
the
hashes
of
the
messages,
we
won't
send
the
actual
messages
over
reduce
already
one
round-trip
from
the
whole
thing
and
apparently
on
carrion,
when
we're
saying
that
it'll
be
a
lot
more
stable.
Also.
A
So
that's
kind
of
cool
I
really
wanted
to
you
that
namespacing
the
channels
right
now
all
the
channels
in
orbit
are
just
one
string,
basically
the
name
of
the
channel
and
they
get
translated
into
pop
sub
topics,
so
namespacing
them
in
a
nice
way
that
we
don't
clash
with
anything
and
there's
an
all
of
these.
Have
issues
open
on
on
github,
so
discussion
can
can
happen
on
individual
items.
There.
A
See
then
yeah
few
kind
of
small
but
important
ui/ux
improvements
like
adding
a
date
separator
cuz.
You
know
it
gets
confusing
if
you
come
back
online
and
you
see
the
message
you're
smart
yesterday,
but
you
only
see
the
timestamp
so
you're
like
these
are
old
or
new
messages
and
it
gets
kind
of
wibbly-wobbly
timey-wimey
orbit
an
IRC
I.
Don't
think
I
will
personally
have
time
to
work
on
this,
but
there's
been
few
people
in
the
community
that
have
expressed
interest.
A
So
basically,
the
idea
here
is
to
figure
out
a
way
how
orbit
can
be
used
together
with
RC,
not
as
a
as
a
bridge
as
as
you
would
normally
do
it
so
that
there's
a
server
somewhere
running
an
IRC,
client
and
and
handling
all
the
communication,
because
that
involves
setup
for
for
the
users.
I
would
like
to
find
a
much
better
solution
where
you
just
kind
of
lock,
launch
orbit
and
then
join,
say,
slash,
RC,
/,
IP
FS
and
you
get
on
the
actual
artists
each
channel
and
it
works
both
ways.
A
So
you
get
messages
from
IRC
and
you
can
post
messages
on
IRC
there's
few
difficult
things
there
like
identity
and
kind
of
yeah
identity
is
one
of
them
and
that
kind
of
boils
down
to
how
you
architecture
in,
but
I
would
be
really
really
happy
to
see
people
working
on
this
in
the
next
quarter
and
make
that
happen,
and
then
yeah,
basically
like
cache
emojis.
The
the
emoji
icons
is
one
of
the
examples
of
what
we
should
do.
A
These
are
kind
of
may
seem
small
and
they're
kind
of
chores,
but
at
the
same
time,
they're
all
related
to
the
user
experience
that
you
get
with
orbit.
So,
for
example,
if
you
have
orbit
right
now
the
the
application
and
you
started
it
when
you're
offline,
the
funds
are
not
displaying
the
emojis
that
are
not
displaying
because
they're
not
cached,
they're
they're
downloaded
from
urls
from
where
they
were
taken.
A
A
C
A
D
B
So
I
do
have
three
three
points:
I
want
to
talk
about
when
it
comes
towards.
First,
it's
the
the
overall
UX
like
not
about
the
fonts.
That
is
loading.
That's
like
how
I
used
to
actually
use
its
orbit
and
try
to
understand
how
we
can
make
it
I
mean
it's
it's
a
bit
confusing
with
the,
for
example,
that
we're
trying
I
think
and
it's
real
England
with
replying.
B
D
Think
you
better
if
I'm,
gay
or
anything,
you
think
it
would
be
pretty
useful
to
have
like
a
user
once
a
user
storyboarding
but
like
I,
feel
like
a
clear
look
into
all
these
different
types
of
design
decisions
for
the
user
experience
on
the
product
and
how
this
all
fit
together
and
other
potential
things
that
we
may
do
there
or
am
I
getting
that
right.
So
kind
of
like
product
design,
yeah.
B
B
D
What
returning
it
has
is
right
now,
all
of
that
product
design
is
happening
in
your
head,
family
and
other
people.
Don't
have
access
to
that
and
oftentimes
there's
other
things
that
people
are
noticing
are
potential
problems
that
you
may
not
be
noticeable
or
something
and
orbit
needs
to
get
to
the
point
where,
like
the
decisions
are
made
around,
you
know
something
like
we're
flying
or
something
like
you
know,
various
things
are
kind
of
like
documented
and
discussed
so
that
things
can
be
highlighted
or
shown
as
hey,
maybe
would
be.
D
A
D
I
think
I
think
this
just
means
so
there's
like
writing,
writing
about
one
feature
and
kind
of
like
describing
the
need
of
that
one
feature
and
so
on,
and
then
I
think
you
did
an
awesome
job.
That's
like--that's
that
make
sense,
I
think
maybe
I
may
or
may
not
be
understanding,
Victor
right,
but
I
think
what
is
desired
is
kind
of
like
a
product
design
perspective
at
it
of
like
here
all
the
potential
different
pieces.
Here's
like
the
user
flow.
Here's
like
you,
know
the
set
of
screens.
That
happens,
you
think
about
it.
D
A
E
Okay,
Matt
one
way
that
I
often
think
about
that
part
of
the
process
is
that
it's
about
narrative,
it's
about
building
up
stories.
More
than
just
like
that,
a
j'l
sense
of
stories
it's
about
building
a
narrative
about
who
is
using
the
application?
What
is
their
experience
and
that
might
be
storyboards,
it
might
be.
There
are
a
lot
of
different
ways.
You
can
collect
that
information,
but
it's
more
like
there's
a
thread
of
design
discussions
and
decisions
that
are
about
framing
that
narrative
and
it
sounds
like
your.
E
B
D
One
thing
that
I
would
love
to
kind
of
dive
down
and
do
so
there's
you
already
listed
a
lot
of
those
the
kind
of
hurdles
that
people
have
right
now
with
using
urban
and
so
like
making
your
website
for
it
downloading
it
and
so
on.
I
think
when
one
medicine
we
can
do,
those
can
be
super
useful,
similar
to
like
a
product.
Design
thing
is
to
do
kind
of
like
this
just
sit
down
and
and
and
go
through
all
the
different
pieces
together.
D
D
Okay,
so
far,
you've
been
doing
a
lot
of
heavy
lifting
on
that
and
we
haven't
been
we've
only
like
had
spurts
of
like
helping,
but
it
might
be
really
useful
to
sit
down
like
like
I've
dedicated,
like
look
I
kind
of
like
out
of
the
whole
thing
and
be
like
okay
from
user
hears,
the
word
orbits
and
gets
a
link
to
the
users
now
chatting.
Happily,
what
are
all
the
touch
points
and
what
are
all
the
pieces
that
we
could?
You
know
we
need
to
anyplace
yeah
we'd.
A
F
I
wanted
to
say
something
on
the
only
unit
experienced
quickly.
This
is
one
of
the
features
of
slack.
This
is
playing
the
one
thing
that
made
them
very
successful
is
how
much
and
how
well
they
did
user
experience.
How
well
and
things
like
that,
and
there
is
just
a
lot
we
can
learn
from
this.
Even
if
we
personally
don't
agree
with
choices,
slack
doesn't
make
the
general
sense
they
they
made
of
how
to
understand
their
users
is
very,
very
good
and
something
we
should
aim
for
with
for
bid.
E
Matt
you
had
something:
I
was
just
gonna
suggest
with
this.
The
discussion
before
freedo
commented
that
product
is
I
think
maybe
have
a
milestone
on
your
roadmap
for
some
sort
of
deliverable
from
those
conversations
having
happened
that
you'll,
whether
it's
a
design
document
or
whatever,
and
then
actually
put
it
on
your
roadmap,
so
that
people
see
where
it
where
it
is
yeah
that
sounds.
A
C
A
G
Working
that
needs
to
be
added
to
make
that
experience
really
really
good,
is
relay
so,
and
it
will
come
in
the
Jessica
first
chat
and
now
we
should
like
to
develop
Jessica
test
for
next
quarter.
And
now,
if
you
like,
set
our
priorities
but
like
essentially,
we
need
relay
to
be
present
on
go
ipfs,
so
that,
like
people,
can
I
close
JEP
first
in
the
browser
and
like
connect
to
the
rest
of
network
without
like
seeing
any
problems.
G
A
And
I
think
there's
a
quick
solution
for
that,
which
is
the
bots
we
can
make
the.
If
the
interrupts
works
with
Jace
and
and
go,
we
can
run
the
bots
who
are
kind
of
catching
the
channels.
So
then
you
at
least
have
something
there
that
can
in
a
pass
through
the
things
and
while
it's
not
a
deal
solution
at
least
that
would
get
us
started
while
we
kind
of
implement
the
relay
Stefan,
and
so
one.
G
D
One
part
where,
where
the
BOTS
come
in,
you
can
put
them
actually
out
once
in
scription
it
comes
in,
you
can
put
them
outside
of
encryption
and
they're,
really
just
relaying
these
ciphertexts,
and
so
they
actually
can
look.
And
so
not
all
bots
will
do
that
right.
So,
but
some
bots
can
be
just
bouncers
of
data
and
they
could
potentially
do
this
for
like
channels
that
are
new
right.
So
one
piece,
the
other
thing
I
was
going
to
mention-
is
am
I
getting
sorry
if
it
was
so
important,
Oh
Marcel.
G
Is
not
a
degraded
on
genocide
get
dressed,
but
we
have
we
peer-to-peer.
Fourth
sub
working
or
anything,
we've
do
I
pass
pops
up.
So
it's
just
a
matter
of
like
integrating
Gavin
also
has
been
working
a
lot
on
like
the
pub
sub
test
net
and
also
very
like
some
order
to
integrate
all
right.
Put
our
pub
sub
over
that
just
like
best
about
apologies,
make
sure
that
the
yeah
I'm
doing
these
likes
like
using
too
much
memory
or
am
I
dreaming
up
stuff
that
we
should
be
cleaning
but
yeah
there's
a
lot
of
work
there.
G
We
know
that
we
have
interrupts.
We
have
the
primitives
with
the
last
thing
I
was
working
on
on,
observe
was
really
when
we
eat
the
interface
discussion,
because
I
was
like
creating
a
different
interface
starting
from
the
lip.
It
appear
foot
self
and
then
the
interface
and
Jeremy
bill
forgot
because
was
different
and
yeah.
Now
we
know
we
know
which
universe
it
has
to
be
and
I
understand.
Why,
and
we
have
basically
to
my
get
interface
I've
been
on.
The
Jessa
is.
G
It
is
interface
that
we
wrote
the
notes
I'm
busy
I'm
more
specifically
talking
about
the
way
the
subscriptions
are
made
and
I'll
be
are
cancelled.
Remember
I
was
with
the
idea
that,
like
it
would
be
beneficial
to
have
and
for
me
to
start
a
subscription
and
I'm
gonna
not
to
cancel
it
and
and
they're
like
one
end
points
to
subscribe
to
the
feed
over
this
even
subscription,
but
apparently
it
is
better
for
the
developer
if
the
subscription
gets
cancelled
if
the
requests
on
that
subscription
gets
canceled
as
well.
A
G
G
So
it
is
better
like
if
you
draw
the
requests
just
like
to
draw
the
subscription
like
SharePoint,
and
we
can
make
that
state
up
and
because,
like
we
also
don't
want
to
requests
for
the
same
feed,
so
we
have
to
make
that
happen
on
just
because
API
and
which
will
be
the
same
thing
that
gets
offered
by
just
a
bit.
That's
alright!.
A
C
A
So
my
take
on
that
is
that,
first
of
all,
we
don't
want
to
track
users
in
a
way
that
it's
done
normally
in
these
kind
of
applications
there
so
like.
Basically,
that
means
no
Google,
Analytics
or
any
similar
component
in
any
part
of
the
the
code
bases.
However,
what
we
could
do
is
use
orbit
to
track
orbit
in
in
a
way
that
we
can
make
it
completely
anonymous.
A
No
IVs,
no
user
names,
just
knowing
that
there's
a
new
user
somewhere
joined
in
might
be
difficult
and
I
haven't
really
thought
the
whole
thing
through,
but
we
might
be
able
to
do
something.
If
not,
then
we
just
gotta
live
with
that
for
now,
I
I
personally
put
the
privacy
of
the
users
above
getting
metrics,
so
we
need
to
figure
out
some
kind
of
a
good
solution
here.
One
you.
D
A
Agreed
there
might
be
a
good
solution
for
this.
We
should
open
an
issue
in
orbit
and
discusses
last
point
before
we-
and
this
is
not
actually
ordered
related
but
or
wordid
DB
since
kicks
is
here,
I
wanted
to
point
out
that
he's
been
working
on
an
implementation
of
ipfs
log
in
go,
which
is
the
very
core
most
important
component
of
this
whole
stack
and
I.
A
Guess
the
idea
there
is
to
build
orbit
DB
and
maybe
eventually
orbit
in
itself
in
goal
completely
so
I,
don't
we
haven't
discussed
yet
about
the
details,
but
it
it's
there
and
maybe
after
this
quarter
we
already
have
a
much
better
idea.
What
what
that
will
end
up
being
kicks?
You
don't
have
to
talk
if
you
don't
want
to,
but
if
you
want
to
say
something
about
this,
that
would
be
fantastic.
H
A
D
A
I
mean
I've
been
trying
to
say
this.
This
is
why
I'm
so
happy
nowadays
cuz
we're
finally
there
so,
but
thank
you,
that's
awesome
to
to
hear
and
let's,
let's
as
a
demon
as
a
community,
let's
make
sure
that
we
really
make
it
a
cool
thing
for
for
everyone
to
use
and
finally
get
the
future
of
the
web
in
the
way
it
was
always
supposed
to
be
right
cool.