►
From YouTube: Using Telepresence for Kubernetes Development
Description
In this video Michael Hausenblas of Red Hat interviews Abhay Saxena from Datawire
A
Hi
there
today,
we
have
a
very
correctly
to
the
credit
to
pronounce
your
name:
I
Barry
yeah,
that's
right
from
Dana
White
and
we're
gonna
talk
about
something
really
cool
that
you
really
want
to
check
out
if
you
haven't
yet,
and
that
is
telepresence
a
true
that
every
greatest
developer
should
really
know
and
use.
So,
let's
start
with
the
bit
about
yourself.
So
about
your
background,
why
are
you
doing
you
know?
Why
are
you
helping
in
kubernetes
developers,
sure.
B
A
B
So
kubernetes
is
is
there's
a
lot
to
say
there.
Kubernetes
is
well
okay,
my
CTL
tries
to
likes
to
liken
it
to
a
helicopter.
It's
a
really
powerful
device.
It
can
do
a
lot,
but
it's
very,
very
complicated
and
until
you
get
the
hang
of
it,
it's
it's
very
dangerous.
In
a
sense,
I
mean
essentially
there's
a
lot
of
stuff
and
kubernetes
tries
to
do
a
lot
of
things
to
make
sure
kubernetes
tries
to
do
a
lot
of
things
to
make
it
so
that
your
workflow
is
smooth.
B
But
if
you
don't
understand,
what's
going
on
you'll
be
surprised
again
and
again:
oh
kubernetes
did
that.
I
didn't
understand
why
it
did
that
and
so
the
basically,
it
boils
down
to
understanding
what
kubernetes
does
and
then
you
have
a
great
deal
of
power
to
to
build
complicated
systems
and
not
have
to
think
about
all
the
details.
B
Once
you
once
you
have
reasonable
expectations
for
what's
going
to
happen,
then
you
can
work
with
those
and
kubernetes
becomes
an
incredible
accelerator
towards
keeping
things
running
and
getting
new
things
up
and
all
the
little
the
little
issues
that
crop
up
so
I
guess
as
a
developer.
We're
we're
in
the
in
the
modern
world
we're
being
tasked
with
having
our
service
online
and
making
sure
it
stays
online
right.
B
So
the
the
traditional
split
of
developers
writing
code
and
then
ops,
keeping
it
running
that's
sort
of
going
away
by
allowing
developers
to
have
the
agency
to
make
that
possible.
It's
not
just
about
dumping
responsibility
on
the
developer.
It's
also
about
giving
the
developer
agency
to
make
that
happen.
B
Most
of
the
time
you
care
about
deployments
and
making
sure
your
services
point
to
the
right
place
and
then
the
other
stuff
only
comes
up
when
you
have
to
do
nitty-gritty
details
or
you're
changing
the
shape
of
your
individual
services
in
some
way,
and
then
you
start
writing
templates
for
your
llamo
and
you
and
you
get
a
set
of
let's
say,
Ostra
box,
that
you
can
reuse
and
you
understand
what
they
do
in
kubernetes
for
you
and
it
all
becomes
very
smooth
and
quick
over
time.
I
mean
we're
building
tooling
around
this
stuff
too.
A
B
The
normal
process,
with
a
would
setting
up
a
new
deployment
or
new
service
in
kubernetes,
is
you
have
your
piece
of
code
and
you
need
to
put
it
into
a
a
docker
image.
You
bake
a
docker
image
for
for
this
piece
of
code
and
you
push
that
up
into
a
repository
so
that
the
kubernetes
can
then
pull
that
down
into
the
cluster.
B
And
then
you
need
to
update
your
llamo
files
associated
with
that
deployment,
so
that
kubernetes
knows
to
get
the
latest
version
and
then
kubernetes
goes
and
does
its
thing,
which
basically
means
bringing
up
the
new
version,
shutting
down
the
old
version.
If
the
new
version
comes
up,
if
it
doesn't
fall
down
and
this
whole
process
is
not
necessarily
slow
or
long,
but
there
is
definitely
a
process
there
and
and
if
you
start
out
doing
it
all
manually,
you
know
docker
build
edit,
your
mo
file,
coop
control,
apply,
etc.
B
It
can
take
a
while
and-
and
we
built
a
tool
called
Forge
that
automates
a
lot
of
that
so
that
you
can
I
mean
you
can
imagine
writing
a
script
that
does
these
commands.
The
Forge
is
sort
of
a
very
smart,
powerful
script
that
it
takes
care
of
writing
those
scripts
for
you
which
doesn't
try
to
you,
know,
take
over
your
process
or
whatever,
but
in
any
case,
so
Forge
is
a
way
to
to
speed
up
that
cycle,
but
the
ultimately
there
is
a
cycle
there.
B
There
is
some
amount
to
latency
between
you
make
your
code
change
and
you
have
it
running
in
the
cluster.
So
telepresence
lets
you
sidestep
all
of
that
with
telepresence.
As
soon
as
you
can
run
your
code
on
your
own
machine,
you
can
run
it
in
kubernetes.
It
is
literally
one
in
the
same
thing.
So
if
you're
writing
say
you're
writing
code
in
Kotlin,
and
you
have
your
ID
running,
which
I
guess
would
be
IntelliJ
right.
You
have
your
Kotlin
code
in
IntelliJ
and
you
hit
the
compile
key.
B
Sorry,
the
run
key,
and
now
your
code
is
running
with
telepresence.
You
can
make
that
be
in
the
cluster
right
away.
You
don't
have
to
deal
with
the
bake
cycle,
the
push
up
to
the
repository
and
then
pull
down
breweries
and
all
that
good
stuff.
If
you're,
using
a
language
like
Python
or
Ruby,
where
there's
not
even
a
compile
step,
for
example,
if
you're
writing
your
application
in
flask
or
in
Express,
you
can
literally
edit
your
code
and
the
running
application
will
update
itself
and
immediately
show
you
the
newest
results
with
telepresence.
B
A
B
Right
so
so
consider
your
your
organization
has
a
kubernetes
cluster
and
an
application
that
is
running
in
kubernetes
and
you're
writing
a
brand-new
service.
So
in
that
stage
one
of
writing
the
service.
All
you
really
care
about
is
being
able
to
run
your
code,
but
access
the
services
that
are
already
there.
Access
may
be
cloud
systems
like
Amazon,
RDS
or
Google
BigTable,
something
like
that
that
your
application
might
want
to
use,
and
so
telepresence
takes
care
of
that
for
you
by
effectively
putting
your
machine
in
the
chromatic
lustre
in
a
sort
of
out
bond
direction.
B
Now,
over
time
you
you
develop
your
service,
you
deploy
it
and
it's
running
and
you
find
a
bug
or
you
or
you
discover
that
you
need
to
add
a
new
feature,
but
now
that
your
service
is
out
there,
other
things
are
gonna,
be
accessing
you
as
well
right.
This
is
not
a
brand
new
service
anymore.
This
is
something
that's
in
production.
So
now
you
need
both
directions
of
telepresence
procs
proxying
feature.
B
So
when
you
run
telepresence
and
you
swap
that
deployment
out
and
it's
now
running
on
your
local
machine,
other
services
that
are
out
there
will
hit
this
hit
the
the
kubernetes
service
and
that
will
go
to
the
telepresence
pod
that
will
come
down
to
your
local
machine
so
effectively.
All
of
the
services
that
are
in
your
cluster
that
are
accessing
your
service
will
continue
to
do
so,
even
as
that
service
is
running
on
your
laptop.
So.
A
It's
really
a
first-class
citizen,
it
does
fqdn
DNS
works
as
normal
can
just
access
it
from
other
services.
You
as
a
developer,
don't
really
see
a
difference
and
at
some
point
in
time,
you're
going
to
switch
over
to
the
you
know.
Traditional
model
at
you
know,
building
the
the
image
or,
what's
your
recommendation?
What's
your
flow
there
well.
B
Well,
ultimately,
you
don't
want
to.
Ultimately
you
don't
want
to
keep
running
you
application
on
your
development
box
right.
So
once
your
once
you're
satisfied
that
things
appear
to
be
correct,
as
you
want
them,
you've
done
your
git
commit
and
your
push
and
so
forth.
You'll
you'll
do
your
Forge
deploy
or
whatever
your
your
deployment
system
is,
and
so
you'll
bake
that
dr.
image
you'll
put
it
into
the
repository.
You
now
have
this
immutable
blob.
B
That
represents
the
current
state
of
your
service
at
this
particular
version,
and
you
will
deploy
it
into
staging
and
then
ultimately
into
production,
and
it
will
run
in
kubernetes.
So
telepresence
is
not
there
to
be
part
of
your
production
system.
I
mean
sure.
If
you
have
this
crazy,
the
world
is
burning
situation.
Maybe
you
will
use
telepresence
to
get
into
production
and
and
do
some
some
very,
very
temporary,
short-term
nasty
things,
but
in
general
telepresence
is
there
to
help
you
as
a
developer,
build
your
system,
improve
your
your
service
debug.
A
It
so
in
a
sense
it's
the
proxying
is
the
new
ssh
into
the
production
server.
You
can
at
any
point
in
time,
access
it
and
do
crazy
things,
but
you
essentially
should
only
be
doing
it
for
development
and
maybe
troubleshooting,
but
not
really.
Once
you
are
satisfied,
you
kind
of
like
Bakley
image
and
then
really
deploy
and
so
I.
B
Think
it's
very
good.
Ok,
ok,
I
was
going
to
say
so
so
with
the
kubernetes
lets.
You
do
things
like
canary
deployments
and
things
like
that.
Splitting
traffic
between
multiple
versions,
especially
if
you
use
service,
mesh
tools
like
sto
or
envoy,
side,
cars
or
things
of
that
nature.
Let
you
do
some
advanced
routing
stuff,
where
you
could
set
things
up,
such
that
most
of
the
the
users
of
your
service
get
the
version
that's
running
in
kubernetes,
but
a
small
fraction
of
them
get
the
version.
That's
running
on
your
laptop
through
telepresence.
B
So
it's
it's
very
reasonable
to
try
to
take
a
running
system
and
debug
it
using
telepresence
by
stepping
through
the
your
code,
in
your
in
your
debugger
setting
breakpoints,
and
things
like
that.
As
long
as
you
understand
that
some
portion
of
your
traffic
is
going
to
be
very,
very
much
slowed
down
when
you
do
this,
because,
obviously,
when
you
stop
at
a
breakpoint,
you're
stopped
and
you're,
not
returning
an
answer.
What
but
I
mean
in
a
staging
system
or
with
the
right
type
of
redirection
setup?
B
For
example,
you
can
give
your
your
test
user,
a
special,
cookie
or
special
HTTP
header
and
set
up
your
routing
system
like
on
VoIP
and
do
this
to
only
send
to
the
the
test
version
of
a
particular
deployment.
If
you
have
that
header
set
something
along
those
lines,
so
you
can
carefully
control
what
traffic
you're,
debugging
and
and
then
use
telepresence
to
get
that
debugging
for
right
in
front
of
you
in
your
own
IDE.
B
A
What
I
was
about
to
say
or
ask
you
is:
is
it
fair
to
say
that
it's
kind
of
present
it's
not
only
useful
if
you
have
like
a
real
life
cluster
somewhere
the
cloud
or
on-premises
whatever,
but
even
if
you
run
you
know,
mili
cube
mini
shift
on
your
local
machine.
It's
still,
you
know
kind
of
shortcut
this.
You
know
building
image,
deploying
it
pulling
it.
So
you
you
still
benefit,
even
if
you
and
your
cluster
is
on
your
machine.
B
Absolutely
so
with
something
like
Mini,
Cooper
or
mini
shift.
You
have
the
option
to
docker
build
using
the
the
the
docker
that's
running
in
the
mini
coop,
so
you
can
avoid
the
one
step
you
can
avoid
pushing
out
to
the
repository
so
that
kubernetes
can
then
pull
it
down.
So
you
reduce
the
latency
a
little
bit,
but
that
said,
it's
still
far
more
interactive
I
mean
again
the
ability
to
be
able
to
literally
edit
your
code
and
hit
save
and
then
try
to
access
the
service
and
see
immediately.
A
A
About
like
we
had
a
couple
of
use
cases
now
and
I
think
everyone
gets
it
that
you
know
if
you're
serious
about
developing
on
oncologist
and
you
need.
You
know
to
the
questions,
to
really
be
very
agile
and
and
having
arrived
at
developing
velocity
there.
Can
you
talk
a
bit
about
like
limitations
or
like
stuff
that
people
should
be
aware
of
that?
You
know
many
expectations
pissed
at
they
know
we're
like
this
won't
work,
or
you
have
to
make
sure
that
second,
in
this
version
or
whatever
the
requirements.
B
Sure
well:
well,
let's
talk
about
how
telepresence
works,
because
that's
ultimately,
where
the
limitations
come
in,
telepresence
is
trying
to
do
something
that
isn't
natural
for
kubernetes,
right,
kubernetes,
typically,
controls
its
hardware,
its
nodes
and
and
controls
the
the
pods
or
the
the
various
the
sets
of
docker
containers
that
are
running
inside
it,
and
so
it's
it's
very
well
designed
for
that
purpose.
What
telepresence
does
is
deploy
a
pod
into
kubernetes
that
then
pretends
to
be
the
service
that
you're
running
on
your
own
machine.
So
some
of
some
aspects
of
this
worked
perfectly.
B
The
pod
that's
running
in
kubernetes
has
access
to
all
of
the
the
configuration
the
config
and
the
secrets,
the
the
environment
variables
in
the
file
system,
and
it
can
it
can
telepresence
can
copy
those
over
to
your
local
machine
without
any
trouble.
Other
aspects
of
things
are
a
little
more
complicated,
so
there
are
three
ways
that
telepresence
works
right
now.
B
If
your
code
naturally
runs
in
a
docker
container,
then
then
you
want
to
use
the
container
method
and
what
that
means,
as
telepresence
will
manipulate
your
docker
container
running
on
your
local
machine
to
set
up
its
networking
such
that
it
appears
to
be
running
inside
kubernetes,
but
I.
Think
the
more
common
case
is
that
your
code
is
running
directly
on.
A
B
Local
machine,
like
you're,
using
your
debugger
and
you
hit
the
Go
button
or
your
or
your
running,
your
Express
or
your
or
your
flask
service,
and
so
for
that
we
have
two
methods:
there's
inject
TCP,
which
uses
overriding
the
the
linked
libraries
that
go
with
your
executables
to
intercept
the
network
traffic
and
the
DNS
traffic,
and
then
there's
VPN,
the
proxy
VPN.
So
what
we're
trying
to
do?
There
is
set
up
a
a
VPN
like
system
where
all
network
traffic
is
captured
and
then
the
right
subset
of
it
is
sent
to
the
kubernetes
cluster.
B
So
in
either
case
we
have
limitations,
would
be
the
library
based
injection
of
code.
You
run
into
issues
where,
if
your
library
is
completely
statically
linked.
Sorry,
if
your
executable
is
completely
statically
linked,
for
example,
most
go
code,
then
you
cannot
inject
a
library
into
it,
because
it's
not
right
to
load
any
libraries
in
certain
commands,
especially
operating
system
commands
like
ping.
They
don't
follow
the
normal
path
of
of
network
connectivity,
so
those
those
things
won't
work,
but
I
mean,
if
you're
developing
application.
This
is
not
a
major
limitation
you
to
the
time
now.
B
B
That's
under
system
integrity
protection,
and
so
yes,
your
code
is
not
going
to
be
under
that.
But
if
you
happen
to
run
your
code
through
a
shell
script,
the
shell
is
protected
and
so
that
that
injection
gets
lost
and
by
the
time
we
start
executing
your
code.
The
injection
is
already
gone
so
again,
there's
ways
around
this
and
and
TelePresence
sort
of
tries
to
work
around
this.
B
B
Now
the
the
other
approach
is
the
VPN
approach
and
that
avoids
messing
around
with
your
binaries
and
instead
operates
at
the
the
system
level.
So
it
captures
all
the
traffic
on
your
laptop,
including
your
web
browser
and
so
forth
that
you
might
be
doing
other
stuff
with
now.
It's
selectively
only
forwards
the
packets
that
are
relevant
by
looking
at
their
destination
IP
addresses,
so
it
has
to
figure
out.
Kubernetes
is
over
here
in
this
space.
B
B
So
if
you
need
to
use
a
VPN
for
your
own
purposes,
you
can't
run
telepresence
in
this
mode
at
the
same
time,
and
similarly
because
the
proxying
is
all
one
piece
as
in
you're
replacing
one
deployment
in
the
cluster
with
your
own,
with
with
telepresence
you
can't
with
VPN
mode,
you
can't
run
telepresence
more
than
once.
Simultaneously,
you
can't
proxy
two
different
deployments
simultaneously,
whereas
with
the
other
mechanism
you
can
now,
this
is
something
I'm
working
towards
improving
in
the
future
right.
We.
A
B
A
Essentially,
wrapping
up
this
is
this
part
in
terms
of
languages,
all
the
languages
are
supported
and
for
some
languages
or
or
systems
like
essentially
go
statically
linked.
You
need
to
do
it.
Some
workarounds
apply
some
workarounds
or
Mac
OS,
which
has
certain
other
security
requirements,
but
but
they're
always
like
workarounds
that
make
it
possible
for
everyone
to
actually
better
another
person.
So
there's
there's
no
like
you
cannot
use
this
language
just
for
certain
languages.
A
You
need
to
use
some
work
on
substantially
or
write
certain
systems
and
one
thing
before
we
get
to
the
future
part
in
terms
of
since
we
are
in
security.
Quite
often
we
see
issues
with
you
know,
especially
since
we
have
Arabic
now
and
vanilla
is
six
other
see
any
issues
around
them.
You
know
people
with
with
using
our
bag
and
or
as
a
Linux.
So
you
know
any
kind
of
security,
related
access,
control
or
whatever
otherwise
settings.
B
Well,
you
you
bring
up
two
very
tough
topics,
actually,
so,
with
regards
to
SC
Linux,
we
we've
noticed
that
it's
definitely
possible
for
SELinux
to
to
basically
keep
telepresence
from
working
entirely
and
I'll.
Be
honest,
I've
largely
sidestepped.
That
issue
for
the
moment,
I'm
I'm,
testing
on
a
sort
of
default
or
install
and
on
a
default
ubuntu,
install
and
I
haven't
run
into
issues
there
specifically
and
I'm
I'm
looking
towards
users
getting
back
to
me
and
filing
bugs
or
whatever
the
case
may
be
when
they
run
into
issues.
B
So
I
can
address
them
one
at
a
time,
because
selinux
is
a
huge
topic
and
I
I
will
fully
admit.
I
do
not
have
my
brain
wrapped
around
that
just
yet
so
we'll
see
we'll
see
how
that
goes,
but
so
far,
at
least
with
the
the
standard
configurations,
it
hasn't
been
an
issue
with
the
role
based
access
control,
I
think
what
we've
seen
so
far
is
users
are
using
telepresence
with
their
their
staging
setups
or
with
their
mini
coops,
or
things
of
that
nature.
B
Smaller
sorry
non
production
clusters,
where
perhaps
we've
not
not
run
into
this
yet
so
there's
definitely
experiments
I,
have
in
mind.
I
want
to
see
what
happens
and
how
telepresence
can
fail.
I
think
the
thing
we
have
going
for
us
here
is
that,
as
long
as
the
developer
has
the
ability
to
deploy
the
the
service,
the
code
that
they
are
working
on,
they're
going
to
have
the
same
capability
to
deploy,
what
telepresence
does
telepresence
is
not
messing
around
with
the
cluster
as
a
whole.
B
A
So
I
you
know,
I
did
not
intend
to
put
you
on
the
spot
here.
It's
really
Chester
really
this
expectation
management
that
people
know
you
know
if
if
they
would
need
to
disable
I
see,
then
that's
fair
or
if
they,
you
know
all
be
careful.
You
need
to
have
these
these
elevated
permissions.
For,
for
you
know
our
work,
settings
or
whatever
I
think
you
know,
since
there
is,
let's
be
honest,
there
is
no
alternative
to
telepresence.
B
So
far,
I
haven't
run
into
it
and
I
look
forward
to
having
specific
use
cases
that
need
solving
that
I
will
happily
look
into
and
try
to
I
mean,
let's
be
honest:
oh
you
have
to
disable.
Selinux
is
not
a
great
answer.
It's
never
a
great
answer.
So
I'm
hoping
we
can
come
up
with.
Maybe
a
more
pointed
solution.
If
problems
arise
right
so.
A
Yeah,
and
is
there,
like,
you,
know
they're,
like
managed
environments
like
Google
container
engine
shift
online,
where
maybe
a
user
doesn't
really
like
even
have
the
privileges
whatever
is
there
anything
that
you
know
you
need
to
be
aware
of?
Does
it
need
anything
and
the
elevated
privileges
in
the
cluster
to
run
or
is?
Can
I
just
you
know,
use
it
with
any
kind
of
husband.
B
You
should
be
fine
with
any
kind
of
cluster
as
long
as
you
have
the
ability
to
deploy
that.
Well,
basically,
if
you
can
deploy
your
code,
if
you
can
create
a
deployment
that
runs
your
code
using
your
image,
then
you
should
be
able
to
use
telepresence
to
deploy
its
code
now.
Telepresence
is
dr..
Images
are
in
think
we're,
using
goodness
are
we
used
in
Kuwait
I,
actually
forgot
where
they're
they're
in
the
public
cloud
so
long
as
you
can
pull
that
down
right,
you're,
fine,
if
you're,
if
you're
firewalled
off
it
may
get
slightly.
A
A
B
A
Let's
move
on
to
the
future:
what's
you
know
not
necessary?
Only
telepresence,
you
mentioned
a
few
things
in
terms
of
improving
and
definitely
your
your.
So
you
can
feedback
more
use,
cues
from
the
community
and
testing,
but
you
know
right.
Where
is
that
whole
thing
heading?
What's
what's
next
for
telepresence
or
other
developers,
support
tools,
data
we're
well.
B
On
the
telepresence
front,
we
started
out
with
telepresence
by
by
addressing
particular
use
cases.
For
example,
I
want
to
develop
a
brand
new
micro
service
and
I
want
to
be
able
to
talk
to
the
cluster
talk
to
the
services
in
the
cluster.
So
for
that,
we
we
have
to
make
sure
that
you're,
local,
the
local
instance
of
your
service,
that's
running
on
your
machine,
can
talk
to
the
cluster
right.
B
So
there's
kind
of
three
pieces:
really
there
is
network
from
your
laptop
to
the
cluster
and
that's
the
sort
of
thing
where
I
feel
like
someone
who
works
on
a
kubernetes
application
could
kind
of
leave
that
running
all
the
time.
There's
really
little
reason
not
to
have
that
running
unless
your
cluster
has
services
that
have
names
that
conflict
with
other
things
you
use
regularly.
B
Why
not
just
be
constantly
connected
to
the
cluster
using
this
telepresence
channel,
then
there's
bringing
stuff
from
the
cluster
down
to
your
machine
right
now.
At
the
moment,
if
you're
using
inject
you
inject
TCP,
you
can
do
that
with
multiple
multiple
deployments,
but
if
you're
using
the
VPN
approach,
you
can't
do
that
right.
B
The
third
piece
is
perhaps
the
simplest
one
where
you
need
to
have
a
deployment
in
the
cluster
to
access,
configuration
and
secrets.
So
again
we
run
into
the
situation
where
we
want
to
be
able
to
do
multiple
deployments,
but
we
don't
want
to
run
into
this
issue
of
having
to
use
all
sorts
of
workarounds
for
go
binaries
and
the
static,
so
so
I'm
trying
to
fit
a
brainstorm
up
with
the
team.
How
we
can
separate
these
three
things
still
still
offer
a
reasonable
user
experience.
B
We
don't
want
this
crazy,
complicated
command-line,
so
we're
working
on
it
and
we
hope
to
end
up
in
a
place
where
it
as
a
as
a
kubernetes
developer.
You
can
reasonably
swap
out
as
many
deployments
as
you
want
to
have
them
all
running
on
your
own
machine.
If
you
need
to
you,
can
redirect
services
to
point
to
your
machine
rather
than
having
to
create
multiple
deployments,
and
then
you
can
access
all
of
the
the
usual
file
system,
type,
stuff
and
environment
type
stuff
that
you
can
get
in
kubernetes,
but
little
ways
out
from
that.
B
So
so
we
are
on
telepresence,
IO
is
our
website,
our
documentation
is
there
and
we're
on
github.
So
it's
data
wire,
slash
telepresence
and
it's
linked
from
telepresence
IO
and
we
are
very
happy
to
receive
issues
and
pull.
Requests
are,
of
course,
always
welcome
and
we're
particularly
interested
in
hearing
about
how
you
use
telepresence,
because,
as
I
said,
that
is
how
we
develop
the
feature
set.
That's
already
there.
We
want
to
know
what
you're
trying
to
do
so
we
can
help
you
do
it.
Is
there.
B
So
so
I
believe
we
have
no
I.
Take
that
back.
I,
don't
believe
we
have
a
roadmap
on
this
site
at
the
moment,
so
so
to
be.
To
be
clear.
I
took
over
development
of
telepresence
from
the
original
developer
a
few
weeks
ago
and
I'm
basically
running
down
his
his
set
of
of
suggested
changes
because
he's
brilliant
and
he
made
telepresence
and
it's
amazing
and
I'm
trying
to
do
the
things
that
he
suggested
first,
because
he's
more
aware
of
the
community
than
I
am.
A
A
Last
question
around
the
future:
whatever
off
of
telepresence
or
other
really
tools?
Is
there
anything
in
the
you
know,
you
know
sake
and
a
special
interest
group,
or
whether
good
it
is
community
where
you
you
want
to
submit
it
or
to
bring
it
in
I,
am
a
standardized
form
or
do
you
want
to
keep
it
in
your
space?
Is
there
any.
B
A
B
B
A
A
Perfect,
that's
a
great
place
for
people
to
yeah
reach
out
to
you
and
start
start
out
in
question
and
giving
feedback.
Awesome,
hey
thanks
a
lot
for
your
time.
That
was
great
and
yeah.
Let's
hope
that
you
know
seeing
it's
available
for
ownership
and
I'm
a
big
big
user
and
fan
myself
that
this
the
word
spreads
and,
and
you
get
even
more
feedback
and
more
users.
Thank
you.
Thank.