Thank you for joining us, so the next talk will be about recent advances in privacy and
collaboration.
Thanks for the introduction, so I will present a quick pad today and basically, more
said, like recent advances, actually, in quick pad not in privacy and collaboration.
I mean, yes, it is part of it.
And so I am Fabric Morten, I am a quick photographer and I am one of the developers of
the, I mean, I am part of the quick pad team and now I show a presentation to
what, um, kids not working.
What created, what created the quick pad is.
So, first of all, a quick pad like is a collaborative office suit, like really an office suit
with many different applications.
And actually, even in this, this screenshot, this cascade of screenshots, there is one
missing, there is not the diagram apps which helps making nice diagrams.
But we have a large span of different applications.
So, I don't know why it did this.
So, we have like all the office, usual suspects, like spreadsheets, document and presentation.
And also, other things, like Markdown HD, rich tech edition, which is a bit different from
documents because we, it's really like to produce rich tech documents and not like type set
type set it document and some whiteboard apps and actually other things for collaboration,
like Kenban and forms, which we don't have, which is, which we don't have in other
aspects, in end-to-end encryption, in an end-to-end encrypted fashion.
And as I said, also, the diagram, like just the diagram in apps where you can
make things as nicely as you want.
And the thing that, so they say it's an online collaborative office suit.
And the main difference with all those solutions, it's open source.
And it's end-to-end encrypted, meaning that in, in, or you don't need to trust
us to have your data stored with us.
And it has been born at XWeKit 10 years ago.
It's actually started as a small, like, a research project, like just to have real
time in XWeKit, which is, which you will see other presentations today.
And so, that's where the name comes from, CryptPad, where it's a bit misleading because
we will think that it just like hit our pad, for instance, encrypted, but in the end it's
a little official.
And, actually, not many people know that, but that's a bit sad for on our side.
And it's really false.
It's a GPL V3, as a lesson.
And we have, like, this breakthrough site, and we also host, as, I mean,
it took here as a company.
Also, host, flagship instance, CryptPad.fr, which is one of the biggest one I
did actually in use.
And then it's, there is a question, like I said, that it's end-to-end encrypted,
and why do we need to have end-to-end encrypted, like, office, office things.
So, I think that, like, one of, I mean, the biggest actors in office will be, like,
Microsoft and Google.
And they are not really known for, like, respecting GDPR, there are other things with
that the data may be stored in the in the US.
It's a new, both are US companies, which are not really compatible with EU laws.
And, especially this day, it becomes worth and worth.
But, I mean, it's kind of important.
And the thing that, there are many, like, institutions where,
they have the need of using office shoots.
And, like, schools, for instance, and then, there are, there are sensitive
sensitive data, for instance, children's data, which may be stored in this unsafe
environment.
So, that's where we come, we come.
And we want to say, like, yes, in this context with ScriptPad, you can have both
real-time collaborations, something that is quite easy to use.
Where you don't need to have, like, all this knowledge about cryptography, about, like,
how things work, like, for instance, with PGP, where even, like,
trying to, getting started, like, the onboarding step is kind of complicated
because then you have a list of different keys you need to check.
And so, we do all this.
I mean, iPad does all these choices for you and gives you, like, something
that doesn't change a lot from your everyday use.
Also, with other things that, obviously, are missing because we are doing everything, like,
in a secure manner.
For instance, for instance, like, pass forward recovery.
We don't have it because we don't, we have no way to link,
I mean, one of your drive in our, in our storage and your user name.
We need, like, both your name pass forward and we can do anything from that.
And so, yeah, there are some things missing, but we try to give you, like,
as a best user experience as, as we can provide in this context.
And how do we do that?
So, the development is made, like, mainly on GitHub.
You know, it's not the best way to do it, but, at least, we can reach a large community.
And the development is led by the crypto team, which is hosted at XWC.
And it, which is made of nine people, which I'm glad to be part of.
And we have quarterly release where we moved from, to calendar versioning, like, this year,
because we noticed that semantic versioning doesn't mean a lot for a product that is, like,
basically, um, running release, like, we are basically, like, here, every quarter,
we, we met a new release with all the bug fixes, all the improvements, all the features,
uh, in it, after, like, a strict, uh, release calendar with testing and everything,
as much as you can do in a, with our team.
And, uh, if you need anything, like, we have, uh, different ways to contact us.
So, inside the crypto pad, we haven't, and to an encrypted, uh, support system,
which uses, like, actually, the crypto mechanism to, to do this.
Uh, actually, I won't enter into details on how it works, uh, for that, they're, I mean.
There are other resources, uh, and, and, even other tools I gave, for instance,
at Puzzle Salt, uh, last year, uh, so, and so, let's come back.
So, we have also, like, uh, GitHub issues, uh, community forum, and, uh,
a metric space issue need, like, have to ask, like, a quick question,
if you are, like, for instance, hosting your own instance, and you want to have some help,
on that metrics and be the nice place to be.
Uh, community forum, if you have a question, you're not sure if you need to open a GitHub issue,
or simple debugging on, uh, on your instance, and, uh, then GitHub issues for
really development, uh, development parts.
We try to keep everything, like, we separated this way.
And so, no, the introduction is done, and let's see what, uh, what,
have we done in Trippad, like, in the past year.
So, one big change is, I mean, one big thing is on only office.
So, if you are using Trippad, you may know that, um, so we have different applications,
and if you are, and, uh, we are using only office for the office part,
for the main, uh, for, for the quality.
And so, there are, like, uh, spreadsheets, documents, and presentation.
And if you have a free account on Trippad, if, but FR, or even if you are hosting
your own instance, by default, you want, you will only have access to spreadsheets.
And, um, one reason for that is that is, um, was, um,
stability issue we had with, on your face, because if you also know, like,
how only office works, basically, it's mostly the client, which is,
HEPL, which is open source.
I mean, which has an educational license, and then on the server,
it's a little bit more complicated.
And, uh, in our side, what we are doing is, basically,
hiking the client, and we are emulating a server with Trippad,
which will replace the patches that, uh, on your face, does.
So, we are working directly with only office spaces, and, uh,
it leads sometimes, because it has, it has been something that has been hacked
in the world, uh, stability issues, especially with other apps and spreadsheets,
because spreadsheets, but it is, um, the atomic part will be a cell,
and then you have let will, you will have less.
It's less error-pronged, and documents where I try on your face,
sends a lot of, uh, of changes.
I mean, the, the patch are like kind of complicated when you are changing,
something in a paragraph and stuff like that.
And also for presentations.
But the nice thing is that, in 2024, we improve this stability a lot,
and actually this, uh, those two applications with foreign,
like, basically in detail, like, will be released, uh,
in the next, uh, I mean, I think it's, it will be in the next weeks,
next weeks, and at, at most, uh, in the next release, which will be in March.
So, I keep, uh, stays, I mean, stay tuned for that.
And also, like, we want to upgrade it to only office 8,
which has been released, and, uh, like, brings new, new features, uh, for only office.
And now, uh, there are other changes, as well, for, in accessibility.
So, basically what we want to have, um, will,
to point a, uh, web content accessibility guidelines, uh, compliance.
And, uh, for that, we have different focuses, like,
like, on keyboard navigation, like, having it, uh, working as much as possible in
the iPad, we have a lot of, like, fixes to do around it, but, um,
but yeah, it, uh, you can mostly use keyboard navigation to do almost everything in
the iPad. It may not be the most, uh, usable, but at least it's doable.
Uh, there are also, like, focus indicators, like, when you are focusing something,
you need to see where the focuses, especially when you are, like, navigating with
keyboards, and obviously some responsive design, which will be, um, linked, uh,
linked to usability in mobile as well. So, you want to have things that,
can be used in many different devices. And, for that, we did last year, uh,
the next, the next accessibility scan, actually,
collectivity scans, um, in, uh, last August, which was done by, uh,
H.A. University in, uh, in the Netherlands, and, um,
technically, University of Atlanta in the Netherlands. And so, it, it targets,
like, uh, WCAG 2.2, which is basically 2.1, but, but with extra,
I mean, minor changes. I mean, some changes, uh, and it's,
and it's strictly stronger than, uh, 2.1. And if it has done for apps,
so, uh, not it was done for different apps, and for the drive, which is,
which is, uh, why you arrive when you connect on creditpad, and which released all
your files, because it's two different interfaces, and, uh, wanted to have the,
them assessed, uh, differently. And, uh, at the end of, at the end of this,
accessibility scan, basically, the issues are labelled on GitHub with, uh,
hand, uh, accessibility scan, obviously. But the thing that, actually,
the audit says that, um, the suite is quite accessible already.
I didn't put the one for drive, which basically said that the drive is,
I mean, is there a good and well labelled, which is not the case for all the apps,
because, basically, we have integrated many different apps, and we want to have
a, um, protein-nice together, and, um, and yeah, and then we have other,
like, contrast issues and things that we want to address, but it's already in our,
it's in our roadmap, it's in our issues tracking, and we hope to handle them,
as soon as possible. Also, and, uh,
similar or not, like, they have been, uh,
advances in mobile, um, a mobile, like, on the usability of crypto
mobile, uh, we had some good reports about it.
And, um, the thing that here at the goal, what I've been to,
improve the UI responsiveness, having things nice, uh, on mobile,
and improve the mobile experience, uh,
unfortunately due to the way crypto is more, I mean, uh,
I mean, because we have everything integrated, and the way everything is loaded,
is not really mobile friendly, as for now.
So, even if we are, like, having improvements on, like,
the mobile experience, we still have a lot of bottlenecks to,
I mean, a lot of issues to tackle, uh,
before having something very smooth.
And that can work on many different mobile devices.
Obviously, if you have a very good mobile phone, if we'll, uh,
work on, I mean, at least, as, uh,
I mean, in a manner similar to, uh, a computer experience,
but, um, magic.
So, the thing that we, what we did, like,
was to have all elements that, uh,
that are easily accessible and visible and mobile.
So, basically, it's a responsiveness thing,
but basically, when you are on mobile, you want to have things bigger,
so that you can press on it with your big fingers,
at least me, I need that.
And, um, so that's the thing, like,
we optimize the scaling and, uh,
on all the, uh, on all the elements,
especially, like, both that can be quite small,
and also, yeah.
And now, uh, as I said, like, we need, like,
to have, uh, I mean,
there are some bottlenecks on the mobile impact
and, uh, those are actually, like,
in the, in the architecture of Crepad,
and we did also some, uh,
improvement, like, not really on the architecture,
but on the server side, uh,
which is just there for this increment,
I mean, to enable this synchronization,
the thing that we, one of the things we provided this here,
because we met actually in, um,
I mean, in Crepad, we met, like,
some, some scalability issue.
Uh, and, uh,
it was basically, because of the, uh,
Creptography plugin, I mean,
Creptography library, sorry,
that was used in our server to verify the signatures,
basically when you are sending a patch before,
committing it into our servers,
we verify that the signature and the encrypted data
is, uh, is a valid one.
And, uh, this verification step part,
like, was, uh, very heavy.
And, uh, the reason was that we're using,
like, tweet, tweet an SEO,
which is, uh, like, uh,
uh, Creptography, uh,
Creptography library, so jam library,
in JavaScript, in full, in full JavaScript,
which is, like, quite simple,
which is really small, uh, like,
in, uh, in terms of number of characters,
which is not the most, uh,
optimized for hardware,
and, uh,
so we use sedium-native, like,
basically, which will, uh,
which will call the native sedium library in, um,
in your server, uh,
I mean, in our server,
and, uh, as we have an open source license,
especially HEPL, which is,
as it tells us to, uh,
when we are providing a service to show what we do,
so we also, like,
ready for, to the community,
as a cryptographic plugin,
I mean, as a plugin on, uh, on our GitHub.
And if you have an instance,
and you meet this kind of scalability issues,
like, there's actually a blockpost tutorial on it.
Uh, and don't worry, like,
the slides are already on, uh,
on the first-name website.
Yes.
It's divided by two of the CPU, uh,
yeah.
Yeah.
Yeah. So, as we were saying,
like, we divided by two of the CPU's edge,
on the server, with this,
simply with, with, by changing this.
Uh, but yeah,
if you have a, uh, a smaller instance,
it may not be, uh,
like, very useful.
But, yeah, for us,
we have a big instance.
I will show you some figures at the end,
about the use of crypt.
Uh, also, uh,
we also added, like, some, uh,
monitoring plugin,
because, I said,
we have, uh, we have some figures,
and before that,
it was mostly log analysis.
But, uh,
we needed, like, some more fine-drained, uh,
like, measurements,
especially, like, for, um,
on your, different actions.
Why not,
leaking,
and, uh,
we'll just be, like, counting,
for instance, how many times you,
how many times,
for instance, you will download an image,
which can be useful for us.
And, uh,
actually, this way,
you know,
you don't have a good example,
because you can also have it with
log analysis, but yeah.
Like, for more,
more fine-drained,
uh,
monitoring.
And so,
we hope, uh,
we hope in the future that it will help us,
like, uh,
understand more,
how people are using cryptat,
because we have our,
our own idea of what cryptat is.
We are also, like,
we are, like,
obviously a lot of people in,
uh, I mean, in the tech industry,
and so we may not know how people will use
our product in the real world,
because then we just, uh,
like,
give it,
for people to use.
So, yeah,
that's the thing.
And, uh,
the main point will be, uh,
to monitor the usage,
uh,
the data usage for,
I mean,
to have a data that we can use on graph,
and, uh,
to be,
which is,
also,
one thing that can be nice for,
uh,
different,
companies will be,
some single,
some plugin,
uh,
actually,
dates from last year,
but there have been some,
uh,
improvements,
improvements on it.
And, uh,
we can use,
uh,
the main main,
main SSO system,
like,
YTC and,
and you can have both,
actually, if you want,
can have many single sign-on systems on a single instance.
And it's kind of important for organization.
And we also added something that was requested
is like SSO login, I mean, restriction,
I mean, login on Lydia, single sign-on.
And also you can add on top of it,
like also your own password in order to keep your data
really private.
And as I said, like we have some scalability issues.
And one way to address this was, I mean,
was to develop a new server prototype,
which is distributed actually,
because right now, our server is really,
is a single server, I mean,
have to be running on a single machine.
Also call that to be run on a single machine.
So yes, so this is something I actually led last year.
And so it's an independent prototype for the main code base.
And we hope to integrate it at some point.
It's still very exploratory.
We just started having our different components,
and have them communicate one to each other.
So results are quite encouraging, but we hope to finish it
and include it in a real server and have this,
but I mean, maybe done with this bottleneck.
And I have something that will be scalable in the future.
One other thing that I've been done this year,
I've been end-to-end testing with end-to-end testing
with Sprite.
So there is a repository that is available on GitHub.
And we use Sprite to have some automated end-to-end testing.
So basically, simulating real world actions.
There is also integration with browser stack
for different, I mean, to be used on different platforms.
And also test, accessibility with it with X Core framework.
And there are about 300 tests to check
like breaking changes before releases, before each release.
And actually, some bugs were discovered with automated tested testing.
We also, I mean, you also saw that there were some tests that didn't pass.
I mean, in the previous screenshot, it was not one of them.
But actually, there are also some issues that we integrate in the end-to-end,
in the test and giant wing.
In the test suit, to that we also know, like when we are solving some issues,
sometimes we say the effects we can solve those or bugs.
And we also have dedicated testing sense for the releases for that.
And one thing that people have asked a lot is client-side API.
Because basically, the thing that has everything is end-to-end cryptid,
is we provide the web application, and that's basically all we are providing.
It's hard to use in other context.
Actually, it's not a server-side API, which would be really nice to have,
which will, for instance, allow us to connect our calendar to other applications,
because right now we cannot.
But here it's a client-side API, which allows you to use
as a synchronization tool, like elsewhere.
And the goal is to use, I mean, to have an end-to-end cryptid editor,
without any data processing sense that you can use in other contexts.
And we also have an integration, which next cloud was your project for this.
And so that was what was new on the crypto development part.
And now I will tell you a bit about our many instance, and how we are managing it.
So basically, the thing that we had some locality of service issue at the beginning of last year,
our server was like crashing or like very low, I mean, slow to answer.
And so that's what I said with our scalability issues and everything.
And the thing that what we did, we did the object thing, like, is to give more resources to put more resources in it.
But it won't solve the issue in the long term.
And so there have been also, like, this crypto collaboration change to solve this.
And we also change the file system we use, because actually, in crypto, our database, our database,
is the file system.
And so it's really dependent on the performance of the file system.
So before that, we had a BTRFS, and we had issues with it, especially.
And so now we move to the interface and the data access is also faster.
And only in all, like, it makes crypto, like more reliable nowadays.
And the crypto ad part, we also introduced, like, crypto cloud at the end of last year,
which basically allows you, I mean, which is a form, a form that will allows you to create a cloud demo instance,
like simply like with some clicks create on the crypto ad cloud, I mean, a subdomain of a crypto ad cloud,
create a crypto ad instance.
And then explore, like, the different, I mean, the administrative part of crypto ad,
and the crypto cloud features, if you want to trade, you can go and
crypto ad.org it at the bottom of the page.
And then customizes, as you need, I mean, for your needs, because, for instance,
you may want, like, when, for your association, or for your company,
and it can be a way to create it, like, easily.
And have, like, I mean, that we will, we will all, we will all sit, but as an independent instance,
and as part of crypto ad.fr, and, yeah, and the thing in the, you can manage your own instance,
which we saw else as well, if you have a page instance.
And on the usage statistic part, like I said before, I will give you, like, some insight.
The thing that, like, we have on the crypto ad, for instance,
like, basically six, six point five thousand people, like,
registering, like, every month on a crypto ad.
And the bad activities actually, how many times, I mean, one productivity is
counted when you open a pad, or created or created one.
And so, basically there is, there is one million pads open per month.
But to give you an idea of how much traffic we have to handle.
Yeah, no, yeah.
We don't know for the other instances.
Yes, it's only for crypto ad.fr, is the instance we are managing.
And also, like, in terms of, unique IP addresses, it's not exactly how many people,
but it gives a real idea.
We also had, like, 20 more, percent of people using crypto ad per month.
And all the figures are actually, like, mostly average.
So, when the end lecture is, like, something like this,
seven thousand people, like, I mean, new registrations last year,
for free account.
And one other thing that is kind of, like, funny to look, like,
doesn't give a lot of information, but it's kind of interesting.
So, most of our users are actually from the United States, like, more than a quarter,
and a little bit less.
I mean, and with Germany, it's, like, exactly half of our users.
Different of that, it was, uh, many Germany, but yeah.
And actually, as you, I mean, I, for the say, but crypto ad,
of the crypto ad.fr is, from a French company.
And actually, there is only seven percent of people from France using it.
And, uh, yeah, that, uh, kind of interesting.
I think that the first word is related to the fact that many thought
exit in all that need to.
But, uh, it may be possible, because we are only, uh, I mean,
we only analyze, uh, IP addresses and GUIP, so.
Ah, yes, sorry.
Uh, the question is, like, was that, uh, do I think that it may be
related to the, to the tour nodes?
I mean, exit node distributions, and, uh, my answer is, like,
it's, maybe possible, because we,
I mean, we don't have that many data to analyze.
So yeah.
It's a possibility.
Uh, and now for the funding, uh, status of crypto, uh,
uh, a neat question.
Uh, so, we have a transparent management, so, like,
actually, we just published, I mean,
Ludovic here, uh, wrote, uh, the funding status, uh,
uh, of last year, which is on our blog.
And, uh, to summarize it, basically, we have medium-term financing,
with, with our products, uh, which gives us,
basically, two, three years, uh, of safety.
Uh, however, it's on research projects, and then it's also
have the, I mean, I mean, it's not really,
we cannot choose it as we want.
It's really, like, oriented.
Uh, and I think that we don't, uh, achieve sustainability.
So, as I said, like, we, we had, um, two, I mean,
24,000 new accounts.
Basically, we rich these years, uh,
270K.
I mean, 270,000 accounts, like free, uh,
uh, registered.
But in the end, we rich.
And Wednesday, the 10,000 paid subscription and crypto.
Yeah.
So, thousands, sorry.
There's a 1,000 subscription and crypto.
So, you can see that it's not, uh, a very good, uh,
conversion ratio, but, uh, right, but yeah.
We need, like, basically, uh, more independent revenue streams.
We also have donations, like, for different, uh,
uh, the natals on open collectives.
And I said, like, uh, we, we have, we have many different products,
like funded by VPA friends, that is, uh,
which is our major, main, medium-term financing, uh, financing.
Uh, we also receive, like, uh,
money from NNAT and NJ, NJ zero and,
more generic NJ.
And, uh, your, your opinion as well, but, uh, yeah.
We're not, uh, we don't know how we, how we will go,
but, uh, if you want to learn more about it,
actually there is, there will be a talk from Ludo at 10, 30 tomorrow.
Um, in the first funding, uh, room.
And, uh, so, basically, to compute.
Uh, so the crypto project, I mean,
the progress on, uh, many different fronts.
We, we had, like, progress in, uh,
different, different fronts and, uh, which are kind of, um,
I mean, which are important, like, accessibility,
which is, uh, really important.
We want to, make it, I mean,
basically, uh, our main point is not to give,
I mean, our main point is to give something that people can use.
I mean, everyone can use, uh,
uh, while knowing that behind it's secure.
So UX is really, uh, is really important here.
And, uh, we had, we had improvement on, uh, UX UI on this, uh,
we had improvement on UX UI and also some back-end improvements
that you won't feel like directly, but,
that we had to do to make it still usable,
at least on crypto.fr.
And, uh, so I also like new plugins for the crypto ecosystem.
We hope to have more in the future.
And it can be used, like, that you can install as a server
depending on your needs.
So if you need SSD, you can install the SSD plugin,
but it's not there by default.
And, uh, and, uh, on the product side,
then, uh, we have, like, like,
as you see that there is, like,
20, 30% growth and, uh,
crypto that they further are more and more people using it.
We hope that it will, um,
okay, continue.
And actually, for the thousand people, uh,
there will be, um,
there will be a promotion, uh,
promotion could, uh, next week, I guess.
So stay in touch.
And, uh, if you want to have your own crypto instance,
you can also try, I mean, we can also use a crypto cloud if you want.
And, uh, for the next steps, um,
so here is a QR code for the roadmap.
And, actually, if you go on the slides, uh,
online, uh, those are applicable.
If you don't have to scan them, try to open the link.
Um,
so, uh, we, there will be some works on, uh,
first content, uh, integration.
So what it means that we want to have,
like, something like, that is more crypto agile.
And, uh, where basically we can go,
I mean, we can have hybrid encryption.
So meaning that we will have,
we will encrypt with the first one term.
I mean, a quantum secure, um,
an encryption and, uh,
layered with, um,
classical, I mean, uh,
standard one, one of the standard, I mean,
what we have today, um,
actually it's not free encryption,
if we be signature that is, uh,
the most important in our case, but, uh,
uh, yeah.
Uh, so there will be works on it, uh,
this, uh, this summer with, uh,
an intern.
We will continue as well the efforts and
accessibility that is ongoing and, uh,
mobile usage.
Uh, we also, like,
will have an other focus on the quality of life
improvements, so I,
uh, if you are using Crippad here and,
you need, like, more improvements,
don't hesitate to contact us and ask
thing we will, uh,
take it into account.
Uh, there was also one of the things
that have to be done this year.
I mean,
the replacement of, uh,
sick a little four,
which, uh, end of life was, uh,
was less, uh,
last year, uh, not 25.
Yeah, one point five years ago, uh,
for, which takes addition.
I mean, we may replace with, uh,
something between it in the world map.
And also, I said, like, the only of this upgrade.
And so, all of this is, uh,
is provided by you, uh,
uh, from, I mean,
by the Crippad team, which I said is, uh,
made of, like,
10 people, uh,
and, uh, so yeah.
Thank you for, for your attention and
if you have questions, uh,
I think we have, like, eight minutes or something.
Thank you.
So we have, uh, questions.
I think.
Let's consider a case when, uh,
a few users, let's say three users are collaborating
on a document at the same time,
changing one paragraph of text.
So, uh,
conflicts between their changes are,
likely, yes.
And more or, on top of that,
uh, some users may have network issues,
and their updates are coming with a delay.
Uh, do you handle such cases because,
in an end-to-end encrypted setup,
it may be quite tricky.
Yeah.
Actually, uh,
here's a trick,
a trick as part will be, uh,
a network issue, uh,
because actually the thing that, uh,
uh, we are doing it, like,
we are sending the patches, like,
in a very, I mean,
very small patches, like,
it would be one to three letters, like,
as you type and, uh,
something like,
three, four hundred,
and a second delay.
So, there will be, like,
three small patches,
but then when you say that, uh,
so usually when you are working on the same paragraph,
and it's also real time,
and you see the curve sort of,
other people.
So usually you see,
when you are going to create a conflict,
uh, and as the patches are really small,
they won't be that many conflicts.
However, when there is, um,
a network issue,
and as you said,
there are editing the same paragraph,
so there is a probability that there are editing the same thing,
uh,
then basically I think what will happen,
I mean,
what will mostly happen,
uh,
that the people who will have a good connection
will continue editing their things,
and, uh,
it will create a,
a brand, I mean, a fork there,
which will be small,
and our conflict resolution in this context
will be taking the longest branch.
So basically,
the smallest branch will disappear,
but then when the person will have that connection,
we'll come back,
I mean,
they will see that,
it just, uh,
disappear.
Yeah.
Um,
considering the legal topic to GDPR,
do I get it right,
that derived by zero knowledge,
architecture,
it is not necessary for your customers
to have a data processing agreement with you,
or is this necessary,
if I use this in a business environment?
Oh, this, I don't know.
Frankly,
um,
not sure.
So,
this is,
it would be nice that the GDPR says,
if you're really making data impossible to,
to be seen or to be,
then you would need it,
but I,
I don't really think that it completely,
waves the need for a DPA.
Uh,
and we do provide DPAs,
only for,
um,
uh,
25 user subscriptions at 500 year,
so if a school or something like that wants a DPA
to be fully compliant with GDPR,
they can get it on Crip at a far,
uh,
at 500 year year,
or 1000 year dependent on the number of users.
Uh,
but we don't provide it for individual accounts,
because it's just,
it's a,
it's a huge paperwork.
We have to sign,
we have to sign documents and stuff like that,
and we don't want to sign something just for free,
or for five years,
because we also need some revenue.
So that's the difficulty.
So I was very,
I went very entested by Crip,
but there is two limitations,
or problems for me,
or for the organization.
The first one is the,
two block of tax of,
right panel,
left panel on the screen.
I have,
uh,
I tried to have a full screen,
but I don't,
uh,
succeed in that.
So,
it was for me,
very important,
and that's cloud.
Next up,
only of this much better,
but it need,
a several,
uh,
framework,
and so that,
Crip,
but for me,
for me,
it's a good alternative to Google
workspace.
It's not safe,
not for user friendly,
and so on.
Uh,
and so the other problem is the,
lack of,
uh,
guest mode,
not every day,
to have temporarily access
for other people,
very,
uh,
easy,
not,
complicated tools,
only to test,
or to drive,
prepats,
so,
and so,
I have not discovered this kind of thing.
And so,
okay.
So,
thank you for,
you're interesting,
repeat and,
you're,
what you want about the UAUX.
Uh,
actually,
I don't,
it's a possibility,
possibility for,
uh,
other people,
so to test,
if it is convenient for them,
but temporarily,
it's possible with,
next cloud,
this kind of thing,
and we,
after,
uh,
the given date,
it is,
the,
this facility is shipwessed.
So,
uh,
it will be good to have this kind of thing.
Okay,
because,
actually,
I think,
it's very easy to test,
you can go to prepare the far,
you can create a document in two clicks,
you can create the document with any of the pads,
you can create an account,
so it's actually very simple to test,
so,
but for,
anybody,
you can do,
and you can share the document with anybody.
I mean,
even if you pay an account,
you can actually share with any people,
they don't have to pay.
Uh,
so,
you can actually,
test very easily.
For my point of view,
you can test more easily than next cloud,
where you have to install the server,
and so on.
If you want to test,
if you want to test,
like an enterprise or an organization,
to test the full instance,
a credit cloud has been made for that,
so we launched it in December,
and you can create an instance and test it for,
for,
for 10 days,
and,
and see,
what it would mean to run an instance,
if it was inside your company.
How practical is it to self-host such a solution?
I mean,
as an organization,
I would probably like to have an access to all the documents,
internal,
organizational documents,
or,
isn't it always the case?
I mean,
let's say,
some,
my employees share some document between themselves,
but me as an administrator,
I can't see it, right?
No.
So,
what if,
the access to this document is lost,
how to restore it,
for example,
what are the real use case for,
for the self-hosting setup?
Okay,
so,
I think there are many questions in one question.
So,
first thing,
for organization,
we have something,
which is called Teams,
where you need,
like some,
team administrator,
and like,
everyone in,
you,
organization,
you need it,
and so that like,
the files will be shared by,
with all the people,
like,
which are part of the team.
So, on this side,
it's,
okay,
then the thing that,
like,
for losing access to a file,
it's,
I mean,
it's basically stored in your drive,
or in your team drive,
like some,
so it,
shouldn't be that,
I mean,
it should be complicated,
like, to lose access to it,
but it's still possible.
But, you know,
if you really lose access to a file,
and you lose the keys,
you're a browser story,
which is one way to find,
your data,
and then,
yeah,
you cannot do much,
that's,
well, the thing.
I said,
like, one of the limitations,
like,
when you lose your password,
you're,
basically,
then, and, like,
uh,
thank you very much,
the police.
Thanks.
And thanks, you all.
Thank you.