Alright,
well,
so welcome to prime time,
we're gonna go ahead and get started with the questions that we have
established.
Uh,
so we have what the dog doing,
this is what the dog's doing,
um.
This is what the dog's doing.
Hey Mr.
Fire,
uh,
how am I doing?
I'm a bit sleepy today.
I had to wake up for like an earlier meeting than my,
my sleeping schedule should have allowed for,
and it's just cold as well.
Like,
I don't wanna,
I wanna go outside.
This little guy was um very grumpy last night.
I don't really know why.
I think his tummy might have been a bit upset cos the only thing I could figure out.
Um,
was that his tummy was making a lot of noise and so I put
my hand on his tummy and it was just going like I was like,
oh,
maybe you ate something that disagreed with you.
So
he's OK today.
I think I walk down the park will help out,
so we'll do that after this.
Um,
next up is,
do I have your permission to transmit Fetter over SSTV?
Yeah,
sure.
Fetta's got an Instagram.
You can take any photos from there.
He manages his Instagram.
It isn't me that manages it.
So I know he hasn't posted in a while,
but like,
it's his fault.
He hasn't managed it.
I think he forgot his password,
maybe.
Did you forget your password?
You did.
Oh,
OK,
I understand.
What the human doing,
I'm holding the dog right now,
that's what's going on.
Uh,
knob it is the next question,
which is not an answerable question.
Uh,
so we'll go from that on to
Moonbase who's talking about the failed to establish connection errors.
Do you have the,
the GitHub issue for that one?
You got the,
the GitHub number for.
Get me the GitHub's number for that one.
Yeah,
I know that you might have replied to it,
but I haven't seen your reply.
Give me the number.
You send me Mr.
Feder's back feet.
I don't know why,
but he seems to like it when
they're resting on my hand.
Whilst waiting for that GH issue,
does anyone else have any other questions?
It's a bit light on questions today.
We could also open up the tech tree,
which I did promised to do.
Um,
what are you doing?
What are you doing?
Are you licking?
OK,
understood.
Is that all you're doing?
OK.
Sorry,
there's no questions and I'm
distracted by liy dog.
Hi,
you OK?
Oh,
thank you for the issue.
Just a second.
Stop licking my face.
I'm trying to
read over.
Thank you.
Hello.
Uh,
you,
uh,
you linked me a closed GitHub issue,
um,
when no one's complaining of the issue.
So
if you'd like,
um,
help with that one,
post a response saying it's still happening,
add some new logs,
or maybe open up a new GitHub issue and we'll be able to.
We'll be able to,
uh,
we'll be able to
uh help you out.
Uh,
Carlson's just linked
another
random
GitHub issue.
Let's take a look at that one.
Uh,
this one might actually be the same as the one
based on the time frame,
but we'd,
uh,
I'd have to take a look.
I don't,
I don't see any
urgency on either of the issues,
particularly seeing as one is,
is closed.
Are you going,
OK,
bye bye,
bye fellow.
Uh,
so any other questions?
Or is it tech tree time?
Question here from Powder Pup who says,
uh,
how has
the asset variant system been doing since the transition to?
Yeah,
it's great.
Um,
the metrics are looking really good.
I did want to add some more metrics,
but we're kind of at the point where,
Um,
the metrics don't really tell us anything or anything more.
Um,
they might be able to once we're able to fix,
uh,
the like 6000 bugged,
uh,
issues,
which I do have uh some questions out to fruits to try and resolve those.
That'll get the number down to actually 0 rather than 6000 being our base.
Uh,
we've also got some bugs with,
with,
uh,
some bit maps.
I don't really know why.
So the,
the,
the strange thing to to keep in mind on the,
the failing graphs,
which are right at the bottom,
is that
it's a failed task,
it's not like a failed image cos like images can be in multiple
tasks cos it's like a que system and sometimes they come back round.
So there's probably,
I don't know,
like maybe like 60 to 40% of the number
you see might be the actual number of assets that
have a problem depending on how many times they've been through the queue.
So there's a um an inconsistency with ETC2 RGB crunched,
which is like usually
very easy to do.
It's like you can see that like 28,
29,
30,000 of them have succeeded and 86 of them have failed.
It's just like,
That's still 99%.
So
we're gonna take a look and
figure out,
hey,
what's going on there,
but there are a couple I'm aware of.
Uh,
we don't support
our 8 or something,
so,
uh,
that one after that.
It'll be,
uh,
pretty much just like it'll just keep running.
Like,
hey,
remember when the bridges and the relays kept going
down and then I fixed them and now they,
they
rarely go down.
I know the US one does,
that's actually for a different reason
to,
um,
what it appears to be.
The um US one goes down because it's the first in the,
the list of
queries that
the status checker does.
Um,
and occasionally it looks like the status checker is
getting rate limited,
checking your API,
which is a bit silly.
I can directly speak to the,
um,
the bridge though so I can remove.
that from using like another API core,
which is also like a bad move because it means like
if the cloud API goes down,
you'll see the bridges also go down and that isn't that the bridges are down,
that's the cloud API that we're using to report the bridge status is down.
So I,
I just need to move the alerts over to.
Um,
just directly talking to them,
cause we're directly talking to them over HTTP anyway,
so we can just check for a presence of the endpoint hitting 200,
uh,
and then it'll be like
better,
faster,
easier,
and without rate limits,
but I just keep forgetting to do that.
So yeah,
the,
uh,
the
bridge and relay just don't go down.
Asset worker now just doesn't go down.
Um,
I wish I could claim like all the credit for it,
but what I basically did was shoved it inside a .net 9 generic host
and
uh then put it in a,
well,
actually the bridge and relay aren't in a docker container yet,
but like the variant worker is,
it's in a docker container
and I just put like
restart unless stopped
onto it and so if it crashes it just restarts.
Um,
the failures that you'll see there are also you know might cause it to crash.
Uh,
red asks,
what's your biggest want for a future feature that would be a pain to uh implement?
So the biggest,
most painful feature to implement,
um.
I don't know,
there's like there's like so many things that like
I know we're going to be a pain,
but that's like part of the reason why we're here and doing it because,
you know,
in some cases no one else has done it,
um,
or in other cases it's done differently elsewhere,
etc.
but I
I don't know.
It's always difficult to like evaluate such questions because it's like
today the answer might be this,
but tomorrow the answer would probably be something else,
etc.
I keep saying it,
etc.
so I'm gonna try and stop doing that.
Anyway,
um.
At some point this year I've got to integrate with
Microsoft's Azure Active Directory or whatever they're calling it these days.
Um,
they renamed it from
Microsoft Active Directory to Azure Active Directory,
and then they called it
Etreo or Erea or something like that,
ID,
um,
but I just saw that they renamed,
um,
Office 365 to co-pilot 365 or something.
So
maybe Azure Active Directory will be
um Azure co-pilot directory at some point
cause that's exactly what I need is a
larger language model behind my uh identity provider.
Uh,
but yeah,
that will be
much,
much better than
um the current
approach that we have for like larger organisations.
We're using SAML right now,
which is great.
Um,
but like an active directory implementation
would more closely tie the systems together
in a way that would allow for active
directory changes to be reflected over and resonate,
so.
Um,
if the company would be,
I don't know,
let's say someone gets fired or quits at the company,
we wanna deactivate their company account
and right now we would then have to,
they'd have to like probably email us or something,
or like,
I don't know,
like there's no flow that would
would be set up currently for that,
where we would have to delete their resinant account
or at least you know prevent access or whatever.
But if we integrate with
um Active Directory or any other identity provider.
Then,
um,
the moment that identity provider goes,
that account is terminated,
they wouldn't be able to log in.
Like it'll all be synced across somehow.
Also makes things like group permissions really easy because,
uh,
Active Directory has like groups and permission sets and stuff like that.
And again,
we can just sort of use their sets and use
their groups and their permissions to sort of inform our own
um
stuff.
It's a completely useless feature for um regular players.
So don't,
don't
think of anything
good about it,
it's,
it's purely business,
but I know it's gonna be a pain.
Uh,
there's other ones that are gonna be a pain,
um,
but
I don't know.
Ask again,
you'll get the other ones,
I guess,
cos there's a different answer every time.
You forgot formerly Microsoft Active Director.
Actually,
I think you probably have like more names.
Let's get the entire history of Active Directory names up on my computer here.
Active directory,
yeah.
OK,
Active Director is apparently a a slightly different
product because it's the one that you can install
um on your,
on your servers.
But you can do that with Azure Active Directory,
there's a thing called like
Azure loopy flop,
which allows you to put um
Azure services onto your own infrastructure.
Yeah,
I remember seeing an after directory screen
um in my IT class,
right,
because someone had to go in there and change someone's password or something,
and it looked cool,
but I didn't understand it at the time.
I know you want to go outside and we'll promise
we'll go outside as soon as we're done here.
Noki says,
how does one do local values of dynamic variables?
I
don't
recommend
that.
You've only use locals,
use a local,
otherwise you're just.
Like
fighting the data model.
Yeah,
I guess you could drive the value.
Oh there you go,
just drive it.
Yes,
so if you use dynamic value variable,
which is the one that has,
um,
the value as an input field,
and then you drive that field with a drive,
um,
then
provided you don't
update the variable anywhere else,
um,
and
that should work.
Have you resorted to just barking at me now,
is that what you want
to try and get us to go outside and like.
It says how do people localise volume systems in worlds?
I mean,
volume
stuff is usually just value user override on like a
slider.
In fact,
if you hook up like a value user override,
yeah,
value user override.
Um,
if you hook up,
you hook up the dynamic variable locally
and then
just drive it everywhere,
right?
So I reading the Microsoft Azure Etra ID
website
and it's just like all over it.
It's just like Azure is now intra ID.
It's like Azure blah blah blah intra ID.
Here's what it can do
without actually like describing what it can do like at all.
And there's like a diagram which is just like,
it looks like one of those like science diagrams that are actually
shit posts because it doesn't provide like it doesn't tell me anything.
It's like,
hmm,
OK,
so my HR system,
my external identity,
and my workload identities can connect to the blue cloud.
It doesn't mean anything.
Oh my God,
it's just like,
it's just crazy.
Yeah,
I got like a bunch of Azure stuff to look at.
Um,
we don't currently use like a Azure key vault for our secrets,
we use a different route.
I won't tell you what route because.
Talking about secrets is weird,
but we wanna move it to um
it's your key vault,
so I need to look into that as well.
That's easy though,
that's just gonna be like,
especially when it's like a,
a piece of code that like no one's touching
and no one's going to touch until it's ready,
I can just set up a keyvolt instance and play with it.
Uh,
so that's gonna be OK.
I might do that like weekend or something for fun.
I might do this like
really aggressive stressful task for fun at the weekend,
guys.
I might.
All right,
we're kind of running out of questions here,
so how about I open up the tech tree?
Yeah,
let's open up the tech tree.
Fetta,
you can come back on here absolutely.
Come on,
there you go,
back on my lap.
Good,
good.
Welcome to my lap,
how you doing?
OK,
you're gonna lick my face again,
great.
Yeah,
keep going with the questions,
they're fine,
but we're gonna open up the tech tree.
If I can get there
cos I'm being attacked.
Hey fella,
that's my desk,
you can't go on my desk.
That's the rule,
remember.
Oh God,
why did you do that,
doc?
Get off.
Thanks.
All right.
Welcome to the tech tree.
So I'm gonna make some updates,
uh,
cause it has been closed for a week,
so let's let's go ahead and make some updates.
So I gotta go into
where are we,
this is like.
There are still bugs,
but it's like basically done.
I know way in progress,
completely agreeing,
done.
Uh,
it's the asset worker,
uh,
yeah that's in progress,
asset worker,
yeah,
that's fine.
OK,
cool.
Uh,
still in it,
that's fine.
Uh,
yeah,
are you good.
Let me open the questions on another tab.
So this isn't,
this isn't like a roadmap or like a timeline,
this is
like a
tech tree or like a series of connected arrows that sort of explains
how various features interreact and what we're working on.
Like you shouldn't read any of this as timing or
uh timeline related,
it's purely sort of relational.
of ideas,
uh,
in a way that sort of helps people understand
why certain things take longer than other things,
or why,
uh,
certain things end up being prerequisites for other things.
Actually,
yeah,
someone dropped a note I think earlier on in the previous week's chat.
They were saying that
we had finished
the settings rework.
Which is true.
So that can go in you where we work,
cool.
So keep coming with your resonate questions or if you've got feature questions let
me know cos I can add them to the map as we go.
Uh,
this is actually in Fergus by J4 right now,
uh,
better enough.
Uh,
oh,
this was done as well and doesn't really matter.
It wasn't like really done
effectively,
but yeah,
whatever,
um.
Uh,
Lucas asks,
uh,
I had a question with the round about rights,
do you know whether what writing the same value to the field gets networked?
Are you talking like if I write
one
to like an in field and then a second later I write one again,
so like no no change in the data,
just the same data over and over again.
What?
OK,
yeah,
uh,
the what was to Feder not to to you guys,
he's been a pain in the butt.
What's up?
We'll go out soon,
I promise.
Let's,
let's let's cut it at 5:30 today.
So in 5 minutes,
we're gonna go outside,
Feder,
5 minutes.
I know that you have no concept of time,
but 5 minutes.
Um,
I don't know enough about our networking system
to understand how that would be deduplicated.
You could test it,
um,
if you,
uh,
pull out the,
the ribbon display,
the,
um.
Uh,
impulse display,
um,
and your other person in the world sees it,
then the event had to go through the network,
like the right success or whatever.
That means like if the right success pulses and it's the same data,
then that means that like something had to go
through the network to do that unless it went
via the network on the,
I don't know if the impulse display node networks,
uh,
it's a good question,
it's just,
it's just complicated.
Um,
feta,
what?
We're gonna go out in 4 minutes,
OK?
I'm cutting an event short for you.
4 minutes,
4.
Uh,
OK,
so next up is
Ny says how we will create a system where a repeating timer
on a reminder was controlled by a locally set variable controls such system
and when it's evolving timers and sounds with a local variable.
Uh,
like one of.
Local,
I've never really seen like a local timer.
There's usually like global timers,
like,
you know,
save the world,
world is shutting down,
um,
game systems where there's a synchronised timer as well.
I've already seen a local timer.
When it comes to a local timer,
it's probably
not suitable to do like something like the stopwatch node cos that syncs.
Um,
oh my God,
Mr.
Vedder,
you are such a pain.
3 minutes,
Mr.
Feder,
I promise you,
we'll go straight out,
straight down to the park,
yeah,
um.
Yeah,
I presume stopwatch wouldn't work.
Uh,
a lapsed time also wouldn't work causes that sinks.
You'd probably have to like write you see nows somewhere.
I don't think we have like a a local stopwatch.
There is,
there is like one way to do it,
which is like crazy,
which is using local impulse timeout,
um,
which I've done before.
But like,
don't advise that one as well.
Uh,
that is like you set up like a local impulse.
I think the local almost timeout thing is actually bugged and it's assigned to me.
But like,
yeah,
there's a um
local impulse time that could theoretically be used by if you have a
uh a bucket size of one.
Um,
and you
pulse it,
it will go to overflow.
And then if you set the timer on the bucket to be your timer interval,
it'll overflow until
that timer has elapsed and then you can,
you can get another output.
But that's like a really weird timer that I've only used once and that was back when.
Uh,
that no worked.
Uh,
other than that,
yeah,
you'd probably just have to write
actual date time nodes locally
and then compare them to
the current UTC time
and then that way you'd have,
Full control over the like synchronisation of parts or not parts of it,
cos what you'd do is you would say the,
the,
the goal time,
like when the alarm should go off and
you could make that a local variable and then then do it that way.
Uh next up is what do you think about using a value copy
on a variable to itself with right back to make local values.
Please don't do that.
Like you can absolutely do it and like it'll probably work,
but
it's,
it's very clear that you're doing something unintentional there
and it's very clear that we might accidentally break that.
Like we might purposely break it,
I don't know,
I'd have to look at Freaks and and talk to him about the,
the data model rework,
but
aside from just like.
Purposely breaking it,
that's something we can easily,
easily accidentally break.
Uh,
yeah,
you should be using the other,
the other,
uh,
value types as well,
um,
rather than like all this like weird hacky stuff.
But I know like,
you know,
giving out the Proto Fox tool for like one variable is soon as forbidden,
because,
um,
as a community we can't get past the point that like components are somehow optimal,
even though they're young and it's exactly the
same and has always been exactly the same.
Yeah,
what Jeb said,
sort of what I was doing,
but like the
technical expansion of that.
All right.
Has anyone got any questions on the text for whilst it's open,
any,
any features you're wondering about,
any features you don't see,
anything you're confused about,
let's,
let's go.
We got,
haven't got much time left.
Go once,
going twice,
sold to the
chihuahua on my chest.
Or go off ahead and leave off.