Thank you.
Hi, everybody.
I'm Maupachekko.
So a few years ago, I joined a nonprofit in the US.
The simple goal was to use my skills.
The skills that I have acquired in my long career as a software engineer.
I'm put in a good cost, right?
So the nonprofit that I choose or that I get into is some stack.
So some of the stack is a nonprofit that helps people on the represented backgrounds to break into tech, right?
So social, Hispanic and Latinx, which I am part of that community and allies.
So I don't know if you know how nonprofit works in the US.
I certainly didn't do like, didn't know at the time.
But nonprofits usually manage a lot of different things, right?
It is my contribution is no bullet from volunteer to be the city hall or some of stack.
And there I see it in monthly board meetings talking about two things.
So the first one was legal stuff.
Like how to protect the data of the people that we were like getting,
how to, I don't know, avoid conflict of interest.
And you know, lawsuits is almost the American national sports, maybe after tariffs.
And the second thing is managing the budget.
So the budget in an nonprofit, especially like ours, that is very small.
We get money from grants, from company match or from donations.
So the budget was a big thing.
But as a city hall, I really wanted to focus in the technology part in the strategy part.
So these are the four things that I get myself involved into.
So the first was maintaining websites and systems with the help of the volunteers.
The second like create content for hackathons or lab training skills.
Building community tools like resume reviewers, interview simulators or matching mentors with mentees.
And mainly organizing meetups with people or leaders from the industry.
We fast realize that all of these can benefit from the data recognition, right?
So each one of these activities, like for the volunteers, maybe the volunteer of the month,
maybe for the speakers that went to oral events or maybe went someone,
computer hackathon or maybe mentorship program, right?
So all of these require a digital recognition.
So we went there and then we looked for options and then we realized that the biggest one was
readily by Pearson. This is non-sponsored.
So we asked for a quote and it was insanely expensive, right?
So this was outside of our budget.
It was something that we couldn't pay.
So, you know, as a programmer as a heart, I said, why don't we build one, right?
So I pitched that to the board.
Not because it was easy, but because I think it was easy.
So the board saw that with good eyes.
I vaguely know about open boxes and stuff, but we have 100 things more to take care about.
So that went to the backlog.
I have been in the February for a few years, but it wasn't until, you know, who, but Twitter,
the one that we cannot name, that I moved my presence for good to the mastodon.
So I spent all my time there and I got really, really involved and excited about the activity
that everybody here knows.
What is activity pop?
And then I started creating my blog, right?
So I started creating my blog and then I read some posts about it and then it got viral.
You know, for the Fediver's kind of thing viral, right?
Like five reports and 10 likes.
But I really knew the challenges of the activity pop and the potential of it.
And then I remember my project of the batches.
So I say, well, why I don't build one, right?
Of course, I am not naive.
I have a long career.
I know that when someone thinks about that.
Good idea.
Maybe there are others that are working on that.
And yeah, I mean, I find that there are things.
I think the people that is behind activity pots is behind activity batches,
which was trying to create a new specification for how to do this,
how to federate batches into the Fediver's.
But I think it was not what someone was looking for.
And then I decided to still to build my own.
Now, I have a confession to make.
I love that net.
So I know that is not the first choice for many people in the Fediver's.
I know, but I think it's a beautiful language.
So I decided to build batch fed in dot net.
And I knew that because it's not the first option for many people in the Fediver's.
You need to be scalable, extensible, you need to be based on the standards.
You need to be something that maybe people don't go to toast the code of there, right?
So I decided to do that.
I didn't want to create a new standard.
So of course, I look into activity pop and open batches.
So activity pop and open batches, as you may know, both are based on JSON, L.D.
So this is language or specification for link documents in JSON.
And I know that maybe here is going to be, yeah, I was thinking that maybe I could
zoom in, but I don't know how to do it in Max, sorry.
But basically, this is an open batch object.
And it has many sections.
It has a section like a batch, an issuer, and a recipient.
So the recipient can be a URL or an email.
So I decided why not to link the identity of the recipient with an activity pop actor, right?
Or why not the issuer, which has an ID and a URL,
can be that an actor, right?
So that's why JSON-LD can work on, like you just link a document with another one.
So I discovered that in activity pop we have attachments.
Attachment usually are used for images or for videos or kind of things.
But there is nothing that tells me that it cannot be used to actually attach an open batch, right?
So this is how it looks like.
So this is an activity pop node that has inside an attachment that is an open batch.
Now the issuer, the URL of the issuer, it is the same URL as the attributed to, like,
feel.
So this is how you link that.
There are a few other things about how to sign this and everything.
But basically, this is the main link between an open batch and an activity pop node.
So now this enables a lot of different things, right?
So now issuer can be followed, then batches can be, like, commented.
You can share, you can boost, you can even quote.
So these are social features to open batches, right?
So this is how it looks like.
So it basically, this is a batch fed instance.
You can see that I am taking right now an issuer from my batch fed instance.
And I put it that into MasterDone.
So in MasterDone, I can follow that.
And you can see that the notes show there.
The recipients or the batch is also there.
I will copy that.
I will go to my MasterDone and then I will can interact with that, right?
So if I, like, fast forward a little bit,
you can command it the batch and then you go to batch fed and it will show the comments.
So people can interact with the batches directly in batch fed, right?
But now, because an issuer can pose a batch, right?
And this is an activity for batch.
Issuer can also follow the issuer's.
And then issuer can receive those notes.
And then they can validate that those are actually batches.
And then so here you can see that that is how the centralized aspect works.
In this instance, I have external batches and I have batches of that instance.
So they can decentralize each other.
So now I can just view the batch in the original instance.
So this is really a cache.
This is very, very similar to how MasterDone does things with notes.
Because I can do that.
Now I can have relays.
I can have one actor that just repose things about that university, right?
I can have batches for my indigames.
So indigame industry can have a relay.
And you can follow that actor and then you can receive the batches for that actor.
Or for a specific industry or for a specific region, right?
So now the federation enables all of these basically because activity.
So I mean, I have so many demos and I don't know how many most minutes I have.
Yeah, I think I have a few.
But I mean, this is something that is working.
Now, because batches now lives in the fediverse.
You can create your own wallet, right?
You can create your own wallet.
Again, this is based on standards.
So you can put some code there that listens to notes.
Check that half an open batch.
It is linked to some notifications.
And then you can have your own Mozilla backpack.
Or I think it's called batch here now.
You can have in your domain.
You can have your batches there.
Your employees can go there.
Or you can, I don't know.
Say, hey, I am very good in this indigame.
And I have that in your own domain.
Right now, I think it's not loading.
But right now, yeah.
Now, you can embed those batches in your website.
For some reason, the videos are not loading.
Yeah.
So this is my profile.
You can go to your profile.
You can just copy like a snippet.
And then you can embed that inside.
I will make all this slides available.
So you can see all the money behind batch fare.
Right?
And the thing that enabled this was to some mistake.
And I know that this is linked in.
But some of us that usually made use of linked in to reach the community,
the Spanish community.
And then you can see here, we have like.
Issue a lot of batches for all the volunteers for all or community for all or speakers.
They don't even know that this is the Fedivers.
They just receive the batch to the profile.
They have like this linked in capabilities.
And they can interact with the batches.
And they don't know that are in the Fedivers.
This is really now making an impact in or non-profit.
And now I want to expand that to other non-profits that are out there.
So the problem was traditional batch platforms were costly, but also were siloed.
Now we want to create something that is standardized, open source, federated.
It doesn't need to be in.net.
You can create it in Python or.
But the key takeaway was it is not about batch fare.
It's about the idea that we can link these technologies.
And then we can do this in other instances.
I want to see this implementation in other languages if possible, right?
So as a developer, you can grow there.
You can try to help me in UX or development,
integrations, documentation.
There is a lot of things to do there.
There are already some people that have contributed.
So thank you very much.
I issue some batches.
As an organization, maybe you can use batch fare.
Or maybe you can join community credentials.
It is free for non-profits.
So they can just go there and then start issuing batches.
Also as a supporter, you can go to that web page right now.
Vatfet.org slash get slash force them 26.
I don't know if my server is going to be able to handle 100 people getting batches.
Let's find out.
Yeah, let's find out.
You can break my server right now if you want.
And then at the end of the day, this is going to be locked down.
So take your batch if you can.
There are a lot of challenges.
Scaling.
How to search batches.
How to do discovery ability.
This is not new for batch or only isolated for batch fare.
But also for all kinds of diverse implementations.
Moderation.
How I avoid someone to issue a batch that I don't want.
It has some basic moderation like public and private and stuff like that.
But still we need to have more right.
And then identity portability.
How can we move credentials between platforms?
How can this something that that we are having is some mistake?
How can they have their own instance?
And then move everything from community credentials to there.
But this is not just for batch fare.
This is our challenges for the whole diverse implementations.
Right.
So I really believe in this project.
So the question is not like how we are going to transform it.
But the question is how you are going to help me to get there.
All right.
So again, these are the links and I can take questions.
All right.
We've got hand here.
We've got a hand here that there was actual vibration where I was sitting.
But I think that's because Evan is kind of drumming his hands.
Hi.
What's the feedback from the community that you've received about the batches?
So I got good feedback.
A lot of people love batches.
But the first thing that I received was that it was a spammy.
So because if you are in a conference right now and you issue 100 batches, you have 100 notes.
And if I put a hashtag that is for them, then people are going to get 100 notes about that.
So the first thing that I think and you put an issue, I don't remember.
But the first thing that we did is we had some hashtags that people can filter from.
And then we did some modifications that bought.
We still need to do more modifications like for example, a batch that can have multiple attachments.
And then you can just issue 100 in one note.
So that was the first feedback.
But then another foundation from Poland.
Then join.
And then I realized that everything wasn't English, right?
So I have like a federation discovery.
I don't know.
Like I waited.
You can fed it with different batches instances.
So that's another one.
Like, oh, I forgot to add a language, right?
So I mean, the more people use this, the more I will get closer to something that can.
Everybody can use.
Just before Evan says anything.
I think I've been a big fan of this particular project.
I've been a fan of all of your projects.
I'm such a petty fan.
But from my background, I've been in I'm tech for a long time and yeah, I was IBM and they do these.
You know, badges for your accreditation and things.
And then I knew the Mozilla effort around open badges as well.
So I just think this is such a cool idea.
Congratulations.
Yeah, thank you so much.
One of the use cases I think you mentioned earlier was about identity verification.
And I just wanted to check and see how that works or what you think.
Where do you think it would work?
Like, this is the real Evan Pedro Moff.
Yeah, so this project opened to me a world of micro credentials, right?
That I didn't know it.
So there is a whole community there that is very active.
And there are a lot of challenges that are not specifically about the Fedivers or the
Batchets itself, but outside, like, how did you cross an issuer, right?
How did you know?
So you can actually issue someone from UK told me, hey, can we verify the age, right?
Like, you know, now in social media, you have this age verification.
Can we, like, verify the age?
Yeah, of course, like, if you have a government and everybody tries that government,
you can issue an open badge.
It has some cryptographic protections and everything.
So it can help.
Yeah, it really can help.
I really love the Federation, but the same challenges that the community has for
the micro credentials things apply here.
That is not a new about that.
Okay, anybody else?
Go on down there from Ian.
By the way, awesome.
Awesome.
T-shirt.
Swatchet, you're wearing.
Yeah, thank you.
He's always that.
Does anybody know he writes this blog?
The feature is federated.
I think it's put.
It's a really good one.
You should all be watching it.
Sorry, Ian.
So, yeah, I've, well, I saw this up for the forum.
I was blown away.
Yeah.
And I was blown away.
And I've been speaking to public service broadcasters who want to use this.
And one of the things that they can be asking me is, could you combine this with some
of the bridges?
So then you could start to, obviously, on your profile, you could say, look, I've
put it's badge, but also you can also push it forever as well.
It seems like it should be possible.
But it is possible.
So I explore this in two different ways, right?
So the implementation is very simple.
Activity pop, plus open button, JSONLD, right?
You can also take that simplicity and go to blue sky and say, hey,
I will search for all the posts that have a link.
And then I will check if the link has an open button.
Well, you have this centralization there.
And the other option is, like, I will create a whole taxonomy and stuff.
And then in blue sky that nobody's going to support.
And then I need to have 100 million of users creating an app that you'll
say that.
So you have these two extremes.
It is something that is pending in my backlog.
Mental backlog, but I am very bullish about Activity pop.
So I want to go there.
If there's a pay you, what the backlog is.
That yeah, Monica resolves a lot of different things.
Maybe not passion, but yeah, of course.
We can try somewhere.
Do we have any more questions from a heart?
It is crazy to me that companies like big companies like Microsoft
would like say the certifications incredibly.
I mean, that is mind blowing.
Like you need to have your own instance.
So, but thank you very much.
All right. Thank you very much.
Thank you.