►
From YouTube: 2019.07.18 Growth Call
Description
Call Agenda
--------------------------------------------------
https://github.com/bisq-network/growth/issues/150
Links Mentioned During this Call
--------------------------------------------------
👉 Proposal #93 - Implementation of protection tools: strengthening Account Age by requiring payments from 2 Bank Accounts
https://github.com/bisq-network/proposals/issues/93
Slack Link
--------------------------------------------------
https://bisq.network/slack-invite ➡️ join the #growth channel
About Bisq
--------------------------------------------------
👉 A Brief Introduction to Bisq
https://docs.bisq.network/intro.html
If we didn't get to your question on the call, feel free to join us on Slack (link above).
A
Hello,
everybody
welcome
to
this
week's
girth
call
for
bisk
for
the
week
of
July
18th.
My
name
is
Steve
Jane
hello
to
Chris
Tov
here
in
the
in
the
zoom
room
and
everybody
else
watching
online
or
on
YouTube.
We
had
these
growth
calls
every
week
at
this
time
to
discuss
how
the
disk
network
has
been
doing
and
to
discuss
current
priorities
for
the
project.
A
A
The
third
voting
cycle
just
ended
a
couple
of
days
ago
on
well
actually
yesterday
and
was
a
success,
we'll
talk
about
what
the
outcome
was
there
and
then
at
the
very
end,
we'll
talk
about
translating
bisque
to
Japanese.
If
anybody
has
any
thoughts
there,
we
saw
some
activity
in
the
Japanese
yen
market
a
couple
of
weeks
ago.
There
are
a
few
offers
pending
there
right
now
so
yeah
we
just
talked
about
the.
A
We
are
at
1059
the
Bitcoin
in
volume
for
the
month
so
far,
which
very
very
strong
we're,
probably
not
going
to
quite
hit
the
the
total
volume
for
that
we
had
in
June
in
July,
but
we've
already
passed,
total
volume
for
the
month
of
May
and
many
other
months.
It's
a
very
good
month.
So
far
we
have
a
daily
average
Bitcoin
volume
of
about
fifty
eight.
Fifty
nine
fifty
eight
point,
eight
Bitcoin,
which
is
also
very
high
on
75
average
trades
per
day.
All
very
strong
numbers
driven
by
Manero
for
the
most
part
and.
A
Let's
see
yeah
driven
mostly
by
Manero,
of
course,
fiat
trading
is
still
somewhat
constrained.
We'll
talk
about
that.
In
a
couple
of
minutes,
we
are
hopefully
close
to
releasing
those
constraints
with
the
new
accounts
signing
mechanism
that
will
be
releasing
most
probably
with
the
next.
Hopefully,
with
the
next
release.
A
B
B
On
the
one
hand,
side,
there
were
a
couple
of
bug
fixes
on
the
Tao
synchronization
issue,
so
that
should
be
a
better
now
or
hopefully
fixed.
A
couple
of
I
just
want
to
mention
a
couple
of
bucks
that
popped
up
that
were
fixed.
If
you
had
issues
with
editing
or
especially
small
offers
that
should
be
covered.
Also,
if
you
traded
C
with
C
per
instance,
you
probably
ran
into
an
issue
that
you
were
not
able
to
transfer
any
money
to
the
trading
peer
because
there
was
no
account
information
displayed.
B
It
was
bad.
There
was
fixed.
So
thanks
for
the
developer,
fixing
that
also
we
had
some
improvements
on
the
peer-to-peer
network
by
Florin.
We
are
now
kind
of
bundling
messages,
so
so
that
should
reduce
the
traffic
in
a
p2p
network
and
there,
let's
see
at
the
moment
it
doesn't
look
like
as
everything
crashed.
So
it's
it's
behaving
quite
fine
yeah,
let's
see
if
it
improves
the
network
over
when
when
lots
of
people
are
updating,
it
would
help
get
the
load
off
the
network.
B
Also,
what
we
introduced
is
a
small
cleanup
tool
for
safe
trades
that
failed
on
market
price
check.
So
if
you
had,
if
you
accepted
an
offer-
and
there
was
a
second
of
the
RMS
had
shown,
that
was
some
price
disagreement
and
then
you
probably
had
some
issues
in
the
client.
Now
we
publish
this
cleanup
tool.
So
actually
it's
just
a
special
version
of
the
piece
client
you
can
install
it
run
it.
It
will
display
a
short
information
dialog
that
it
cleaned
all
the
trades
and
it
shuts
down
immediately.
So
it's
it's.
B
You
can't
do
anything
wrong
after
you
have
overwritten
your
existing
pista'
cancellations.
This
client
just
install
verify
and
installed
the
told
the
current
version
again
and
yeah.
Hopefully,
all
the
problems
should
be
gone,
so
yeah
I
think
so
there
are
lots
of
other
smaller
back
fixes
and
improvements,
but
that
was
the
major
major
part
and,
as
you
already
mentioned,
we
are
heading
for
releasing
the
con
signing
with
an
ex-police
with
1.2.0
yeah.
A
Awesome
yeah,
so
I
guess
we
could
just
segue
right
into
the
account
protection
mechanisms
that
were
working
on.
As
you
mentioned,
it's
something
we
want
to
make
sure
we
get
right,
and
you
know
it's
probably
taken
longer
than
most
people
have
expected,
but
it's
really
for
the
for
the
good
of
a
network.
If
we
rushed
it
out,
then
people
are
very
strong
chance
that
people
will
just
get
hit
and
lose
money,
lose
trust,
and
it
just
would
not
be
a
good
situation.
So
we
want
to
make
sure
we
get
it
right.
A
The
proposal
that
we
are
working
on
implementing
right
now
is
proposal,
number
93
for
account,
signing
and
I
think
I'm
gonna
attempt
to
explain
it.
Let
me
know
if
I'm
missing
anything
but
basically
accounts
accounts.
Payment
accounts
that
were
created
before
March
1st
are
gonna,
be
signed
by
an
arbitrator
under
the
assumption
that
they
are
honest
and
they're.
Okay
accounts
after
payment
accounts
created
after
March
1st
are
going
to
be
they're.
A
That
acknowledgment
will
count
as
a
sign
signing
of
the
payment
account
and
after
30
days,
the
restrictions
on
trading
the
point:
oh
one,
Bitcoin
restriction
will
be
lifted
and
the
original
account
trading
size
rule
will
then
apply.
So
if
you
know
after
30
days,
you
can
trade
is
0.06
Bitcoin
after
60
days,
a
amount
and
so
on.
I
think
it
varies
by
payment
account
type
and
then,
after
60
days
from
that
date,
after
90
days
total.
A
That
user
can
then
sign
other
payment
accounts,
themself,
so
I
think
right
now,
if
I
have
it
right,
we
are
relying
mainly
on
delay
like
time
delay
after
a
successful
trade.
What
we're
looking
at
doing
after
that,
after
this
is
in
place
and
successful
in
working,
is
to
add
other
verification
methods
could
be
through
a
second
bank.
Account
could
be
through
other
verification
methods.
A
To
add,
you
know
to
act
as
additional
verification
methods,
in
addition
to
delay
time
delay.
So
that's
kind
of
and
I
guess.
We
have
Christoph
posted
some
mock-ups
earlier
over
the
past
couple
of
days
on
how
this
will
actually
look.
If
you
look
at
the
proposal,
it's
number
93
the
bottom
toward
the
bottom.
There's
a
little
bit
of
discussion
on
on
the
UI
user
experience,
the
dialog
boxes.
B
Maybe
just
a
quick
note
on
the
under
conditions:
we
might
go
even
stricter
than
we
thought.
Also.
You
mentioned
that
all
the
accounts
that
were
created
before
March
1st
will
be
signed.
So
there's
the
idea
to
make
it
as
we
don't
know.
If
the
accounts
before
March
1st
ever
was
trade
as
a
were
used
in
a
real
trade,
we
will
start
by
only
signing
accounts
where
there
was
a
dispute
and
the
buyer
received
the
Bitcoin
in
the
end.
B
So
if
the
buyer
received
a
bit
kind
of
dispute-
and
we
do
know
that
there
are
two
bank
accounts
involved
and
they
there
was
real
money
transferred
which
was
verified
by
the
arbitrator.
So
so,
if
we
even
limit
it
to
that,
then
we
have
we're
sure
that
we
only
sign
accounts
that
were
used
in
a
real
trade
and
there
was
no
charge
back
the
only
problem
we
might
run
into.
B
If
you
release
that
with
that
restriction
that
the
initial
number
of
people
who
got
our
accounts,
some
people
payment
accounts
that
got
signed
might
be
a
little
bit
low.
But
if
it's
too
low
and
it's
it's-
that
it
takes
so
long
to
to
spread
out,
then
we
might
I
have
to
think
about
loosen
up
this
condition
and
and
start
signing,
maybe
yeah
any
any
account
before
March
1st,
but
as
this
is
something
that
can
be
done
will
be
done
at
the
moment
by
the
arbitrator's.
We
don't
need
an
extra
release.
B
So
if
you
see
yeah,
we
just
have
don't
have
enough
accounts
to
to
kick
this
off
in
our
markets.
Then
we
can
dispute
special
versions
to
the
arbitrator's
and
they
they
can
reassign
sign
again,
all
the
other
accounts
as
well,
but
let's,
let's
start
just
small
first
and
then
spread
out.
So
it
sounds
a
little
bit
complicated.
Maybe
if
you
hear
it
for
the
first
time,
but
for
you
as
the
user,
it's
quite
easy.
B
You
don't
have
to
do
anything
special
to
sign
someone,
so
you
just
trade
as
usual
and
the
if
the
seller
clicks
on
payment
received,
he
will
automatically
sign
the
other
trading
peer.
So
so
we
try
to
make
to
create
an
network
as
a
trusted
network
of
accounts,
so
trusted
accounts
can
sign
other
accounts.
After
some
time,
they
could
also
trust
it
or,
depending
on
the
on
the
verification.
B
Yet
immediately,
yeah
and
so
over
time
should
have
a
really
broad,
secure
network
of
trusted
accounts
and
we
might
can
go
down
with
all
the
limits
and
secure
the
measurements
we
had
in
place
before
limits
and
so
on,
just
to
prevent
scammers
getting
into
the
platform.
So
if
that
works,
that
might
open
up
some
opportunities
to
to
make
bisque
more
easy
to
use,
because
we
don't
have
to
enforce
lots
of
limits
to
the
user,
but
let's
see
yeah.
Regarding
that
discussion,
that's
going
on
on
the
account
signing.
B
Maybe
a
couple
of
I
want
to
talk
about
a
couple
of
comments
that
were
raised
so
regarding
signing
options,
Steve
already
mentioned
the
first
step.
Is
you
just
trade
with
a
appear
that
is
a
kind
of
a
trusted
payment
account
and
can
sign
if,
if
your
account
gets
signed,
nothing
changed
at
the
moment
for
you,
after
30
days
at
this
initial
limit
of
0.01
bitcoins
is
lifted
and
yeah
you
can
trade
within
the
regular
limits
that
are
in
place
and
after
90
days
you
can
sign
other
accounts
as
well.
B
So
if
we
introduce,
let's
say
to
bank
account
a
verification
or
some
yeah
kind
of
verification
options,
then
we
can
think
about
if
you,
if
you
want
to
go
down
with
or
remove
this,
this
time
delay
completely
so
and
that
that's
up
to
us
or
if
we
have
kind
of
other
certificates
that
sign
payment
accounts
which
are
100%,
trust
or
yeah
quite
near
to
hundred
percent
trusted.
Then
we
might
also
can
just
remove
this
time
delay
completely
if
this
kind
of
signing
options
are
introduced
still
for
me
personally,
there's
still
the
same
state.
B
So
at
the
moment
correct
me.
If
I
am
wrong,
we
have
three
states,
so
we
have
two
state
make
or
four
states
unsigned
account
was
the
first
state
an
account
was
signed,
but
it's
still
with
has
still
a
limit.
This
initial
limit
of
0.01
bit
con,
then
we
have
account,
was
signed
and
limit
is
lifted
and
then
we
have
a
combo
signed
and
can
at
the
account
can
also
sign
accounts.
So
that's
that
there
are
the
states
that
we
have
the
system.
So
if
we
have
this,
two
bank
accounts
verification
and
we
say
yeah.
B
There
will
be
no
time
delay.
Then
there
will
then
the
account
that
the
state
account
was
signed,
but
syllabus
limit
will
be
kind
of
skipped
and
it
will
go
right
to
the
account
was
signed
and
limit
is
lifted
state
and
then,
of
course,
we
have
still
well
that's
up
to
this
for
for
discussion.
If
we
then
still
have
the
delay
until
an
account
can
sign
other
accounts
but
yeah
we
regarding
the
state
so
maximum.
We
have
this.
This
is
for
states,
but
yeah.
B
B
What
I
wanted
to
communicate
addition?
So
we
are
so
for
those
who
are
not
aware
there
might
be
another
column
in
the
North,
a
book
for
each
offer,
where
you
can
see
not
only
see
this
P
icon
so
which,
which
you
might
know
if
you
trade
on,
am
pissed.
But
there
is
another
column
where
it
says
time
since
signing.
So
if
you
haven't,
if
I
haven't
been
signed
and
yeah,
there's
nothing
there
to
display.
B
If
you
have
been
signed
two
days
ago,
then
it
will
say
yeah
two
days
and
what
I
wanted
to
bring
in
there
with
these
icons.
Is
this
information
that
if
the
account
was
signed
but
still
is
not
kind
of
trusted?
So
so
it's
still
within
the
limit.
So
so
we
need
this.
This
first
state
somehow
to
communicate
as
an
account
was
signed,
but
still
with
limit
with
the
second
state
account
was
signed
and
limit
is
lifted.
B
Today's
is
that
it
was
signed
and
you
can
sign
other
accounts.
Why
is
that
interesting
to
the
user,
this
state
account
was
signed.
I
can
sign.
Other
accounts
might
be
interesting
for
everyone
who
is
not
signed
yet
so
probably
account
owners
which,
with
payment
accounts
that
can
sign,
will
could
create
lots
of
small
trades,
0.01
Pitkin
trades,
with
a
kind
of
maybe
above
the
current
market
price
because
yeah,
it's
interesting
for
for
people
to
get
signed.
B
If
I
don't
have
any
display
that
there
is
the
contents
been
signed.
I
can
still
have
a
look
and
on
the
pier
info
on
the
account
h,
if
it's
a
really
old
account
or
if
I
see
okay
was
signed
two
days
ago,
the
account
age
is
maybe
10
days
ago.
Maybe
I
will
take
another
payment
as
a
another
offer
to
be
super
super
secure,
but
yeah
it's
up
to
the
user.
The
user
can
then
decide
what
what
kind
of
risks
do
they
want
to
take
but
yeah.
B
B
So
if
we
have
yeah
so
I'm
not
sure
how
this
can
communicate
it
best
with
with
an
IQ,
if,
if
you're,
watching
that
or
if
you're
in
a
call
right
now-
and
you
have
a
good
idea-
what
we
could
use
just
you
don't
have
to
make
artwork
just
just
write
a
comment
comment
in
the
in
the
proposal.
What
do
you
think
would
be
in
or
just
post
some
some
icons
you
found
in
the
web?
What
you
think
communicates
it's
in
a
good
way
and
yeah
we
need.
B
We
can
have
a
look
what's
what's
the
best
I
couldn't
communicate
the
states
and
I
think
they
should
work
for
other
payment
methods,
as
well
as
the
state
shouldn't
change
with
additional
verification
methods
that
might
be
just
less
states
because
I'm
some
verification
results
but
yeah,
but
that's
just
my
opinion.
So
far.
So
it's
it's
all
up
up
for
discussion,
yeah
and
and
the
last
so
that
I
guess
that's
a
long
discussion
and
the
last
message.
B
No,
that
last
comment
you
had
Steve
regarding
the
liability
message
at
the
moment:
I
just
added
a
small
information
on
the
payment
received
a
pop
up
that
you
know
that
as
a
seller,
you
not
only
kind
of
releasing
the
Bitcoin
but
you're
also
signing
they
are
appear.
What
was
the
idea?
Steve,
regardless
liability
messaged,
to
make
some
social
pressure
so
that
people
not
just
press
without
thinking?
Oh
I,.
A
Additionally,
it
just
seemed
to
me
that
there
might
be
a
concern
that
if
I
acknowledge
that
I
receive
the
payment,
that's
fine,
but
if
I
sign
the
account,
then
am
I
attesting
that
this
guy
is
innocent
and
honest
forever
and
if
so,
if
he
does
something
wrong
down,
the
line
am
I
gonna,
be
on
the
hook.
For
that
I.
Don't
know
if
that's
gonna
be
a
concern,
but
that's
something
that
I
think
people
might
like
might
ask
or
might
wonder
about
it.
Yeah.
B
So
some
ability,
if
there's
an
issue
but
yeah
if
your
trade
was
appear
as
Steve
said,
everything
went
fine.
There
was
no
charge
pick.
This
pure
starts
to
I,
don't
know,
try
to
trick
or
scam
people
yeah
of
course,
yeah.
We
there's
no
look
guilt
on
your
side.
The
two
scientists
this
at
a
payment
account
in
the
first
place,
so
we.
B
A
B
A
tree
yeah,
it's
a
tree.
What
we
are
in
in
discussion,
we
might,
we
surely
not
implement
it,
but
might
prepare
it
talking
with
sq.
Yet
yet
the
idea
of
that
an
account
can
get
signed
multiple
times.
It
makes
it
more
complicated
to
to
implement
it's
it's,
but
if
we
just
have
the
opportunity
format
structure
perspective
because
we
can't
change
so
much
stuff.
So
if
it's
out,
we
can't
change
anything
that
I
can't
in
the
witness
store.
B
But
if
we
kind
of
prepare
that
there
might
be
more
signatures
possible
for
one
account,
then
we
could
do
it
in
a
way
that
so,
if,
if
we
found
find
a
rotten
egg,
we
just
delete
invalidate
all
all
signatures
this
that
were
from
from
this
scan
account
and
still,
if,
if
the
other,
if
one
of
the
child
child
accounts
traded
with
another
peer
and
it's
an
honest,
I
can't
and
God's
a
God
also
signed
by,
let's
say
two
other
peers.
Then
it's
still
fine
just
lost
one
one
sign
that
one
signature
and
so
so
stead.
B
That
could
be
something
for
the
future.
If
you,
if
you
want
to
implement
some
kind
of
automatic
functionality,
that
just
wipes
out
all
signatures
downwards
from
from
an
untrusted
account
but
yeah,
we
try
to
be
prepared
for
that
to
implement
at
the
moment
it
will.
It
will
be
a
account
by
account
benning,
okay,
just
to
make
it
to
get
it
out
quicker.
A
B
So
that's
that
yeah,
just
just
in
general,
as
we
were
quite
so
I
personally,
was
quite
silent
on
this
feature
over
the
last
couple
of
weeks.
I
just
have
personal
time
constraints,
so
I
will
try
to
post
now
more
frequently
updates.
So,
if
you're
interested
I
want
to
give
feedback
on
this
story,
just
join
us
on
the
proposal
and
give
feedback
and
yeah
the
more
feedback
we
get,
the
better.
The
first
version
of
the
account
signing
will
be
yeah.
I.
Think
that's!
That's
that
other
points,
at
least
from
my
set
ahead.
B
A
If
I
guess,
since
we
looks
like
we
have
a
couple
of
people,
join
the
call
one
new
face:
garland
garland
welcome,
garland
Huy.
So
far,
we've
covered
the
market
update
and
the
release
that
we
had
on
Tuesday
and
we
just
got
finished
talking
about
the
protection
mechanisms
that
were
working
on
we're.
Still
we
have
the
two
items
left
are
devoting
the
outcome
of
the
latest
cycle
and
translations.
B
Not
for
my
side,
so
just
just
maybe
one
thing
we
also
are
in
discussion.
If
there's
a
way
to
to
do
this
without
arbitrators
at
all,
but
it's
kind
of
tricky
because
it's
it
will
always
run
into
if
you,
if
you
don't
have
this
trusted
starting
point
yeah,
then
we
have
an
untrusted
set
up
and
the
can
work
and
can
fail
depending
how
it
is
communicated,
for
example,
if
we
so
yeah,
maybe
one
thing
because
that's
different
than
it
is
right
now
right
now
we
applied
this.
B
The
room
to
release
this
feature,
the
account
signing,
will
only
be
in
mature
markets,
so
in
our
mature
markets,
where
we
do
have
enough
dispute
cases
to
to
kick
off.
This
account
signing
for
all
our
markets
that
are
kind
of
just
slowly
growing,
we're
thinking
about
removing
this
limit
completely
and
don't
have
any
account
signing
on
now,
because
yeah,
if
there's
no
liquidity,
there's
there's
really
small
chance
that
it's
interesting
for
scammers
anyway
anyways
and
we
can
start
signing
still
signing
accounts
in
the
background
based
on
dispute
cases.
B
B
A
B
A
Whoo
all
right
next
topic
devoting
cycle
number
three
ended
on
yesterday.
17Th
we
had
a
successful
round.
Let
me
get
the
numbers
we
had
21
proposals,
I
think
most
of
them
I
think
all
of
the
mix
up
for
for
work,
compensation
requests.
The
other
four
were
proposals
to
adjust
fees
to
raise
training
fees.
We
had
a
total
of
three
hundred
two
votes
on
on
those
twenty
one
proposals
issued
just
over
twenty
two
thousand
twenty
two
thousand
seven
hundred
and
thirty
bsq.
A
They
contribute
contributors
for
their
contributions
and
fees
were
raised.
So
I
think
the
market
for
bsq
started
out
pretty
strong
and
it
was
just
the
stakeholders
voted
to
increase
fees
to
start
bringing
the
the
balance
of
vsq
issued
and
vsq
burned
more
into
line,
and
this
was
the
first
first
step
toward
that
new
cycle
started
cycle
number
four
started
now
and
yeah
we'll
see
the
hope.
We
see
a
new
successful
cycle
over
the
next
three
or
four
weeks.
A
A
Yeah
definitely,
although
actually
I
have
to
ask
you,
do
we
want
to
have
someone
in
charge
of
the
repository
just
to
close
out
the
it's
true.
So
there's
that
and
there's
also
a
pull
request.
I
put
out
for
updating
the
issue
template
for
compensation
requests
because
I
think
there's
like
the
old
one
had
a
bsq
address,
but
we
don't
need
that
anymore,
so
I
removed
it,
but
it
just
needs
to
be
merged.
I,
don't
know
who's
in
charge
of
that
yeah
I
can.
B
Much
as
I
still
have
as
I'm
now
I
have
also
the
github
admin
right.
I
can
assign
someone
yeah.
So
if
someone
is
interested
I'm
running
this
compensation
maintain
a
role.
It's
it's
now,
not
so
much
a
high-risk
role
anymore,
because
yeah
older
voting,
all
the
critical
stuff
takes
place
in
the
in
the
client,
but
still
yeah.
It's
it's
it's
a
it's
an
important
role.
B
Yes,
yeah!
It's
not
only
you.
If
you're
a
compensation,
maintainer
I
could
could
theoretically
also
alter
existing
issues.
But
yeah
des
in
history
is
the
history
which
which
proves,
if
you
change
some
stuff,
so
it's
it's
yeah.
It's
a
one-time
thing.
You
might
someone
to
so
yeah.
We
can
put
up
some
peace
coupons
if
it's
necessary,
but
yeah
I
think
it's
it's
something
that
can
be
it
open
for
taking
to
be
taken.
Also,
maybe
one
thing
I
don't
know
if
it's
just
me,
which
might
be
interesting,
that
someone
is.
B
Position
repository
also
updates
the
calendar
when
voting
is
happening
or
when
the
what
reveal
phase
is
so
personal
together
to
get
this
notifications,
always
in
the
calendar,
if
it's
time
to
kind
of
start
the
bisque
client,
if
it's
not
running
to
do
the
waterwheel,
otherwise
you
have,
you
always
have
to
remember
it
yeah.
It
might
be
something
that's
worth
to
continue.
I
did
it
for
the
first
second
and
no
I,
don't
know
if
someone
else
took
over
or
if
it's
still
just
roughly
working,
because
it
did
it
repeatedly.
A
A
A
A
Of
course,
it'd
be
helpful
to
understand
what
is
going
on
like
how
this
process
actually
works.
But
if
you
just
watch
one
cycle
you'll,
probably
understand
very
quickly
what's
going
on
and
how
it
works.
So,
if
you're
looking
to
get
involved
with
bisque
in
a
somewhat
minor
or
I
guess
intuitive
role
to
start
out
with
this
could
be
a
good
thing
to
do
so.
I
guess
get
in
touch
and
slack
or
you
don't
to
call
like
this
and
we'll
help
you
get
started.
A
And
I
guess:
the
last
item
is
translations.
I
guess
two
items
here.
Actually
one
I
want
to
first
mention
that
big
thanks
to
Huey
4
for
the
translating
the
website
to
Portuguese.
That
was
a
really
great
big
step.
I
think
that's
gonna
set
the
set
the
stage
for
other
languages,
hopefully
many
other
languages
for
the
website
to
be
translated
into.
We
had
a
couple
of
issues.
A
I
think
there
might
be
a
slight
issue
with
caching,
that's
causing
some
of
the
images
to
to
not
show
in
the
selected
language
and
then
there's
an
issue
I
overlooked
of
the
responsiveness
of
the
actual
button
to
pick
the
language
does
not
show
on
on
mobile
and
on
desktops
of
a
certain
width,
I.
Think
of
close
to
the
break
point
of
like
9999
under
90
pixels,
the
the
menu
gets
a
little
wonky,
so
a
small
issue,
I
think
I
think
I
know
what
to
do
to
fix
it.
A
A
B
Not
nothing
from
my
side
yet
so
regarding
the
Japanese
translation,
just
also
to
put
it
in
perspective,
yeah.
Of
course,
every
translation
will
cost
money,
also
psq
in
the
end.
So
we
have
to
think
about
yeah
if
it's,
if
it's
worth
also,
if
Kenny
is
gues,
estimating,
might
be
as
a
translation
and
reviewing
might
be
in
the
range
of
1500
psq,
because
it
everything
gets
translated
and
there's,
of
course,
costs
cost
over
time.
When
we
add
new
features
and
translation
is
maintained,
so
we
yeah,
we
just
need.
B
If,
if
you're
in
Japan
are
super
fine
having
issues
or
just
English
clients,
or
if
it's,
if
it's
critical
for
the
option
to
have
it
translated,
I
think
modern
Japanese
is
left
to
right,
so
that
that
makes
it
easier,
at
least
from
a
UI
part,
as
we
have
some
some
issues
with
the
right
to
left
sis.
So
if
languages
are
written
right-to-left,
some
of
the
components
don't
render
perfectly
so
that
we
still
have
this
problem,
but
I
think
the
modern
Japanese
is
left
to
right.