►
From YouTube: Lisbon Hack Week // Aegir Browser - Hugo Dias
Description
Originally recorded during the Lisbon Hack Week from May 21-25, 2018.
A
I
moogle
I'm
work
in
moxie
and
I'm
working
on
ipfs
now
Giuseppe
a
face
so
basically
I'm
gonna
run
you
through
some
things,
I've
been
working
on
and
some
of
them
I've
managed
to
finish
so.
The
pull
request
is
up
Viktor
already
I
did
some
review.
So
basically,
what
I
want
to
wanted
to
improve
is
like
first,
the
Karma
tests
and
actually
the
browser
build.
So
basically
I
wanted
to
be
able
to
do
something
like
this
I.
A
Don't
know
if
you
can
see
so
I
started
with
this
issue
explaining
some
stuff
that
we
can
improve,
but
the
the
basic
stuff
was
improving,
karma
and
browser
builds
and
trying
to
follow
those
rules
up
top,
so
the
new
commands
would
be
able
would
run
the
original
CL
eyes
from
web
pack
and
whatever
bundle
we
need
and
also
from
karma.
So
we
can.
We
are
able
to
basically
redirect
anything
we
want
extra
to
the
original
CLI
and
that
basically
allow
us
to
do
stuff
like
that.
A
A
A
I'm
able
to
be
running
the
tests
on
two
browsers,
chrome
and
firefox.
Now
the
main
thing
is
actually
we
have
an
error,
so
that's
normal
right
and
we
need
to
be
able
to
just
click
and
it's
right
on
the
line
we
need
to
fix.
So
we
do
this
go
again
and
it
should
be
running
again
and
then
it's
done
so
this
was
the
main
objective
and
it's
done
it's
still
not
merge,
but
hopefully
victor
will
have
time
to
review
all
this
and
merge
and
it
will
for
the
time
being
be
behind
the
flag.
A
The
browser
bills
are
also
behind
a
flag,
but
that
should
be
easy
to
find
out
and
another
thing:
that's
in
the
in
the
process
of
doing
this,
I
managed
to
achieve
is
like
this
situation
right
now,
I
fork
the
ipfs
and
publish
a
package,
so
I
can
show
you
how
this
works
and
basically
right
now
with
unpacked
I.
Don't
know
if
you
know
it,
but
it's
like
a
CDF
connected
directly
to
NPM
and
with
this
API
FSHD,
it's
my
fork.
A
So
we
can
just
do
if
you
want
to
do
some
kind
of
projects
like
a
Dem
or
something
you
can
just
do
this
and
it
redirects
directly
to
the
browser.
Bundle
like
a
standalone
browser
bundle,
that's
as
everything,
and
so
basically
the
package
is.
This
I
did
the
same
for
GES
deliver,
so
we
can.
You
can
do
exactly
the
same
or
if
you
want
you
can
just
use
the
direct
link,
another
cool
thing
that
would
be
kind
of
helpful
for
some
demo
like
Diogo
presented.
A
A
They
open
this
stuff
if
they
change
anything
this
Forks
and
they
can
play
with
it
and
make
the
demos
make
whatever
you
want.
So
this
would
be
a
good
tool
to
like
port
our
examples
to
be
easy
to
enter
and
play
with
our
examples,
because
with
this
we
don't
even
need
to
clone
the
repo.
We
don't
nothing-
and
this
is
one
of
the
main
web
editors
that
people
are
using
right.
Now,
it's
pretty
complete
and
you
can
do
a
lot
of
stuff
like
linking
and
actually
running
tests
and
whatever.
A
So
it
could
be
a
good
entry
point
for
a
new
person
that
wants
to
understand
our,
why
PFS
works
and
other
ripples
that
we
that
we
have
and
it's
quite
easy
to
start
yeah.
So
this
is
one
one
other
example,
but
it's
basically
the
same
just
a
different
web
editor,
but
this
this
one
doesn't
allow
you
to
connect
directly
to
to
the
github
repo
and,
as
you
can
see,
this
goes
directly
to
this.
A
So
one
other
thing
I
wanted
to
show
you
is
so
basically
those
who
are
else
we
can
make
them
work
just
by
putting
this
stuff
here,
the
specific
path
to
unpackage
and
for
Jas
deliverer,
and
it
works
automatically
and
whether
one
other
thing
it's
like
the
bundles
or
the
butler's.
We
are
in
a
kind
of
weird
situation
right
now,
because
if
I
I
think
I
have
the
yeah
boy,
let
me
just
run.
A
If
you
want
to
build
something
we
like
BFS,
as
you
see
it's
like
two
megabytes
and
if
you
use
the
bundle
directly,
it
will
be
exactly
this
all
bundled
in
one
file.
So
this
is
not
not
the
the
the
most
optimized
thing
to
do
right,
because
a
lot
of
lot
of
stuff
that
we
use
like
a
sink
and
low
lash
and
other
stuff
you
actually
may
be
using
in
your
in
your
application,
in
your
bundle-
and
this
can
be
all
I
stood
by
web
pack
and
not
replicated
inside
your
your
dependency
bundles.
A
So
this
is
kind
of
strange
right
now,
because
most
examples
just
assume
we
have
a
bundle
like
I
show
you
on
the
others
example
and
other
examples.
They
use
a
standalone
bundle.
Everything
here
is
in
one
file
and
the
bundler
just
concatenates
that
file
in
the
other
stuff.
You
have
in
your
application,
but
actually
the
best
way
to
do
it.
A
So
the
thing
is
kind
of
its
kind
of
strange
out
how
to
set
up
this,
so
it's
easier
for
anyone
trying
to
use
ipfs
in
in
the
beginning,
because
what
you
we
need.
We
have
a
lot
of
keys
on
packages
that
we
can
use
it.
We
have
module
and
we
are
browser
when
we
have
main
and
all
this
stuff
bundlers
assume
and
use
it
according
to
some
rules.
But
to
to
be
easy.
We
need
to
have
some
good
defaults
here,
so
people
can
more
easily
use
and
on
their
on
their
application.
A
Right
now,
one
one
of
the
boiler
plates
that
people
use
it's
the
the
react
stuff.
So
basically,
either
we
tell
people
to
do
this
and
go
directly
to
the
to
the
bundle
and
it's
easy,
because
we
cannot
use
the
like
the
browser
key
on
packages
and
to
point
to
this
one.
If
we
could
use
it
would
be,
we
will
put
there
and
people
didn't
need
to
do
this
stuff
on
their
own
configuration.
A
But
still
you
still
still
have
some
work
to
do
to
optimize
our
our
own,
bundles,
so
big,
you
can
see
that
this
dependency
has
low
Bosch
entirely
there
and
all
our
last
packages
are
all
over
the
place
there.
We
have
a
couple
of
new
duplications
in
here
and
we
should
try
to
improve
this,
so
can
others
building
applications
on
top
of
this
can
also
benefit
from
it
and
I
have
smaller,
bundles
and
faster
applications.
A
A
One
more
thing
that
that's
actually
important
so
this
year
in
any
repo
right
now
as
you,
we
are
started
using
Bible
to
run
all
our
code
or
transpile
our
code.
We
can
just
add
browser
lists.
Hopefully
some
of
you
know
this
works.
You
define
your
the
browser
you
want
to
support
and
our
current
of
you
are
our
experimental
configuration
right
now.
We'll
know
about
this.
A
You
just
need
to
put
this
this
on
your
repo
on
your
package
JSON
or
browser
least
RC
file
or
whatever,
and
our
aja
CLI
will
pick
this
up,
and
when
you
do
the
bundle
it
will
follow
those
rules
and
only
support
and
polyfill.
Whatever
browser
browsers,
you
have
there,
so
you
can
have
different
configurations
like
for
the
Bell,
so
you
have,
you
can
run
your
tests
faster.
You
can
in
you
can
have
different
configurations
and
for
production.
A
When
someone
does
a
release,
it
will
use
the
bottom
configuration
and
you
can
put
this
anywhere
on
your
repos.
You
can
also
over
eyes
the
whole
Bible
configuration
putting
above
LRC
on
your
repos
and
also
where
Park
and
karma
configurations
can
be
customized.
We
using
the
Asian
file.
That's
most
people
already
have
so
everything
works
together.
It
can
be
customized,
it's
pretty
flexible.
So
that's
it.