►
From YouTube: Status Core Dev Meeting #3 - September 3, 2018
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
C
D
A
Six
yeah,
of
course,
let's
just
move
alright.
So
let's
start
with
at
least
some
of
the
topics
that
people
want
to
talk
about,
so
they're
decouple.
We
speak
heat
and
Status
desktop,
and
then
there
was
one
more
thing
most
yeah.
Can
you
hear
me
yeah
so
that
one
and
then
we
can
do
desktop
and
then
we
can
go
into
info
updates
and
and
so
on.
Then
we
can
do
that
web
refresh.
At
the
end,
it's
my
plane.
Okay,.
A
Okay,
awesome,
yep
cool,
so,
first
of
all,
thanks
everyone
for
tuning
in,
for
the
third
quarter
of
meeting,
we
have
a
hack,
MD,
link
and
yeah.
Okay,
do
you
want
to
get
started
Andre
with
the
decouple
we
speak
II
from
wallet,
so
the
context
around
this
is
that
it's
a
dependency
for
the
hardware
like
product
launch
and
the
goal
is
to
discuss
progress
and
make
steps.
E
Yet
so
for
now
we
post
the
form,
because
we
we
started
working
on
the
Java,
cart
and
I
know
that
we
are
doing
a
lot
of
development
in
the
for
PFS,
so
I
think
we
can
maybe
pause
it
for
now
and
start
maybe
the
discussions
and
continue
the
discussion
and
then
start
the
development.
After
we
finish,
maybe
the
PFS
but
I
would
like
to
understand
if
it's
like
doable
I,
don't
know
exactly
how
long
it
would
take
like
to
finish
that
part
and
for
sure
we
need
it.
E
F
Can-
and
so
basically
probably
you
know
in
terms
of
timing,
we
got
our
mom's
still
to
finish
off,
so
we
can
follow
the
process,
the
process
and
discuss.
So
we
got
basically
like
build
stuff
into
each
other.
The
statistical
part
is
basically
implemented.
We
need
to
go
for
it
to
just
make
sure
that
you
make
it
safe
enough,
and
you
know
they
cut
some
corners.
F
Most
of
the
work
has
been
done
now.
What
we're
doing
I
probably
give
the
update
for
BFS
as
well,
which
is
basically
like
in
some
cases
there
might
be
that
the
Bandit
cannot
be
exchanged.
So
then
we
don't
we're
not
able
to
send
BFS
messages
and
so
we'll
find
no
UX
solution
today
and
there's
this
task
force.
So
now
we
sort
of
agreed
on
how
to
do
this.
You
know
essentially
we're
gonna
force,
the
user
to
sort
of
like
send
a
contact
request.
In
that
case,
this
baby
needs
it
just
needs
designs.
F
A
And
then
just
something
I
want
to
confirm
with
respect
to
decoupling,
who
we
speak
here
from
wallet,
it's
it's,
it's
not
a
blocker
in
terms
of
development
of
sort
of
the
general
or
the
general
integration,
it's
a
blocker
in
terms
of
actually
moving
to
production
for
the
hardware
light.
What
is
that
man
selling
correct
yeah.
E
It's
correct
for
development:
we
can.
We
can
continue
having
just
one
key
and
downloading
the
the
key
from
the
Java
card
to
the
client,
even
if
it's
the
same
but
then
yeah
when
we
when
we
want
to
use
it
in
production
and
shake
the
cards
and
everything
we
need
them
to
be
separated
so
for
the
development.
For
now
it's
fine.
We
just
need
to
be
sure
that
we
can
do
it
before
before
using
their
magic.
As
you
said,.
A
You
all
right
cool,
so
stutters
desktop.
The
context
is
that
we
are
planning
on
using
desktop
internally,
so
slack,
and
we
wanna
ideally
agree
on
what
features
we
must
have
working
in
order
to
not
have
a
detrimental
impact
on
team
performance.
The
goal
is
to
collect
with
a
list
of
features
that
can
implement
that
in
a
reasonable
amount
of
time
and
will
satisfy
nitrogen
of
the
use
cases
so
wittingly.
Do
you
want
to
take
away.
G
Yes,
so
yeah
briefly
yeah,
our
objective
is
to
use
status
desktop
internally,
instead
of
slack
and
well.
We
initially
had
a
set
of
goals
that
we've
defined
for
our
better
launch
or
like
high
priority
issues,
and
they
have
all
comprised
of
implementing
reliable
messaging
for
one-on-one,
chats
and
public
chats
and
very
little
functionality
outside
of
that
some
profile
management,
QR
codes
and
account
creation,
and
that's
it
but
obviously-
and
this
has
been
raised
both
internally
and
externally
by
other
teams.
G
We
need
to
be
clear
what
set
of
features
we
want
to
have
once
we
basically
greenlight
it
to
substitute
slack
for
status
desktop,
and
we
have
not.
Yet
we
thought
of
maybe
making
some
Bolly
questionnaire
and
also
using
some
smaller
groups
like
this
def
call
to
get
a
hand,
get
a
closer,
better
understanding
of
what
is
actually
needed
and
is
used
by
people
internally
at
status,
and
so
we
don't
have
yet
a
list
of
you
know
of
suggestions,
something
that
is,
you
know,
sandstone
or
anything.
G
There
have
been
just
some
items
floating
around
like
mansions
have
been
mentioned.
A
couple
of
times
obviously
should
be
stable
on
on
multiple
chats
during
prolonged
usage,
which
is
still
ongoing.
On
the
other
hand,
some
stuff,
like
app
reliability,
I'd,
say,
can
only
be
nailed
down
once
more
and
more
people
are
using
it.
So
it
would
a
good
helpful
for
the
product
as
well,
once
more
people
start
using
it,
but
yeah.
G
So
roughly,
we
just
want
to
collect
and
start
basically
peeking
around
and
gathering
input
from
folks
what
they
think
is
important
and
but
on
the
other
end,
on
the
other
hand,
we
have
to
stop
bicycle.
We
have
to
draw
a
line,
collect
features
up
until
certain
threshold,
because
we
want
actually
to
start
using
it
as
fast
as
possible.
H
Ever
a
question
vitally,
regarding
the
the
use
of
you
know
of
desktop
everyday
I.
Think
one
of
the
critical
issues
would
be
how
easy
it
is
to
update
you
know.
Ideally,
it
would
be
very
easy
to
update
every
day,
both
on
Linux
and
on
Mac
OS.
Is
there
a
way
to
that
is
plans
to
have
its
auto
update,
or
at
least
being
just
one
comment
line.
G
H
Because,
since
we
will
be
hydrating
really
quickly,
people
I
think
either
will
get
fed
up
of
going
through
an
extensive.
You
know
everyday
trying
to
play
to
fail
if
they
go
into.
If
they
see
any
broken
feature
or
something
you
know.
Ideally,
this
would
be
done
automatically
so
that
people
lose
as
little
time
as
possible
and
the
other
thing
that
I
see
is
the
URLs.
You
know
right
now,
they're,
not
clickable.
H
A
H
G
Hey
Patrick
just
to
comment
a
bit
on
some
of
things
like
we
haven't
yet
start
working
at
all
on
the
auto-update,
but
the
links
not
being
clickable.
This
has
been
in
the
works
for
a
while,
while
there
is
just
some
blocker
in
decor
around
desktop
library
that
prevents
us
from
clicking
basically
text
components
embedded
in
other
text
components
do
not
process
on
press,
therefore
clicks
are
not
working,
but
it
should
be
done
soon,
I
hope
and
the
changing
channels.
G
Thank
so
it's
been
also
partially
in
progress,
because
they've
been
multiple
improvements
to
the
underlying
scroll
new
component
functionality,
also
as
a
temporary
measure,
maybe
not
so
temporary
well,
so
thought
of
basically
implementing
some
kind
of
a
spinning
wheel
so
that
once
you,
you
know
change
to
a
long
and
intense
public
check.
You
don't
get
a
feeling
that
you
know
you've
clicked,
but
the
event
has
not
been
processed
so
super
to
improve
some
user
feedback
because
yeah,
it's
really
annoying
make.
I
Like
if
I
was
using
an
application
as
a
development
tool,
I
would
expect
a
few
features
that
are
not
necessarily
the
same
as
in
chat
like
a
secure
messenger.
It's
like
markdown
support
and
threads
and
stuff
like
this
that
make
open
source
collaboration
more
efficient,
so
I'm
a
little
bit
curious
like.
Where
do
we
draw
the
line
between
a
good
user
experience
for
developers
and
a
good
users
variance
for
people.
A
I
It's
something
that
makes
collaboration
about
code,
more
efficient,
right
and
yeah
sure
there's
the
argument
that
we're
going
to
be
using
status
because
we're
going
to
be
using
status.
But
that
means
that
we'll
be
communicating
less
efficiently
about
code
and
we're
developers.
So
are
we
so?
The
first
question
is:
are
we
optimizing
for
the
right
people
and
the
second
thing
is
like.
I
G
On
the
other
hand,
we
might
make
it
quite
usable
with
with
a
limited
set
of
features,
because
if
we
wait
until
we
have
all
of
those
additional
stuff
implemented,
then
it
might
take
a
long
time
and
we
just
want
to
optimize
the
return
of
investment
so
to
speak
so
yeah.
The
idea
is
to
make
a
compromise,
essentially
yeah.
We
have
to
make
a
compromise
with
what
fishes
will
not?
You
know,
impact
our
performance
too.
G
Much
maybe
make
a
vote
decide
if,
let's
say
if
from
90%
of
people
the
basics
that
will
work,
then
we
go
with
that
and
then
implement
those
additional
things.
Yeah.
Well,
so
sorry
for
talking
too
much.
But
that's
the
basic
idea
and
I've
made
a
note
about
the
markdown
I've
seen
you
suggesting
it
earlier,
and
the
people
optional,
I
think
and
that's
a
really
good
point,
but
I
think
we'll
just
make
a
democratic
vote
in
the
end
and
see
how
many
people
support
support,
which
features
and
then
go
on
based
from
that
something.
I
Yeah
the
point
about
Martin
wasn't
really
well,
it's
a
nice
feature
to
have
right,
but
it
was
more
to
illustrate
that
developers
don't
necessarily
crave
the
same
features
as
as
well
over
here,
an
unknown
user
group
right
but
like
a
simple
way
to
increase.
Adoption
would
probably
be
a
bridging
feature
bridge
so
I'd
say
right,
because
right
is
kind
of
our
hub
where
we
bridge
we
will
bridge
right
through
together
as
well
and
it's
like.
I
So
if
we
had
the
right
bridge,
it
would
be
an
easy
way
to
drive
up
chatter
in
the
channel
and
wouldn't
feel
so
wrong,
and
it
won't
be
easier
for
us
to
speak
to
the
larger
community
that
doesn't
use
skyress
yet
and
I
think
it's
unreasonable
to
expect
that
everybody
will
hop
on
like
everybody
that
we
want
to
talk
to
will
hop
on
start
us
desktop
just
like
that.
I.
A
Agree
with
that,
nothing
bridging
it's
definitely
a
good
point.
I
guess
one
way
of
looking
at
this
with
like
to
some
extent
like
this
markdown
and
Friends.
In
these
few
things
you
can
it's
almost
like
a
skin
right
like
we
could
imagine
that
if
our
application
protocol
is
so
general
enough
that
this
is
you,
you
could
have
different
ways
of
manifesting
a
UI
where
one
would
be
optimized
for
developers.
Someone
will
be
optimized
for
quick
chat.
For
example,
I,
don't
know
if
that's
that
it
will
be
an
interesting
new
acceleration.
G
What
features
that,
let's
say,
developers
make
heavy
use
of
are
not
available
right
now
on
status.
Due
to
the
limitations
of
this
underlying
protocol.
I
do
recall
that
a
couple
of
months
ago
someone
has
been
talking
about
like
things
like
reactions
that
they
might
be
difficult
to
implement
on
whisper,
but
I
might
be
confusing
things.
Maybe
there
is
something
else
also
like,
for
instance,
about
bridging.
How
do
we
make
it
properly?
G
Decentralized
I
were
going
to
use
reused,
mail
servers
or,
for
instance,
you
know,
split
that
us
will
split
it
up
across
status,
desktop
instances,
instances
in
a
decentralized
fashion.
Maybe
there
have
been
a
body
of
work
already
down
that,
for
instance,
I
have
no
idea
about.
Maybe
there
are
some
other
features
that
are
very
hard
to
implement
due
to
protocol
limitations,
and
this
would
mean
that
we
can
skip
them
for
now,
not.
A
I
I
I
A
A
D
You
know,
if
you
think
about,
and
the
reference
might
not
be
right
as
an
operating
system
as
opposed
to
like
this
brand
language
in
a
way
right,
it's
more
that
whatever
agnostic
or
anti
design
or
whatever
route
we
choose
visually,
it
still
will
become
a
strong
language
based
on
its
you
know,
consistency,
so
that's
kind
of
what
we're
thinking
along
those
lines.
If
we're
gonna
move
to
a
decentralized
platform,
for
example
with
Ghost,
what
are
these
elements
and
constraints
of
these
things?
D
And
how
can
we
start
to
build
one
language
together
which
bridges,
visual
design
and
development
or
engineering?
You
know
it's
like
almost
one
unified
language
that
we
would
all
use
together.
That
would
make
a
really
nice
statement
about
how
we
are
and
how
we
operate
internally.
They
could
also
differentiate
us
from
other
people
that
might
seemingly
to
look
like
us.
So
that's
kind
of
a
roundabout
idea.
Yeah.
B
So
there's
this
the
principles
in
design
that
we
start
as
a
hacker
m.d
document
they'll
also
be
an
ass
going
out
this
week,
where
we're
hoping
to
get
Chordettes
contribute
to
extensions
of
the
principles
that
are
more
product
specific,
which
we
can
use
for
the
web
refresh.
So
there's
a
link
document
in
the
hack
MD
as
well.
The
first
implementation
that
we've
done
with
ghost
is
the
hackathon
site
right
now,
so
this
was
based
on
on
meds
design
and
we've
done
that
in
fig
moats.
B
B
We
can
put
things
in
there
for
for
everybody,
brand-new
literally,
which
really
reduces
the
size
that
the
page
is
going
to
deliver
of
overall
scripts,
and
so
these
things
are
kind
of
important
in
terms
of
moving
back
here
to
the
document
about
how
it
is
that
we
can
do
swarm
and
ipfs
integration.
It
was
really
really
cool.
B
So
that's
where
we're
looking
for
engineering
input
and
and
integrating
ourselves
in
the
process
of
where
you
guys
have
been
already
for
the
for
the
last
year
that
about
nails
it
for
me.
I
mean
everything's
in
these
in
these
documents
that
you
can
that
you
can
follow
through
there's
a
lot
of
links
in
there
and
and
stuff,
and
you
guys
can
look
a
little
bit
deeper
into
where
it
is
so
we're
at.
D
A
Cool
to
the
people,
what
are
people's
general
thoughts
on
this
I
guess
also
expected
of
using
a
ghost
for
this,
and
if
people
have
any
of
concerns
or
thoughts
and
just
on
a
technical
level-
and
this
is
someone
who's
particularly
interested
in
in
your
joining
this
and
pushing
this
forward,
and
maybe
more
generally
like
what
specifically
do
you
need
in
terms
of
developers
for
actually
like
getting
the
initial
work
done.
I
think.
B
Right
now,
I
mean
for
the
initial
work
to
get
done.
What
we
want
to
do
is
just
basically
pour
all
of
us
all
of
our
front-facing
websites
over
for
the
for
the
mini
web
refresh
before
Def
Con
and
we've
got
that
pretty
well
handled
it's
more
of
a
future
music
sort
of
thing.
You
know
how
do
we,
how
do
we
actually
do
this
on
IP,
FS
and
swarm
and.
D
B
Do
we
potentially
then
integrate
it
into
the
into
the
application
as
an
app?
So
not
only
do
that
we
have
chat
and
browsing,
but
we
actually
have
the
first
blogging
platform
or
website
creation
platform
in
the
future.
I'd
really
like
to
see
that
that's
what
status
announces
at
some
point.
It's
like
here's,
your
here's,
your
decentralized!
B
J
J
B
Right,
so
what
security,
the
security
implement?
A
considerations
are,
how
are
we
gonna
actually
do
that
on
an
IP,
FS
or
swarm?
We
have.
We
know
how
we're
gonna
be
doing
that
in
the
legacy
system,
but
how
do
we
integrate
our
own
authentication
and
basically,
the
technologies
that
were
used
into
into
a
into
a
blogging
platform.
A
Yes,
I
was
I.
Think
that's
an
interesting
point
right
like
what
does
it
mean
to
be
an
author
here
in
this
system,
because
you
can
put
all
the
static
stuff
I
profess,
whatever
that's
fine
but
I,
wonder
if
there's
some
sort
of
overlap
here
with
identity
solution,
we're
working
on
and
also
sort
of
past
work
has
been
done:
around
decentralized
content,
discovery
and
the
discovery,
tab
and
so
on,
and
maybe
there's
something
there
where
we
can
use
like
a
basic
version
of
identity,
doesn't
have
authorship
and
then
structure
sort
of
their
content.
D
B
Way
I
understand
right
now
is
we're
probably
just
gonna,
be
interacting,
publishing
and
ghost
on
our
own
host
and
that
we're
just
gonna
be
mirroring
that
to
ipfs
as
soon
as
possible.
But
what
does
it
mean
to
actually
be
able
to
to
act
as
an
author
or
as
an
editor
on
ipfs
yeah
I
have
no
idea
about
that.
I'd
like
to
see
it,
though
so
yeah
identity
and
integration
with
with
where
you
guys
are
already
out,
would
be,
would
be
awesome.
Assistance
to
have
thinking
in
that
area.
A
So
the
way
I
see
just
a
blaze
that
you
have
a
status.
If
you
have
conquered
Everest,
that's
like
a
list
of
some
keys
right
and
then
they
they
have
some
space
where
they
can
post
things,
for
example.
And
then,
if
our
people
in
logic
community
post
things,
they
could
maybe
post
it
to
status
in
some
form,
and
then
you
would
have
this
sort
of
decentralized
discovery
thing
and
that's
sort
of
what
there
was
explore
to
work
on
this
a
while
back
when
it
comes
to
discover
as
I'm
surfacing
that
now
so
I
think.
B
I
B
I
I
Any
reason
why
we
shouldn't
no
real
improvement
like
running
our
own
life
if
a
server
doesn't
really
make
it
that
different.
Oh
it's
a
little
bit!
It's
nice!
It's
cool,
swarm
I
would
just
be
worried
that
they're
gonna
wipe
the
content
because
they
do
that
every
now
and
then
it's
a
little
quickly.
We
upload.
B
It
okay!
Well,
that's
just
that's
just
an
issue
of
the
system.
I
would
just
like
to
be
present
on
the
systems
to
the
degree
that
we
can
be.
You
know
just
being
on
the
front
edge
of
it
by
DEFCON.
It
would
just
be
you
know,
in
our
character,
to
be
saying
we're
pushing
the
boundaries
to
the
degree
that
we
can.
It
has
these
limitations,
okay,
but
we
do
our
best
effort
when
we
iterate
where's.
A
A
C
Are
just
saying
one
thing
to
consider
is
that
at
least
with
ipfs
I
mean
in
Fuhrer
offers
an
IP,
FS,
API
and
I
guess
for
now
they're
they
allow
you
to
pin
to
in
fewer
services.
So
it's
not
the
most
like
decentralized
approach
there,
but
you
don't
have
to
run
your
own
ipfs
know
you
could
pin
it
to
and
if
your.
B
A
B
I
mean
essentially
what
the
plan
is
is
just
to
take
all
of
our
current
content
out
out
of
the
existing
web
sites
and
put
them
into
individual
installs
ghost,
which
have
a
unified
theme
and
unified
navigation
across
all
of
the
sites.
Well,
and,
and
also
the
design
principles
that
Ned's
talking
about
what
she's
hoping
to
to
discuss
this
week
of
the
design
meetup
in
Berlin.
Is
that
we're
carrying
everything
down
just
for
a
real
minimal
sort
of
approach?
That's
very,
very
informational,
very,
very
lightweight.
B
So
it's
really
just
about
about
serving
updated
content
that
we
already
have
inside
of
from
ghost
essentially-
and
you
know
that
wouldn't
involve
documentation,
site
and
stuff
like
that.
Those
would
be
external
sites
with
external
links
but
to
the
degree
possible,
is
just
a
very,
very
pared
down
and
updated
content
of
our
existing
sites.
Whoever
is
going
to
participate
in
that
it
looks
like
that
would
be.
B
K
B
I
think
what
we're
talking
about
is
how
it
is:
how
do
we
serve
our
current,
an
updated
web
presence
delivered
via
ghost
on
both
swarm
and
ipfs
and
and
not
second
done
this
proof
of
concept.
So
I
was
asking
about
that
and
then
the
discussion
went
to
whether
we're
running
our
own,
our
own
nodes,
our
own
servers
or
not,
is
where
we're
at
in
the
discussion.
So.
K
So
just
some
take
on
that.
The
only
bark
like
we're
really
with
so
support
swarm
and
we're
really
interested
in
in
continuing
to
swarm
to
support
swarm.
They
show
that
there's
a
lot
of
breaking
changes.
Some
things
break
easily
or
the
Gateway
sometimes
doesn't
work
as
expected,
or
is
delayed
and
updated
in
being
updated
or
the
content
is
a
wipeout
once
in
a
while.
So
we
had
that
meeting
with
them
last
last
week.
K
K
I
I
B
B
I
L
C
It's
not
immediately
clear
how
to
do
it
with
the
housewarm
hashes
fit
into
the
multi
hashes
library,
which
basically
is
a
library
that
takes
your
hash
and
encodes
it
so
that
you
can
then
figure
out
what
standard
that
hash
belongs
to
it.
It's
not
it's
not
explicit
housewarm
could
could
take
advantage
of
that,
and-
and
so
you
can
actually
reference
the
swarm
hash
from
ens.
B
C
Just
gonna
say
to
y'all
six-point:
it's,
it
really
doesn't
seem
so
much
like
like
and
unless
you
want
to
have
two
versions
where
we
have
a
version
published
on
ipfs
an
aversion
published
on
swarm,
but
it
seems
like
with
all
the
things
that
we've
mentioned,
given
how
like
there's
a
significant
sort
of
tooling
and
and
support
for
ipfs
and
and
like
a
gateway
provider
like
in
Fuhrer,
which
implements
load,
balancing
and
all
kinds
of
infrastructure
to
make
it
to
make
sure
that
when
that
hash
is
published,
it's
the
content
will
will
be
pinned
on
the
network
and
also
be
able
to
scale
as
as
loads
increase,
but
also
with
the
work
that's
been
done
with
implementing
ipfs
and
ens.
C
It's
I
mean
it's
pretty
straightforward
to
do
it
with
ipfs
and
I.
Think
at
the
very
least,
there's,
maybe
more
clarity
needs
to
be
done
or
I
think
I
think
would
be
more
involved
to
get
it
done
with
swarm,
given
the
current
state
of
of
where
swarm
is
today.
I
could
be
wrong
about
this,
but
if
I
am
I
would
love
to
see
a
simple,
you
know
how
to
publish
adapt
with
the
NS
resolution
using
swarm
like
guide.
A
M
Yeah
I
am
listening
all
the
time.
Well,
the
main
focus
was,
as
probably
everyone
noticed
well.
The
word
Jenkins
changes
to
make
the
the
building
spiral
for
all
platforms
and
that's
pretty
much
done.
Okay,
I
think.
If
we
look
at
the
P
R
by
H
for
Jenkins,
it's
mostly
grayness,
so
I
think
we've
got
you
what
we
want.
M
There
are
still
some
improvements
to
be
done
for
release
builds,
so
we
don't
have
to
like
20
different
Jenkins
files
already
started,
removing
those
and
hopefully
it
by
the
end,
we're
just
gonna
have
one
or
maybe
two,
the
worst
and
groovy
files
that
we
will
reuse.
That's
definitely
an
improvement
and
other
than
that.
Yeah
of
the
other
questions.
We
now
have
a
small
storm
cluster
and
slowly
iterating
on
it.
So
it's
it's
more
stable
I.
Actually,
this
weekend
improved
it
by
adding
storage
limits,
because
by
default
just
uses
the
whole
disk
which
is
come.
M
But
that's
why
you
have
to
read.
You
read
the
manual
I
just
guess,
but
yeah
the
more
the
most
of
the
work
was
with
Jenkins.
Everything
else
is
kind
of
small
small
facial
around.
Don't
think
it's
worth
talking
about
I
guess.
One
thing
of
noting
is
that
we
now
have
Hong
Kong
fleet,
which
I
managed
to
get
working
with
for
elastic
ApS
after
some
fighting
with
the
terraform
module
for
Alibaba
cloud.
Although
I've
noticed
there
are
some
issues
with
connectivity
with
without
it
all
they
have
to
wait.
L
Yep
hello,
so
in
the
last
week's
we
were
pretty
much
merging
rendezvous,
piers
discovery
protocol,
and
this
is
already
running
on
staging
plate
and
it's
it's
working,
fine.
So
the
next
step
that
would
like
to
is
to
update
and
better
beat
up
need,
so
that
it
also
has
the
same
notes.
The
current
problem
is
that
bit
of
the
super
old,
it
runs
that
is
go
which
is
over
a
month
old
or
even
even
more,
but
here
right
now
we
hit
means
to
test
that
between
staging
and
beta.
L
So
we
will
do
that
next
things
that
we
started
looking
into
there
to
efforts
that
we'd
like
to
really
push
forward
as
soon
as
possible.
The
first
one
is
some
incentive,
ization
layer
for
whisper
and
mail
servers,
and
the
second
one
is
spam
protection.
This
is
probably
gonna
be
like
we
are
gonna,
try
to
figure
out
the
most
versatile,
but
also
the
easiest
solution
for
that.
For
now,
yeah
coop
looked
into
some
OS
level.
L
Oh,
it's
levels,
time
protection
that
we
can
do
like,
for
example,
IP,
right,
limiting
and
some
settings
on
the
OS
level
pretty
much,
but
our
goal
is
to
figure
out
something
more
on
whisper
level,
pretty
much
and
Dimitri
he's
working
on
that.
He
already
prepared
some
some
findings
about
about
IP
rate,
limiting
more
whisper
level
that
takes
into
consideration
the
trapping
the
bandwidth
that
you
are
happy
to
use
from
your
mobile
phone.
Just
I,
guess
that's
the
that's!
L
The
that's
gonna
be
the
huge
and
the
most
difficult
part
like
how
to
protect
your
small
smartphone
from
getting
too
much
traffic
because
infrastructure,
that's
that's
kind
of
covered
with
proof
of
work
and
building
mechanism
in
whisper.
But
regarding
the
are
there
gonna
be
more
tricky,
so
we're
probably
gonna
focus
on
that.
However,
it
is
still
not
decided
yet
we're
still
kind
of
in
the
face
where
we
are
we're
talking
slag
and
like
trying
different
ideas
to
figure
it
out.
What
you
would
like
to
and
I
would
like
to
project
so
yeah.
L
L
However,
it's
super
slow
and
you
need
to
have
you
need
to
be
lucky
to
actually
found
so
some
free,
alias
servers
in
that
dream
network
that
you
could
connect
to,
but
this
is
like
this
was
like
the
first
part,
like
the
first
kind
of
thing
that
we
did
to
unblock
the
swarm.
That's
gonna
integrate
alias
into
the
into
the
into
the
app
so
yeah
that
was
done
as
well.
Yeah
I.
D
J
Hello,
let's
see
last
two
weeks
have
been
relatively
busy,
but
it's
me
and
Jacob
went
and
discussed
I
guess,
the
previous
time
we
had
this
meeting
I
introduced
the
platform
threats
that
they
were
gonna,
try
and
look
at
and
look
at
to
basically
monitor
our
infrastructure.
Rina,
Jacob
and
Asik
had
a
kind
of
call
with
them
for
that
to
give
our
overall
what
they
could
offer
us
I
need
to
go
through
and
do
somewhat
of,
like
a
infrastructure
audit
to
see
how
much
of
our
infrastructure
that
we
have
cuz.
They
do.
One
of
your
terms.
J
J
All
of
that
as
kind
of
the
start
to
an
overall
risk
profile
of
the
entire
company
so
like
basically,
and
that
I
think
will
wind
up
becoming
some
type
of
public
blog
post.
So
people
won't
understand
how
keys
are
created
across
the
board
and
blockchain,
so
they
have
some
type
of
intuition
there
and
then
how
status
uses
those
keys
for
various
things-
and
this
is
gonna-
have
I,
guess
multiple
steps.
J
One
thing
how
things
are
currently
done,
how
things
will
be
done
in
the
near
future
as
we
as
we
break
away
the
whisper
key
from
the
from
the
account
key?
Because
right
now
it's
all
the
same
thing
and
then
how
the
hardware
takes
over
this
and
gives
you
a
better
I.
Guess
better
security
with
interacting
with
status,
and
then,
let's
see
well
I
have
here.
Oh
yeah
Oscar
came
up
with
the
idea
talking
with
me
about
a
company
and
pred
personal
security
week,
which
is
going
to
be
a
long
checklist
of
personal
procedures.
J
Things
to
do
things
that
look
at
when
auditing
yourself
with
regards
to
what
your
security
practices
are.
I've
made
a
discuss
topic
that
brings
up
this
idea.
Why
we
need
it
and
what
they
like
I
guess
the
bird's
eye
view
of
it
is
it's
like
a
we've
broken
up
into
multiple
sections
of
various
thing:
the
various
tasks
that
need
to
be
done,
starting
with
before
actually
doing
it,
buying
a
few
Hardware
things
like
some
like
a
UV
key
and
maybe
maybe
a
printer.
J
If
you
need
one
checking
your
hardware
to
make
sure
that
things
up-to-date,
so
maybe
we
can
start
working
on
getting
you
a
new
laptop
if
you're,
using
really
old
systems.
Things
like
that
I
would
appreciate
if
the
discuss
thread
got
some
more
eyes,
so
I
can
get
some
more
feedback
on
what
people
would
like
out
of
that.
So
I
can
structure
it
or
book.
Really-
and
that's
just
if
you
go
to
discuss
it's
called
kind
of
one
care
somewhere
soon.
J
J
A
A
J
Can
put
the
current
iteration
of
the
checklist
checklist
currently
doing
a
hack
and
B
document
I'll
post
that
the
discuss,
so
people
can
start
looking
at
that
to
see
what
we're
like
what
we're
looking
at
in
terms
of
like
because
it's
it's,
it's
built
off
of
the
my
crypto
blog,
which
I'll
also
link
about
just
like
security
for
for
dumb
people
and
smart
people's
they
basically
and
it's
it's
quite
comprehensive
and
I'd
be
and
I'd
be
curious
to
see
how
much
of
it
people
feel
isn't
necessary
or,
if
there's
anything,
that's
missing.
So.
J
I'm
waiting
on
so
this
this
next
week
at
the
security
and
conference
and
Berlin
I,
think
we're
gonna,
be
fleshing
out.
Some
I'm
gonna
be
trying
to
push
the
idea
of
this
to
a
lot
of
the
security
community.
There
see
if
we'd
come
up
with
I'm,
hoping
that
we
can
come
up
with
some
some
cool
ideas
around
this
like
how
to
infamous
stuff
inside
these
types
of
these
organizations.
If
we
can
all
come
to
agreement,
then
we
can
push
it
out
something
larger
than
what
then,
what
status
is
currently
as
opposed
like.
B
B
J
A
D
J
Think
yeah
I
think
that
that
that
meeting
up
in
Berlin
is
gonna
push
that
forward
quite
a
bit
like
the
telegram
Channel.
But
that's
a
part
of
in
there
is
this
seems
to
be
moving
around
the
lines,
like
that's
the
whole
point
of
that
entity.
Existing
is
developing
standards
across
the
entire
community
and
that's
I
would
like
to
do
it
that
way,
as
opposed
to
starting
something
and
then
doing
that
and
then
trying
to
make
everybody
change
what
we
did
before
head.
J
B
Buried
so
the
last
piece
that
we
need,
or
the
crypto
life
website
is,
is
your
interactive
contract
thing
together
with
Ned
the
pixel
drawer,
so
the
other
would
be.
We
can
definitely
launch
the
page
without
that
with
a
placeholder,
but
it
would
be
really
great
if
we
can
get
that
bat
moving
and
get
it
integrated
with
pushing
out
with
community
on
how
it
is
that
we
actually
do
that
stuff.
So
I'd
be
really
appreciating
it
on
that.
D
D
A
G
Finally,
implementation
of
mobile
warning
system,
warning,
certifications
and
more
work
being
done
on,
Jenkins
builds
and
clover,
script
testing
via
speck
integration,
and
also
some
minor
fixes,
like
fixing
SVG
blurriness
and
summer,
fixes
to
pop-up
menus.
We've
reused,
a
generic
react
native
popup
menu
component,
which
works
quite
fine,
but
there
are
still
some
on
press
handler
issues
that
precluded
from
being
used
properly,
which
we
would
like
to
do
because
many
features
and
Ewoks
depend
on
the
presence
of
a
context
menu.
So
yeah,
that's
the
roughly
over
update
for
now.
H
Yeah
I
guess
it's
mostly
been
around
the
PFS
implementation,
so
we
now
have
some
builds
that
people
can
use
to
test.
Pfs
I've
been
working
on
the
PFS
spec
and
so
there's
been
some
other
smaller
tasks
like
implementing
log
level
configuration
for
status
code
from
the
the
app
UI,
as
well
as
remembering
the
location
of
each
chat.
H
A
F
The
easiest
way
is
probably
just
to
do
pairwise
encryption,
and
so
there
were
kind
of
work
out
of
the
box,
so
essentially
like
send
one
message
for
each
participant,
so
that
requires
no
changes.
The
only
problem
is
that
it
is
fairly
expensive
because
you
would
have
to
calculate
POV
for
every
message.
You
know
basically
send
one
message
for
each
participant.
F
There
are
ways
to
do.
You
know
like
make
it
more
efficient,
because
already
whispered
provides
us
with
the
way
to
send
the
same
message
to
multiple
recipients
for
topics.
So
you
could
do
that,
so
you
know
like
if
we
were
to
do
it
today.
You
know
that
I
would
say.
2
pairs
and
encryption
first
see
you
know
and
start
by
pushing
into
our
version
that
caps,
the
limit
of
participant
to
say,
24
now
and
then
I'm
looking
to
using
a
share
topic,
and
at
that
point
it's
much
more
performant
I.
J
F
We
can
do
yeah
and
also
like
not
to
mention,
if
I,
that
the
chart
that
actually
they
the
chart,
the
management
protocol
needs
to
be
probably
revisited
a
bit.
So
that's
just
a
high-level
way.
You
know
like
at
the
user
moving
users.
Those
messages
need
to
be
revisited
a
bit
because
things
have
changed
since
they
were
first
implemented.
N
Hey,
yes,
sorry
so
mostly
we
focused
on
implemented
the
implementing
the
web
free
option
mechanism,
which
is
something
that
we
are
doing
with
the
metal
mask
a
team.
There's
been
a
lot
of
discussion
around
this
standard
and
and
a
lot
of
changes,
so
we
we
are
always
trying
to
catch
up
with
the
the
latest
VIP
details
that
are
frequently
updated,
but
it
looks
like
the
current
definition
should
be
the
last
one.
So
hopefully
we
should
settle
on
this
one.
N
But
yes
and
surely
the
idea
is
to
improve
the
privacy
of
the
browser
and
and
make
sure
we
don't
leak
as
a
browser
too
much
information
too
to
depth
themselves,
but
still
well.
You
don't
want
to
be
completely
blind
as
a
deaf
developer,
so
you
still
want
to
have
some
some
kind
of
clue
if
that,
as
reported
on
it,
so
it's
kind
of
a
trade-off
here
so
that
that's
why
there
were
some
updates
on
this
ap
but
yeah
as
I
said,
it
looks
like
the
current
incarnation
should
be
the
response.
N
N
I
kept
on
participant
two
extensions
and
eventually
start
considering
how
they
could
use
it
and
get
some
feedback
from
them
with
either
will
not
be
able
to
implement
anything
really
usable
or
useful,
with
the
current
state
of
extensions,
but
at
least
you
they
are
familiar
with
it.
It
would
be
a
great
way
to
to
just
initiate
some
discussion
and
get
some
interesting
feedback.
N
So
what
we
are
finishing
right
now
is
a
simple
chat
command
that
will
allow
to
send
some
nfg
so
like
cryptic
eg
as
an
extension,
so
it's
not
something
that
is
currently
implemented
in
statues
and
and
so
that
that's
the
world
points
to
have
it
implemented
as
an
extension.
So
you
can
just
get
this
extra
bit
of
functionality
in
statues,
but
then
remotely
in
a
decentralized
and
secure
way
through
extension.
N
A
A
M
Yeah
I
think
that
the
proper
way
to
start
this
before
we
get
people
from
motor
teams
to
join
in
the
effort
is
to
make
a
proof
of
concept
with
not
even
of
status.
Go
first,
but
a
very
simple
go
package
to
verify
that
we
can
have
any
useable,
build
system
that
will
work
with
Jenkins
and
a
way
to
have
to
test
that
interested
in
the
package
is
being
built
in
a
deterministic
way
and
kind
of
sort
of
I.
M
Guess
a
checklist
or
or
something
like
that,
of
what
kind
of
steps
we
have
to
go
to
to
do.
The
same
for
first
dates,
go
and
then
eventually
for
first
ladies
react,
which
is
which
is
much
bigger
with
your
challenge,
so
I
think
I'm
going
to
start
working
on
this
kind
of
proof
of
concepts
there
before
even
we
start
this
form,
because
this
form
at
least
for
me,
I,
don't
know
what
I'm
thinking
about
this
correctly.
M
M
Well,
yes,
of
course,
but
that's
as
I
said,
the
state
is
reacting
and
I
think
before
we
get
to
react,
which
is
the
hardest
part
of
this
all
start
of
something
simpler,
which
is
initially
just
a
example.
Go
package
because
I
want
to
start
afterwards
with
states
go
and
once
we
get,
we
have
that
working
and
it's
deterministic
and
have
an
idea
of
how
to
do
this
properly.
Then
we
can
start
with
state
track,
which
is
which
is
gonna,
be
a
real
challenge,
especially
with
platforms
like
Mac,
OS
and
iOS.
M
N
A
H
A
All
right
and
then
so
one
more
thing
there's
been
talk
about,
so
we
have
people
in
the
community
that
would
like
to
sort
of
be
on
a
call
and
and
maybe
ask
questions
or
they
want
to
contribute
to
certain
specific
things
and
so
on.
So
it's
a
one
idea
that
we
had
was
that
we
could
just
append
it
to
this
meeting
as
to
maybe
have
it
like
I,
don't
know
the
like,
like
half
an
hour
like
so
from
now
for
30
minute
or
something
like
this
I,
don't
know
what
the
people
think
of
that.
J
A
B
So
yeah,
there's
there's
you
know
this
is
advocacy
program,
that's
getting
worked
on
by
Sean
and
Hutch
and
then
there's
the
the
people,
ops,
things
that
are
going
on
about
how
it
is.
We
involve
people
more,
so
I
think
we
could
think
do
once
it
is
so
we've
got
it
settled
how
it
is
the
advocacy
program
is
gonna
get
launched,
and
how
are
we
going
to
be
doing
these
different
compensation
models
for
people
patting
it
on
would
probably
be
cool
I.
Just
don't
think
that
we're
quite
there
yet,
maybe-
and
maybe
in
maybe
the
month.
A
B
A
Alright,
wait,
we
can,
we
can
see
it
comes
out
of
it.
I
guess
not.
What's
the
nature
of
it
would
be
if
it's
specific
contributors
that
are
talking
about
things
that
we're
building
us
alone.
Maybe
what
make
sense
to
include
him
in
this
cold,
but
if
it's
more
of
a
I
want
to
build
direct,
it's
like
such
that
kind
of
thing
there
may
be
a
dedicated
call.
A
couple
third
thing
would
makes
more
sense:
I
did
I
guess
it
has
an
audience
right.
I
think.