►
Description
The EOSIO Coalition discusses a potential community RFP bidding application and goes over the new multi chain block explorer in detail.
00:00:00 Intro
00:00:03 Community application RFPs by Ted, Douglas
00:12:13 Secure Socials update by Brandon
00:13:36 Visual Identity discussion by Jeff, Brandon,
00:14:42 Explorer discussion by Jeff, Douglas, Ted, Jesse
00:38:45 Outro
Everything EOS is the official media channel of the EOS Network Foundation (ENF). The EOS Network Foundation coordinates financial and non-financial support to encourage the growth and development of the EOS Network. We’re harnessing the power of decentralization to chart a coordinated future for the EOS Network as a force for positive global change.
// EOS Network Foundation //
https://www.eosnetework.com
https://twitter.com/EosNFoundation
https://www.linkedin.com/company/eos-network-foundation
https://t.me/EOSNetworkFoundation
https://discord.gg/eos-network
info@eosnetwork.com
#EOS #EOSIO #ENF
A
Currently,
almost
everything
we're
working
on
with
the
coalition
in
the
top
20
list
is
something
that
requires
people
that
have
a
strong
eosi
osio
background.
So
what
I
would
call
choreo
sao
so
people
that
your
guild
team
has
some
obviously
wax.
Maybe
there's
a
few
engineers
and
telus
has
a
few
engineers,
but
it's
pretty
much
internal
and
it's
possible.
A
So
what
I
was
thinking
is,
we
could
look
at
making
a
list.
The
coalition
would
jointly
kind
of
build
another
list,
and
this
would
be
a
list
of
things
that
we
would
want
the
community
to
possibly
build
and
put
rfps
out
for
that,
and
then
let
the
community
actually
bid
on
them
to
come
back
and
say
yeah
we'd
like
to
build
this.
I
don't
have
great
ideas.
One
example
is
a
block
explorer,
which
I
know
telos
is
promoting
obe,
which
I
I
personally
am
in
favor
of
that
idea.
A
I'm
just
trying
to
give
you
examples
of
things.
You
know
portals
and
other
types
of
of
applications
that
we
might
want
in
the
ecosystem
that
we
might
be
willing
to
fund
through
an
rfp
to
get
it.
You
know,
get
it
developed
and
done
for
us,
but
something
the
community
actually
could
do,
which,
unlike
things
like
faster
finality
or
sink
calls,
the
community
can't
really
participate
in
that
there
are
very
few
people
in
the
community
with
that
skill
set.
So
it
was
a
concept
along
those
lines.
A
We
could
use
a
process
like
the
enf
grant
framework
to
put
those
out
and
have
people
bid
on
them,
so
it
would
be
much
lighter
weight
than
what
you
see
jeff
doing
today.
With
these
word
documents
and
the
rest,
we
would
you
know,
put
these
rfps
out
in
a
directory
we'd
promote
them,
you
know
from
the
the
new
organization,
account,
etc,
and
then
let
people
apply
and
we
could
put
them
in
a
repo
and
a
repo
in
the
new
organization.
A
A
So
since
I
mean,
according
to
eve,
since
I
mean
for
the
day,
I'll
vote,
yeah,
I'm
okay-
with
that,
the
question
is
all
I'm
just
trying
to
show
you
is
the
the
20
things
on
that
list
is
saturating
the
people
inside
the
coalition
and
we're
actually
stalling,
because
the
community
can't
do
it,
and
so,
if
we
really
wanted
to
involve
the
community,
we
could
come
up
with
a
secondary
list
that
we
really
intended
the
community
to
kind
of
work
on.
It's
a
concept:
if
it
goes
nowhere,
my
feelings
will
absolutely
not
be
hurt.
B
B
I
think
we
should
temper
that,
with
you
know
some
level
of
technical
understanding
recognizing
that
everyone
has
may
have
priorities,
but
but
they
may
not
have
the
you
know
the
same
technical
understanding
needed
to
make
make
some
of
those
decisions
right
I
mean
I
I
and
some
have
surprisingly
high
technical
understanding,
but
I
think
we
have
to
not
simply
put
it
totally
in
the
in
the
users
hands.
I
think
we
have
to.
We
have
to
weigh
in
yes,
but
we
would
write.
A
Those
are
my
thoughts.
We
would
write
an
rfp
that
says
technically
we're
looking
for
somebody
to
build
this
thing
and
we
would
describe
what
it
was
and
then
we
would
let
the
community
come
back
and
submit
bids
on
hey.
We
would
build
something
that
meets
all
the
specifications
for
this
amount
of
money.
Someone
else
would
say
we
we
built
that
it
would
meet
those
specifications
for
another
amount
and
again
it's
the
idea
is:
is
that
they're
a
different
set
than
the
list
of
22.
there?
A
It's
a
whole
new
set
that
we
would
jointly
come
up
with
and-
and
it
would
just
be
something
that
is
potentially
possible-
that
the
community
people
could
build.
You
know
people
that
know
smart
contracts,
people
that
do
that
know,
web
technologies
etc
could
come
back
and
say
yeah.
We
could
we'd
be
willing
to
bid
on
that.
The
issue
is,
I
haven't
seen
of
us
as
a
coalition,
with
a
large
backlog
of
these
types
of
ideas
like
gee.
I
wish
we
could
get
this
working
or
that
working.
It
was
just
an
idea.
A
We
have
a
a
process.
We
do
today
inside
the
enf
with
a
grant
framework
that
also
has
an
ability
to
to
do
rfps
and
have
people
bid
on
them,
so
the
I
could
handle
I
I
could
personally
handle
the
load
of
managing
that
process
of
you
know
reviewing
the
the
inbound
and
you
know
getting
helping
people
through
the
process.
A
It's
just.
It
was
just
mostly
an
idea
as
a
way
to
try
to
engage
the
community.
The
the
onus
that
would
fall
on
us
is
coming
up
with
this
list
of
things
that
we'd
like
developed
by
the
community,
that
you
know
that
we
could
put
rfps
out
for
because
my
whole
point
the
reason
this
came
up.
It
was
in
a
conversation
stephen
and
jeff.
Where
and
I
were
having,
we
realized.
A
We
go
through
this
big,
onerous
rfp
process
and
no
one
bids
on
them
like
we
know
when
we
build
it
like
faster
finality,
you
know
origen
and
gilmore
going.
They
were
going
to
do
it
and
ibc
they
were
going
to
do
it
and
we
knew
when
we
did
the
the
one
on
transaction
life
cycle
that
oci
was
going
to
do
it
and
we
kind
of
the
rfp
is
almost
kind
of
overhead.
A
I
mean
it,
it's
legitimate
we're
willing
to
let's
say
dan's
team
bid
on
them,
but
he's
shown
no
interest
right,
I
mean
dan's
team
would
be
a
person
that
could
have
legitimately
bid
on
fester
finality
or
something
like
that,
but
it
for
the
most
part.
There
are
very
few
teams
that
have
engineers
other
than
they're
sitting
in
this
coalition.
A
That
could
bid
on
any
of
these
things.
So
we
it
was
more
of
a
thought
of.
Should
we
move
up
the
stack
a
bit
if
there's
things
we
would
like
built
and
and
make
it
where
the
community
actually
has
a
chance
to
work.
On
that
I
mean-
maybe
not
maybe
they're.
Maybe
there's
no
pent
up
demand
for
that
by
us.
Yet.
B
Well,
I
would
say
we
probably
haven't
reached
it
yet
because
it
we're
new
and
there's
a
lot
to,
and
we
have
a
lot
to
work
on
and
you
know
we're
wisely
trying
to
get
through.
You
know
a
couple
big
gigantic
projects
launched
and
get
through
that
and
and
but
yes,
I
do
agree
that
there
will
be
pride,
there
will
be
things
that
are
probably
smaller
than
any
of
us
want
to
take
on,
or
you
know
we
could.
B
We
could
try
and
take
them
on
too,
but
we
could
be
things
that
that
you
know
rather
than
a
whole
chain
or
a
whole
large.
You
know
large
development
entity
taking
on
it
might
just
be
you
know
one
company,
one
developer
or
one
block
producer
or
whatever
say.
Oh,
you
know
what
we
kind
of
like
that
we
we're
doing
stuff
in
that
area.
Anyway,
we've
done
some
experiments
and-
and
we
can
we'd
like
to
get
paid
for
that
on
telos
and
also
on
wax.
B
So
we
have
on
telus.
We
have
telus
works
and
just
recently
added
to
telus,
which
is
sort
of
a
free-for-all
funding
system
which
works
great
actually,
but
we've
added
a
more
an
rfp
version
to
that
recently,
and
I
know
that
I
know
that
and
that's
based
on
telos
decide
and
it's
very
easy
to
vote
on
that
using
decide
voter.
B
I
know
that
wax
also
uses
you.
I
can't
remember
what
it's
called
right
now,
but
has
their
has
their
works.
Selection
system
also
based
on
telos,
decide,
and
you
know
and
like
there's
so
there's
a
there's,
a
technology
that
I
happen
to
know
pretty.
Well,
because
I
created
it
initially,
and
you
know
that
could
be
very
useful
and
I
think
it's
proving
useful
on
wax
and
we've
a
lot
of
the
tools
are
already
built.
If
we
want
that
to
be
some
kind
of
on-chain
thing.
B
If
we
want
it
to
be
or
or
it
could
be
a
poll
right,
but
if,
if
we
want
it
to
be
a
off-chain
process,
you
know-
maybe
maybe
we
do
want
that.
I
think
there
are
tools
available
that
we
should
look
at
and-
and
you
know
like
not
have
to
redesign-
you
know
reinvent
the
wheel,
but
I
do
think
we'll
get
to
that
point.
B
A
I
agree
with
you,
I
think,
we're
we
are
premature.
We
do
have
pretty
full
plates
and
we
have
a
couple
of
rfps
that
are
still
kind
of
in
flight
that
he
reminded
me
of
of
faster
finality
and
the
wallet
sdk.
So
yeah.
I
think
I
think
that's
great.
We
we
can
pull
that
back
up
and
revisit
it
as
as
we've
made
more
progress
or
is,
as
we
see
a
backlog
of
these
concepts
forming
and
we
realize
hey.
This
is
something
the
community
can
do.
Maybe
we'll
revisit
that
then.
B
Yeah
I'd
love
to
see
the
car
like,
I
don't
know
if
we
have
on
this
on
this
board.
If
we
have
a
a
column
for
stuff,
we
can't
do
now.
We
don't
know
exactly
when
we're
going
to
do,
but
we
also
don't
want
to
you
know
forget
about.
I
think
I
would.
I
would
definitely
put
want
to
see
that
idea
put
on
to
a
card
there
and
then
every
once
in
a
while.
A
B
A
C
D
D
Eos,
anyway,
it's
not
even
eosio,
so
I
think
we're
good
I'll,
just
kind
of
keep
working
on
this
with
with
the
other
folks
that
are
already
holding
the
assets.
There's
just
a
couple
that
maybe
we
need
to
add
and
think
about
when
the
gmail
and
the
google
account
is
set
up.
We
could
add
stuff
like
youtube,
and
things
like
that.
So
just
we
can
take
it
off
offline
or
off
the
agenda
board.
E
D
E
E
You
guys
see
my
screen
here,
so
this
is,
if
you
ignore
that
sidebar
there-
and
this
is
definitely
a
work
in
progress
but
just
to
get
get
the
point
across.
This
is
basically
our
explorer
that
we
have
that
we're
running
what
I
did
was.
I
took
everything
that
was
hard-coded
for
telos
out
and
made
it
like
totally
a
parameter
that
anybody
can
configure
and
we
talked
through
it
with
our
team
about.
E
You
know
the
best
ways
to
make
all
things
dynamic
here,
and
I
think
we
came
up
with
a
pretty
good
strategy
that
would
let
you
know
any
chain
contribute
to
their
implementation,
but
all
share
the
same
code.
So
this
is
just
one
repository
one
version
of
code.
That's
doing
this
and
what
we
did
do
is
we
have?
Can
you
pull
up
the
os
yeah?
So
when
you
there
you're
gonna
see
our
logo
still.
I
was
working
this
morning
on
the
logo.
It's.
E
E
E
Things
but
it
shows
who's
producing.
It
shows
your
block
height.
Your
price
chart
your
block
producers.
Here,
the
your
proposals,
everything
it's.
You
know
it's
eosio.
I
had
to
point
it
at
a
hyperion
which
they're
not
super
available,
but
it
worked
this
page
load.
It
didn't
work,
the
last
one.
So
it's
not.
This
is
us
sweden's,
but
you
know.
E
On
eos
right
and
I
did
I
had
a
jungle,
so
you
can
see
jungle
and
who's
producing
there
and
what
you
know
the
activity
is.
I
I
in
fact
for
us.
If
you
look
at
I
sort
of
that,
we'll
probably
put
a
separator
above
test
nuts,
you
can
see,
we
just
started
last
night
don
got
the
the
css
working.
So
you
know
he
just
made
our
test
that
gray
for
the
example,
but
you
know
we
can
change
colors,
I'm
working
right
now
on
getting
the
logo
to
be
dynamic.
E
B
B
E
I
know
even
like
the
the
map-
and
I
think,
there's
others
of
us-
that
kind
of
feel
like
the
map's
taking
up
too
much
real
estate,
so
that
in
in
fact,
what
in
in
that
context,
what
we
talked
about
in
the
longer
term,
that
a
user
could,
you
know,
have
a
menu
and
pick
what
homepage
they
want.
Because
some,
you
know
that
way:
a
user
preference
could
be
there
and
then
the
chain
can
set
with
their
default
home
pages
so
like
when
you
go
to
eos.
E
E
But
one
is
the
end
points
and
just
some
of
the
values
like
you
know
where
you,
where
you
go
to
eos,
has
the
eo
that
says:
eos
there
right
so
just
com
values,
then
the
second
big
thing
to
configure
is
like
the
the
style,
look
and
feel
so.
The
logos,
the
images
and
the
the
color
palette,
the
theme
could
all
be
configured
per
chain
and
then
the
third
big
thing
which
which
we
did
have
we
have
some
examples
of
how
we
would
do
it.
E
So
we
just
follow
that
pattern
as
the
code
to
to
do
certain
things
like
so
when
when,
when
it's
configured
for
eos
the
code,
you
know
you
ask
this
chain
configuration
class.
You
know
what
give
me
the
price
data
right
and
it
goes
and
gets
the
price
data,
because
right
now
for
telos
and
eos
we're
using
coingecko.
So
it's
the
same
code
that
reads
from
coingecko:
we
just
changed
telos
to
eos
and
it
works.
E
C
E
You
here,
your
block
rewards,
are
calculated
differently
than
ours
right,
so
these
numbers
here
need
to
be
using
a
different
function
than
they
do
for
telos.
So
there's
there's
different
things
that
we're
going
to
have
to
implement
differently
on
each
network
and
then
there's
and
then
there's
of
course,
a
baseball.
B
For
each
chain
can
have
their
like,
there
may
be
similar
blocks
right,
but
but
but
for
resources,
you're
gonna
need
power
up.
We
don't
use
power
up
for
voting,
you're
gonna,
you
know
we
can
put
in
different
voting
stats
and
wax
can
put
in
blacks,
can
put
in
their
voting
system,
and
you
know
everyone
can.
You
know
you
can
just
basically
either
modify
what's
there
or
create
your
own
and
just
use
that
only
for
your
chain
or
for
whatever
change
you
need
that
it's
very
modular
all
open.
E
So
as
as
each
of
us
kind
of
builds,
our
own
stuff
or
customizes
our
own
stuff,
we're
isolating
ourselves
from
the
other
networks,
so
we
don't
break
each
other
and
then,
of
course,
when
you
deploy
it,
you
know
you
can
deploy
it
without
the
sidebar
on
which
means
in
the
environment
variables
for
the
for
the
build.
You
have
to
say
what
chain
it
is,
so
you
know
we
would
still
run
if
you
go
to
like
explorer.telus.net.
E
We
just
configure
the
build
to
run
with
the
sidebar
off
and
be
pointed
at
telos,
and
then
it
runs
the
same
code
as
you
would
see
when
you
click
telos
on
this
one.
So,
like
my
thought,
is
that
this
this
particular
deployment
with
the
sidebar
goes
at.
Like
a
you
know,
eosio
coalitionscan.com
domain
for
all
of
us,
and-
and
you
know
you
could
in
fact
the
landing
page
could
be
some
branding
for
the
coalition
instead
of
a
specific
chain
and
then
the
sidebar.
E
E
We
could
run
a
version
with
the
sidebar
which
everybody
can
navigate
between
chains
and
see
stuff,
and
then
we
can
each
run
our
own
deployment,
that's
literally
the
same
code
without
the
sidebar
and
without
the
opportunity
to
switch
around
that's
kind
of
the
design
that
we
arrived
at,
so
that
you
know
we
we
could
all
share
one
code
base.
Not
have
you
know
if
all
chains
in
the
coalition
are
running
this
explorer,
they
don't
have
four
forks
and
they're
not
constantly
trying
to
you
know,
merge
changes
from
one
into
the
other.
E
E
It's
pretty
simple
to
add,
you
know
I
added
eos
and
jungle.
Four,
you
know,
you
just
add,
add
a
new
file
that
has
your
chain
information
in
the
endpoint
and
has
some
implementations.
And
you
know
there
you
go
it's
like
you
just
add
a
file,
and
then
you
register
it
down
here.
So
this
is
like
literally
adding
two
chains.
You
know
so
other
chains
can
make
a
pull
request
easily
to
add
themselves
and
it's
pretty
simple.
E
So
that's
that's
what
I
want
to
share,
so
we
we
want
to
pursue
that
and
have
more
calls
about
the
technical
details.
You
know
and
put
put
some
effort
into.
You
know
making
those
those
changes
that
we'd
need
to
make
so
that,
like
power-ups
there
and
block
block
pay
and
stuff
like
that
is
accurate
for
the
other
chains.
We
definitely
could
do
that.
In
fact,.
A
A
E
Yes,
absolutely
you,
if
you
look
here,
you
can
see
it.
That
was
that's
by
design.
So
when
you,
when
you
deploy
it,
you
set
the
environment,
variables
beautiful
and
these
these
environment.
You
can
kind
of
ignore
all
these.
These
are
the
old
ones.
Before
we
parameterized
everything
right,
so
you
say,
show
sidebar.
E
You
said
that
to
false
chain
name
to
eos
and
you
guys
would
be
able
to
do-
and
this
is
the
point
you
know
through
cloudflare
pages,
but
you
can
also
use
netlify,
but
just
you'd
have
your
own
deployment
right.
You
would
take
this.
You
would
just
deploy
the
other
good
thing
about
that,
and
this
was
actually
a
requirement.
I
kind
of
injected
is
that
I
don't
want
like
to
go
and
if
you
look
how
I
have
the
code
here
in
in
the
chains
config,
you
know,
so
you
have
these
chains
right.
E
E
E
D
E
A
E
Again,
we
need
another
point
that
I
would
make
is.
This
is
all
using
hyperion
and
that's
why
it
was
slow
for
for
you
guys
at
eos.
Eventually
you
know
the
nation
transfers
did
come
up,
but
actually
I
bet
that's
is
nation
transfers
yeah.
It
is
never
mind
the
you
know.
Another
thing
that
would
need
to
be
customized,
probably
is
you
guys,
would
want
to
adapt
the
api
to
another
history
endpoint
like
defuse
so.
D
E
These
are
all
things
to
consider
and
then
and
then,
once
we
get
a
little
bit
more
parody
and
get
it
deployed
like,
I
would
think
once
we
have
this
deployed
with
all
the
chains
having
things
working
properly
for
each
of
the
different
chains,
then
we
can
go
boom.
Let's
start
adding
new
features,
and
you
know,
then
we
all
get
the
new
features,
but
first
we'd
have
to
do
the
the
customizations
per
chain
like
defuse.
E
You
know,
for
you
guys
and
power
up
added
for
you
guys,
and
you
know
get
that
parody
there,
so
everything
we
have
now
works
properly,
where
it's
distinct
across
each
chain.
So
anyway,
that's
what
I
wanted
to
share,
because
eve
asked
me
like
how
what
would
it
take
for
you
guys
to
get
us
in
there.
I
was
like
well
the
hardest
biggest
lift.
E
Would
be
to
get
you
know
it
parameterized,
which
is
what
I've
done
and
then
we
would
have
the
outlet
to
go
build
the
customizations
per
chain,
which
is
not
totally
done
yet,
but
to
deploy
it.
You
know
it's,
it
deploys
real
easily
and
now
there's
just
a
matter
of
you
know
deciding
we
want
to
put
the
effort
into
that.
A
I
mean
it
could
literally
be
a
coalition
powered
hosting
and
just
drop-downs,
depending
on
the
v
host
you
came
in
on,
I
mean
the
branding
and
everything
based
on
the
v-host.
You
came
in
on
the
domain,
but
it's
all
really
just
one.
You
know
right
right,
instead
of
us
all
hosting
one.
We
just
agree
that
the
coalition
will
host
one
and
the
v
host
flips
it
to
the
right
logo
for
the
entry,
and
you
can
flip
chains.
If
you
want.
E
E
B
And
and
have
a
coalition
one,
and
it
becomes
a
very,
very
visible,
tangible
thing
along
the
lines
of
what
we
were
speaking
of
a
little
while
ago,
to
really
show
people
what's
happening
on
on
on
these
chains
and
are
working
together
and
how
that
gives
people
new
things
that
they
can
be
excited
about
right
now
in.
In
addition
to
all
the
things
that
they're
going
to
be
excited
about
in
6
and
12
and
18
months,.
E
Yeah
I
mean
I,
I
I'm
a
big
fan
of
of
net
levi
and
cloudflare,
and
I
mean
literally
it's.
This
is
free
to
host,
it's
hosted
with
cloudflare
on
their
cdn,
with
ddos
production
and
everything.
It's
a
static
front,
end
the
back
end
and
defuse
don't
get
me
wrong.
That's
that's!
That's
the
hard
lift
right,
the
apis
that
need
to
be
built
and
hosted
those
those
are
the
things
that
you
know.
Each
chain
probably
will
have
those.
But
this
you
come
in
here.
You
change.
E
C
E
We
each
host
different
versions,
because
what
what
you
also
then,
can
do
you'll
notice.
I
have
this
point
at
the
parameters
branch.
You
can
just
point
at
a
particular
tag,
particular
release.
So
that
way
you
know
each
chain
can
have
their
individual
deployment
kind
of
more
stable,
possibly
or
on
the
cutting
edge.
You
know-
maybe
you
know
jealous,
wants
to
run
the
latest
and
greatest
because
we're
changing
things
quickly,
so
giving
us
eternal
control.
It's
the
hosting
of
this
is
cheap
and
free.
So
pretty.
B
B
Ibc
features
could
potentially,
you
know,
be
built
in
there
and
as
we
as
we
do
more
together
and
as
we
build
more
cross-chain
features,
it's
I
think
the
unity
is
going
to
seem
really
much
more
important
to
our
users
and
it
sets
us
up
to
be
looked
at
as
a
as
a
an
ecosystem.
Right,
like
I
mean
we
are,
but
it's
the
perception
from
people
outside
is
that
oh,
this
is
an
ecosystem
like
cosmos
or
or
polka
dot,
as
opposed
to
these
are
a
series
of
chains
that
hold
similar.
B
E
And
the
one
thing
just
to
give
concept:
this
is
this
is
kind
of
where
the
inspiration
came
from,
because,
if
you
think
about
where
we're
going
as
a
coalition
and
a
multi-chain
ecosystem,
you
think
about
cosmos.
You
think
about
polka
dot
right
and
kirsten
is
the
one
that
said,
go
look
at
adam
scan
and
I
did
and
I'm
like.
E
Oh
wow,
you
know
they
have
that
many
chains,
you
know,
and
you
click
some
of
them
and
they're
like
there's
nothing
happening
or
like
some
of
these
things,
don't
work
for
some
of
them,
but
generally
you
click
around,
and
you
know
in
fact
the
left
you'll
see
the
left.
Nav
changes
a
little
bit.
The
color
does.
If
I
find
one.
Let's
see
this,
this
one
changes
the
color
on
the
left,
but
it's
pretty
much
similar
to
this
was
the
inspiration
for
it,
and
you
know.
E
E
On
here,
if
you
could,
how
do
you
click
here?
So
they
have
some
easy
way
to
add
your
own.
Oh
add
chain
right.
So
there's
like
an
easy
way
to
add
the
chain
like
if
you
add
another
launch
another
chain
right,
so
they're
really,
you
know
growing
their
network
of
networks
and
enabling
that
by
having
a
real
friendly
explorer,
which
is
exactly
what
we
want
with.
B
Exactly
what
we
want
to
convey
to
the
to
the
world,
I
think
imagine
imagine
for
a
second
that
our
coalition
has
a
sidebar
that
looks
like
this
right.
You
know
where
it's
eos
wax
telos
ux
and
then
it's
ultra
and
you
know
in
star
and
europe
chain
and
a
bunch
of
other
ones
that
you
know
maybe
are
very
special
use.
Then
you
suddenly
go
okay,
I
get
it.
This
is
this.
Is
this
is
extensible?
This
is
in
line
with
the
future
that
that
you
know
we
all
imagine.
E
B
D
E
Is
I
saw
this
in
my
head
like
last
week,
but
nobody
could
see
it
until
it
was
here
and
actually
I
this
sidebar
looks
a
lot
better
than
what
I
did,
because
I'm
not
a
I'm,
not
a
ui
guy
but
yeah.
You
know
you,
you
still
gotta,
imagine
some
logos
and
some
other
things
changing
here,
but
I
think
the
point
is
conveyed
so.
B
A
B
B
E
A
E
C
A
C
E
You
know
if
you
guys,
are
interested
and
have
somebody
that
knows
how
to
do
view.
You
know
they
could
get
started
right
away,
just
start
contributing
to
it.
That's
in
vue.js,
yeah
vue.js,
it's
quasar
quasar
is
like
a
component
library
for
view,
so
it
comes
with
all
that
got
it
pre-built
widgets.
That's
the
material
design,
google
css.