►
From YouTube: Oct 13, 2022 - Ortelius Architecture Meeting
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
B
Link
to
the
doc
in
the
chat
so
welcome
everybody
to
October
13th
architecture.
Meeting
for
artelius
I
just
dropped
the
link
to
the
dock
in
the
chat
and
she
had
a
question
about
one
of
the
issues.
A
B
All
right,
let
me
get
over
there,
which
issue
number
was
it.
A
Yeah
you
can
open
like
five
to
five.
B
A
B
Yeah
so
one
of
the
things
that
Json,
when
we
look
at
the
output
from
the
s-bombs
is
they
have,
they
come
out
in
pretty
print
format,
so
they
got
a
lot
of
tabs
and
spaces
and
character
turns
and
all
that
extra
stuff
isn't
good
for
the
nft.
B
We
want
to
collapse
it
into
a
the
smallest
possible
Json
structure.
B
So
the
the
reason,
let
me
just
before
you
go
and
I
stop
sharing
the
reason
we
want
to
to
do
this
is
the
and
part
of
it
is
between
the
node.js
and
the
python.
B
A
B
Is
when
we
push
it
into
ipfs
into
nft
storage,
it
only
gets
stored
once
so.
All
the
storage
on
the
nft
storage
is
based
on
the
hash,
basically
of
the
the
content.
So
that's
where
we
want
to
have
this
consistent,
minified
version
of
this
Json,
so
we
don't
end
up
storing
the
same
thing
twice
so
with
that
I'm
going
to
stop
sharing
and
I'm
going
to
pass
it
over
to
you.
A
A
Is
my
screen?
Listen,
yeah,
okay,
actually
like
in
every
programming
language
right.
So
there
is
one
other
method.
That
is
this
one
that
using
which
method
we
can
Minify
this
Json
contract?
Okay,
so
to
demonstrate
that
I
have
created
a
jsoil
in
a
python
file.
Okay
and
my
sample
contract
is
the
same
that
you
have
shared
in
the
yeah
issue.
Okay,
this
one
is
the
sample
one,
and
this
one
is
the
sample
two.
So,
as
you
can
see,
the
indentation
is
messed
up.
Both
the
data
is
same.
B
A
A
B
A
B
A
B
Right
so
if
we
have
a
a
dictionary
you're
saying
so,
if
we
have
a
dictionary
object
that
contains
the
same
data
that
it
may
get
transformed
into
the
Json
string
differently,
is
that
am
I
understanding
that
correctly.
A
I
need
to
investigator
I
need
to
investigate
right
now.
This
is
the
JavaScript
object,
so
this
is
working
fine
with
Json
Dot
streamify.
B
Okay,
so
I
think
in
your
the
one
solution
around
that
would
be
to
take
the
take
the
dictionary
and
convert
the
dictionary
into
a
Json
object
and
then
convert
then
stringify
it
from
the
Json
object.
I
think
that
will
work
if
we
have
a
dictionary
object
that
we're
going
to
work
with.
A
Okay,
yeah,
that
makes
sense,
there
is
okay.
This
was
with
respect
to
this
JavaScript
yeah
quality
python,
so
I
did
the
similar
kind
of
thing,
but
here
there
is
something
called
Json
dot
load
and
json.com
json.com
right.
Okay,
so
when
we
say
json.load,
this
will
load
the
data
and
when
we
say
Json
dot
down,
this
will
give
us
the
output
right.
Okay.
Here
what
I
saw
here?
What
I
saw?
We
have
a
different
standard,
all
together,
they
are
giving.
A
A
Yes,
so
this
is
the
output
right
now,
so
we
can
write
a
method.
Okay,
we
can
write
a
method
and
truncate
this
space,
no
issues,
but
my
question
is:
do
we
want
to
like
move
ahead
with
the
standard
that
they
have
become.
B
What
we'll
need
to
do
is
from
one
side
or
the
other
from
the
what
I
mean
by
that
is
either
from
the
the
JavaScript
side
or
from
the
python
side.
We
need
to
adjust
the
data,
the
output,
so
both
of
them
match.
A
B
B
Now
I
think
in
the
in
this,
in
the
python
side,
in
the
Json
module
on
the
Json
dumps,
I
think
it
takes
a
bunch
of
parameters
that
we
may
be
able
to
pass
and
have
it
strip
the
extra
space
on
that.
A
B
Conversely,
on
the
the
node.js
side
on
the
stringify,
it
may
have
parameters
on
stringify.
B
Because
I
know
the
the
unclick,
the
library
here.
B
A
B
B
B
So,
in
the
the
key
separator,
one
of
the
key
separators
is
colon
space
and
if
we
change
the
that
says
there,
if
you
want
to
get
the
most
compact
rest,
you
change
that
Tuple
to
eliminate
the
white
space.
B
A
B
But
you
get
the
idea,
we
don't
have
to
go
to
go
to
the
details
now,
but
I
think
that
should
help
make
the
most
compact
version
that
will
match
up
with
the
Json
side.
A
B
B
A
Yes,
yeah
I
think
257
255
to
it.
B
It
may
not
be
there,
it's
close
to
two
five
eight,
but
not
a
hundred
percent,
we'll
create
a
new
issue
for
that,
just
to
make
sure.
A
A
B
What
we'll
need
to
do
is
we
should
probably
create
a
a
directory
in
this
repo.
We
could
do
it
against
this
repo
or
we
could
do
it
against
The
xrpl
Ledger
repo.
So
if
you
go
up
to
the
artillius
org
level,.
A
B
La
there
it
is
so
we
can.
We
may
want
to
put
your
coding
changes
as
in
a
directory
here
that
we
can
kind
of.
You
know,
put
the
example
in
there
and
then
we
could
do
the
pull
request
and
keep
track
of
the
the
Bounty
piece.
So
go
ahead
and
do
it
off
of
this
repo
and
I.
Maybe
we
just
call
it
Snippets
or
something
like
that.
B
And
then
make
make
under
that
you'll
have
a
a
JS
and
another
directory
for
python.
A
B
And
then
I'll,
let
let
Arvin
know
that
he
needs
to
do
a
PR
against
this
repo.
With
his
his
coding
example,.
A
B
B
And
then,
when
you
do
the
pr
you
can
cross
reference
the
issues
so
in
the
pr
at
the
very
top.
In
your
comment
part,
the
very,
very
first
box
that
you
fill
out
on
the
pr
you
can
say
resolves
and
then
you
do
artillius
artillius
pound,
like
5,
25
and
that'll
that'll.
Allow
you
to
cross-reference
the
issue
over
to
the
other
repository.
So
when
we
go
through
and
merge
this
approve
and
merge
this
PR
it'll
actually
go
through
and
close
it
in
the
other
repo
automatically.
For
you,
we
need.
A
B
Make
sure
that's
yeah
and
that
way
we
can
keep
track
of
the
the
bounties,
bounties
and
stuff
who's
getting
paid
for
what.
B
So,
let's
go
ahead
and,
like
you
said,
occurs,
go
ahead
and
get
the
directory
structure
and
the
the
pr
sorted
out
for
this
and
we'll
get
those
merged.
A
B
So
I
will
go
ahead
and
and
add
the
new
issue
so
we'll
have
the
The
Next
Step
will
be
taking
the
the
the
minimized
data,
pushing
it
and
pulling
it
into
nft
storage.
So
there'll
be
two
new
issues
coming
today:
one
for
python,
one
for
node
to
push
and
pull
from
nft
storage.
Now
ukrish,
when
you
did
the
the
proof
of
concept,
is
there
something
like
devnet
or
is
it
just?
Is
there
a
development,
nft
storage,
I
can't
remember.
B
Yeah
and
I
I
think
there's
a
corresponding
one
on
nft
storage
as
well,
because
we
don't
need
these
things
to
persist
forever.
You
know
we
just
need
them
for
testing,
so
I
will
look
into
that
when
I
create
those
two
issues
on
where
they
should
be
placed
which
which
NFP
storage
location
well.
B
So,
just
to
give
you
guys
kind
of
a
heads
up
where
we're
headed
with
this
so
go
ahead,
scroll
down
a
little
bit.
B
So
this
is
the
licenses
piece
you
can
see
right
there
in
the
middle.
The
bsd3
class
is
the
snippet
that
I
kind
of
pulled
out
for
you
to
play
with
some
sample
code.
B
B
We
may
be
able
to
collapse
that
into
smaller
data
because
they
have
the
algorithm
and
the
content
kind
of
broken
out.
We
can
kind
of
do
what
I'm
thinking
is.
We
could
kind
of
do
like
what
Docker
does
so
Docker
will
put
like
shop
256,
then
I
think
it's
an
at
sign
or
a
colon
and
then
the
than
the
the
hash
value
so
and
the
hashes.
We
could
collapse
this
a
little
more.
We
can
do
md5,
colon
and
then
the
nb55
line.
B
So
this
may
change
slightly,
but
that's
the
package
details
nft
and
then
you
see
the
license
nft
and
then
we
have
the
kind
of
like
the
composite
the
package
nft
here.
The
one
at
the
bottom
is
pulling
everything
back
together.
B
So
you'll
see
where
the
license
is
now
referencing,
the
ipfs
storage
for
the
license
nft
and
then
same
with
the
the
details.
The
details
is
going
to
be
the
nft
for
the
the
package
level.
So
what
we'll
be
able
to
do
so?
B
This
is
like
the
next
step
is
to
transform
the
data
in
the
s-bomb
data
into
representation
like
this
and
then
after
we
get
this
going,
then
what
the
next
step
will
be
is
to
take
a
a
full
s-bomb
break
it
into
the
smaller
pieces
and
place
the
missing
pieces
into
nft
storage
and
then
do
the
reverse.
Take
the
the
package
nft
that
we
have
here
and
expand
it
back
out
into
the
identical
s-bomb.
B
So
what
will
be
we're
kind
of
starting
with
the
s-bomb
first
and
we're
gonna
it's
more
of
the
the
bottom
layer
and
we'll
work
our
way
up
to
an
application
version
inside
of
ortelius.
So
an
application
version
contains
component
versions.
Component
versions
contains
these
s-bomb
these
package
versions
and
stuff.
So
that's
where
we're
headed
we're
just
going
to
take
it
in
in
smaller
steps
that
kind
of
makes
sense
where
how
this
is
all
kind
of
being
pulled
together.
B
Now
the
main
reason
why
we're
doing
this
is
like
on
the
license:
nft
there's
about
maybe
100
200
different
licenses
out
there,
and
we
only
want
to
storm
once
so,
instead
of
every
s-bomb
storing
the
license
and
this
s-bomb
that
we're
looking
at
here
is
just
for
one
component.
B
We
will
so
like
this
is
just
for
click.
If
we
have
one
for
like
Fast,
API
foreign
want
to
reference
that
the
same
nft
multiple
times,
instead
of
populating
the
ipfs
storage
with
duplication
at
that
level,
I
was
talking
to
what's
his
name,
I
want
to
say
Brian
from
Encore
no
Jason
from
Encore,
and
he
said
when
they
started
running
s-bombs
against
the
base.
Docker
images.
Within
two
weeks
they
had
three
three
Giga
data
on
s-bomb
data,
just
for
the
the
the
main
very
official
Docker
images.
B
So
what
they're
seeing?
Is
this
huge
growth
in
consumption
on
the
s-bomb
side?
Just
because
they
kept
on
repeating
the
data
that
they're
storing
over
and
over
and
over?
B
B
B
Yeah
we're
kind
of
optimizing
as
we
go
and
as
as
we
build
this
out,
so
you
just
think
of
think
of
it.
This
way,
so,
let's
say:
there's
a
hundred
thousand
programs
out
that
a
hundred
thousand
python
programs
that
use
click,
we
will
click
seven
one
two
that
we
would
only
have
out
of
the
hundred
thousand
programs
that
are
using
click
we'd
only
store
that
package
information
once
instead
of
storing
it
a
hundred
thousand
times.
B
So
go
ahead
and
go
back
up
any
questions
on
this
part.
B
A
B
A
Yeah,
so
there
is
one
suggestion
I
would
like
to
make
here
is:
let's
not
include
or
integrate
any
other
third
party
libraries
until
that
is
needed,
because
I
I
think
this.
This
can
be
coded
using
the
programming
language,
so
I
don't
see
a
need
of
any
third-party
libraries
to
be
used.
B
Right
right,
I
think
just
using
basic
JavaScript
and
the
python
libraries
without
getting
fancy
should
be
able
to
make
this
happen
pretty
quickly.
B
Right
exactly
because
what
ends
up
happening,
because
this
is
just
Json,
both
JavaScript
and
and
python-
transform
those
in
you
can
get
them
into
dictionaries
pretty
easily
and
then
from.
B
The
dictionary
level
you
can
transpose
it
and
you
know
kind
of
pick
it
apart
and
create
the
the
newer
dictionary
objects
and
then
that's
where
the
the
issues
that
you
and
Arvin
are
working
on
are
going
to
tie
in,
because
we'll
take
those
dictionary
objects
and
minimize
them
into
the
Minify
Json
format
that
we
can
then
push
into
the
storage.
A
B
Yeah,
so
this
one's
this
one's
gonna
be
a
fun
one.
The
there
is
from
spdx
there's
a
license
list.
So
if
you
click
on
that,
where
it
says
spdx
license
list
URL.
B
B
So
that's
that's
the
goal
of
what
we're
doing
here
now.
If
you
go
back
to
the
issue,
one
of
the
nice
things
that
they
do
is
they
give
us
a
Json
format,
which
is
that
second
link
there
yeah.
So
that's
the
Json
version
of
it.
So
we
could
actually
pull
that
in
and
just
basically
Loop
through
it
and
create
the
nfts
based
on
the
license.
Id
there.
A
B
Probably
I'd
hate
to
remove
any
of
the
data,
since
it's
not
that
much
yeah
that
and
things
may
change
over
time.
So,
let's,
let's
say
and
I,
think
what
they
mean
is:
let's
say
they
go
through
and
change.
The
is
OSI
approved
from
True
to
false
I
think
the
reference
number
would
go
to
like
215
or
something
even
though
everything
else
has
changed
so
I
think
the
reference
number
is
kind
of
like
a
versioning
number
for
them.
B
Yeah,
so
I
think
we
should
just
keep
it
all
and
again
this
this
one
here
will
need
to
go
through
the
minification
process
as
well.
B
And
what
will
this
one
will
kind
of
tie
into
the
when
I
create
the
new
issue
around
storing
or
retrieving
on
nft
storage,
it'll
kind
of
Link,
together
with
this
issue
as
well?
So
we
probably
want
to
do
the
I'll,
create
that
issue.
B
A
B
B
If
you,
if
you
guys,
want
to
work
on
it
like
co-code
together
just
put
into
the
top
part,
just
go
ahead
and
edit
the
comments
that
you're
gonna
split
at
50,
50
or
if
you're
gonna
split
it,
you
know
25.75.
However,
you
want
the
split
to
happen
or,
if
or
afford
to
go
to
one
person.
B
All
right
cool,
so
those
are
I'll,
create
a
couple
more
issues
today
and
get
them
out
there
and
also
remember
when
you
create
your
PR
for,
was
it
525
and
526
over
another
repo
tag
it
with
hacktoberfest
see
so
it
counts.
A
B
All
right,
cool
I
am
going
to
one
last
thing
is
I'm,
going
to
kind
of
do
like
a
a
stand-up
meeting.
I
go
look
at
I.
Think
this
time
pretty
much
every
day,
we'll
start
going
through
this.
So
I'll
start
it
next
week,
where
we'll
do
like
a
quick
stand
up.
So
we
know
where
everybody's
at
and
we
get
these
things
moved
along.
B
A
B
Yes,
the
daily
same
time
as
today,
unless
there's
like,
like
on
the
day
that
there's
a
an
Outreach
meeting
for
example,
or
a
general
meeting
we'll
just
skip
that
day
and
and
go
to
the
next
day.
B
All
right
well,
thank
you.
Everybody
get
those
those
pull
requests
in
before
the
end
of
the
week
and
we'll
get
those
merged,
and
we
could
keep
on
chugging
along
here.