WEBVTT

00:00.000 --> 00:26.000
Thank you very much to having me here again, so who am I, I'm a Floss enthusiast from Berlin,

00:26.000 --> 00:36.560
and I'm on the 31st since 2008. I'm one of the last very laconicats. I am in a friendica

00:36.560 --> 00:42.880
core development team since around 2010 when I thought about setting up the aspirin and

00:42.880 --> 00:49.520
pay it miserably, but then discovered that the friendica's software stack is that easy

00:49.520 --> 00:59.040
that even I would manage to use it. I funded the Berlin 31st meet-ups 2012 or something, and

00:59.840 --> 01:07.600
some 10 years later we started to think about organizing a conference in Berlin, and we will have

01:07.600 --> 01:15.680
this third, third day in Berlin this year. And in my day drop, I'm a system administrator at the

01:15.680 --> 01:24.720
Free Software Foundation Europe, which happens to be the 25th time at Boston, and it happens to be

01:24.720 --> 01:37.440
also the 25th year for the Free Software Foundation Europe. If you like the fight for software

01:37.520 --> 01:44.160
freedom in Europe and want to support us, it would be a shame, if effort if you would not get

01:44.160 --> 01:51.200
at least 25 new supporters. If you are not yet supporting, please get in that QR code and

01:52.560 --> 02:06.960
get a badge. Yes, we would set that up. So what is friendica? Many people compare friendica with

02:06.960 --> 02:16.560
Facebook, being the Facebook alternatives on the Fediverse, and we started to be set back in 2010.

02:16.560 --> 02:23.360
I deleted my Facebook account in 2012. I have no clue what Facebook is looking at the moment,

02:23.360 --> 02:31.200
so if you say so, I'm happy with that. I cannot really drop. What we are is a decentralized social

02:31.280 --> 02:37.600
communications platform linking to other independent social networks like the Fediverse,

02:37.600 --> 02:45.840
but also to some corporate services like Tumblr, BlueSky, we have X integration,

02:45.840 --> 02:54.880
and we even had Facebook integration when it was still possible. We have a nice homepage, we have

02:54.960 --> 03:00.400
lit our code identity between GitHub and our own self-hosted,

03:02.080 --> 03:12.720
get instance, we are running on PHP, 7.4 up to 8.5. It's basically that you're an old stable

03:12.720 --> 03:22.320
most of the time, that we are still supporting and you need MariaDB. And yeah, if you haven't seen

03:22.320 --> 03:29.440
my talk from last year, please scan that other QR code, you will land up on that page and

03:29.440 --> 03:36.480
can rewatch the entire presentation there. The other question, who is friendica? It's a relatively

03:36.480 --> 03:44.160
small team, so Mike Nagov and started friendica 2010, and then the next four persons are basically

03:44.160 --> 03:50.160
the core development team, that is me, that is Mike Kerl who sits back there, so if you have any

03:50.160 --> 03:58.240
technical questions, he has to answer that for you. People like and Philip are mostly

03:58.240 --> 04:07.760
back in the back end, and over the last year, Markos and Arthur joined working on front end and

04:07.760 --> 04:15.440
back end stuff, and I'm really happy that they joined, but not only they joined, but in total

04:15.440 --> 04:24.480
some 20 new people arrived on the credits file, which I just regenerated, and if you have seen

04:24.480 --> 04:30.640
the last year's talk, you know that slide already, and the only new addition is the last line,

04:30.640 --> 04:40.080
because 2025 we didn't have any release, and that didn't just make flux the confused. Many

04:40.160 --> 04:58.640
people ask what's going on, and see images too large, I don't know, there it is, so what's going

04:58.640 --> 05:08.560
on my day time drop correlated with experiences on my little home server with kind of

05:09.520 --> 05:20.080
dedosing many services that I'm hardly maintaining, there were a lot of LLM scraping swarms,

05:20.080 --> 05:28.080
harvesting everything, and they did not only harvest data, they also drained a lot of motivation

05:28.080 --> 05:35.840
to just turn off on the computer, so I spent many days not looking on my computer,

05:36.320 --> 05:44.320
and now the next image is not showing up, great. There it is, but I was helping many people

05:44.320 --> 05:51.680
to use their old hardware, just a little bit longer by just replacing the one operation system

05:51.680 --> 05:58.800
by another operation system, because Microsoft decided to end this support for Windows 10,

05:58.880 --> 06:07.120
and many people got annoyed to have to get a new one, so in Berlin we ended up with a bunch

06:07.120 --> 06:24.000
of workshops, with a gold-old Linususau party. I see you, there it is, and then the

06:24.160 --> 06:31.760
Fediver's diplomatic costs called and asked me to do something like a presentation and workshop

06:31.760 --> 06:38.880
every month or so about the Fediver's, so I ended up spending the rest of my time for that kind of

06:38.880 --> 06:48.800
stuff, and Zandra already told you so earlier today, we need more people doing outreach for the

06:48.800 --> 07:00.640
Fediver's, yes, and it's not only giving talks and conferences, it's just like tell,

07:00.640 --> 07:07.120
I've seen something interesting on the Fediver's, just keep it in the mouth, talk about the Fediver's,

07:07.120 --> 07:13.120
and people will ask you, hey, and what is it Fediver's thing you are talking about, and then you

07:13.200 --> 07:21.840
can tell them the story of decentralized social network. Okay, other people like Michael and the

07:21.840 --> 07:30.880
other contributors, where active, working on friendica, putting things together, and I managed,

07:30.880 --> 07:37.760
saying to force them, saying to you guys, to inviting me, to have a release ready for force.

07:37.760 --> 07:45.520
So, in the last year, we got improvements for the front end, mostly in the freeer scheme.

07:45.520 --> 07:52.640
We also improved the screen reader compatibility, and we improved our mustardon compatible

07:52.640 --> 08:03.520
API, so you can use almost any mustardon client with friendica and be happy. We overhold the embedding

08:03.520 --> 08:12.400
stuff of things people post elsewhere, so that it's now actually working, and we also overhold

08:12.400 --> 08:18.480
the add-on integration stuff, so should you have written an add-on for friendica,

08:19.440 --> 08:25.040
and it's not in the main repository for add-ons, and you might need to update your code.

08:26.000 --> 08:35.680
We improved some of our supported steps, and as people always ask, hey, you're the Facebook

08:35.680 --> 08:44.640
on friend, the Fediver's right, where is the Facebook set, it's now back. So, it's based, the add-on,

08:44.640 --> 08:52.640
is based on conversations, I think, and we now finally have a website again. Thank you very much

08:52.640 --> 08:59.920
to all the contributors, new and old who made progress last year while I was fighting bots

08:59.920 --> 09:09.520
and stuff. Most important for me, the most important feature for me was already introduced in

09:09.520 --> 09:17.760
2020-3, which is user-defined algorithms. To be honest, I really hate if we are promoting the

09:17.760 --> 09:26.160
Fediver's as being a place without algorithms. I know what we mean with by that, I know that

09:26.160 --> 09:33.440
it's kind of true, but I really would love to see more places where people can define their

09:33.440 --> 09:45.600
own algorithms to sort the view on timelines, and Michael spent a lot of time into improving

09:45.600 --> 09:55.360
our channel feature, and improving the performance of that feature. So, it's just brilliantly past,

09:55.360 --> 10:04.640
I think on my Raspberry Home server, the channel view loads into seconds or something, which initially

10:04.640 --> 10:14.880
took something like 30 seconds and you had to wait to see postings in them. So, 26, what

10:15.600 --> 10:23.280
are we planning to do? Well, actually, Frenica does not really plan anything, so the sky

10:23.280 --> 10:31.360
is a limit, and we will see at the end of the year. But we want to make it really easy for

10:31.360 --> 10:39.120
node admins to import the server block lists by ifters, because I think they do a really great

10:39.200 --> 10:48.000
job there. I'm so sorry that you had just a couple of years to early. I really hope that we get

10:48.000 --> 10:57.360
ifters and Frens of ifters running again. Michael wants to do into blue sky integration just a

10:57.360 --> 11:07.920
little bit more than we actually do already. We want to have more improvements for the accessibility

11:08.000 --> 11:16.240
of Frenica, and during doing the release, we realized that parts of our tool chain

11:17.120 --> 11:24.560
need maybe some switching, so that will be something happening in the background, and I promise

11:24.560 --> 11:34.240
that there will be more releases than last year. If you want to get involved, just do. We are

11:34.320 --> 11:41.040
pretty open. The core developers are really friendly and really helpful, and spend a lot of time

11:41.040 --> 11:50.160
explaining why we did something the way we did. In the repositories, we have attacked for

11:52.160 --> 12:01.360
issues that look easy to join us. I love to see more translations of Frenica. I love to see

12:02.000 --> 12:11.120
more people working on this small address of our web front end. I like to see more people working

12:11.120 --> 12:18.720
on the accessibility, and if you want to chat with us, we have three community chats that actually

12:18.720 --> 12:25.920
are one because they are bridged altogether, and the discussion either happens in the

12:26.400 --> 12:34.400
issue trackers or actually within Frenica because we have groups and people can join groups

12:34.400 --> 12:43.120
like the developers groups. So, save some dates, please. If you are remotely part of the

12:43.120 --> 12:52.080
Frenica community and you like Frens, let's meet tomorrow at two and go down to Frenica to get

12:52.080 --> 12:59.600
some fries. Then, an offspring in Germany, we have the headache hem, which is great, which is

12:59.600 --> 13:07.040
somewhere in the nowhere of West Germany. Living in Berlin, it's kind of a long travel, and we decided

13:07.040 --> 13:13.680
to, okay, we can fry that somewhere, nowhere somewhere in Brandenburg. So, let's, let's have a

13:13.680 --> 13:22.880
free, meet up at the seaside, and then early September, Zander already told you, we will have

13:22.880 --> 13:32.320
the third Berlin Frenica and the call for participation should be out and of February, early March,

13:33.040 --> 13:40.880
and we would like to see many of you people coming to Berlin joining the conference and contribute

13:41.040 --> 13:49.200
to that. Sure, that's it. I'm open for questions, and I guess you can grab

13:49.200 --> 14:03.200
Michael off afterwards outside as well. Great, thank you to this. Does anybody have any Frenica related

14:03.280 --> 14:14.960
questions or anything about how awesome Berlin is or just generally like? Really? Evan, Evan, Evan,

14:14.960 --> 14:24.240
maybe. So, I think one thing I want to ask is it is a code base that has

14:25.360 --> 14:31.120
held together the Fediverse for the last decade and a half, right? It's been the, the throughline,

14:32.080 --> 14:37.440
but you know, sometimes we say that that's that you get technical debt and legacy,

14:37.440 --> 14:45.120
how have you dealt with having such a mature code base over time as the Fediverse has changed?

14:47.280 --> 14:56.320
How do we deal with it? I guess we have an overhaul of most of the back end every three

14:56.400 --> 15:04.160
or four years or something. To just adopt new struggle against ahead and realizing

15:04.160 --> 15:09.920
what we did there ten years ago was really not the way we should have done that and let's just

15:09.920 --> 15:25.760
screw that all up and rework everything. So, now I start. So, I will admit that I am

15:25.840 --> 15:31.040
completely new to Frenica and I just know that it's a platform on the Fediverse and I have heard

15:31.040 --> 15:37.680
it being compared to Facebook, would you say that accurate comparison? Yes. I mean, I said in the

15:37.680 --> 15:44.720
beginning, I have deleted my Facebook account 2012, I don't really know how Facebook is looking

15:44.720 --> 15:52.960
nowadays, but we have events in Frenica, we have picture albums where you can share your galleries,

15:53.040 --> 16:03.840
we have AI slopes for users, generated advertising AI slope, is that in there? I want to make

16:03.840 --> 16:12.960
my move the seamless as possible. We can, I mean, we have add-ons, we can probably create an add-on

16:12.960 --> 16:32.240
for you to add AI generated advertisements. Just for you, Andy. Yes, yes, yes. I'm excited. I didn't

16:32.240 --> 16:36.400
spot that you just done a new release, so I'm excited to check out whether the instance that I

16:36.400 --> 16:40.560
have an account on has updated and that's really exciting so thank you for sharing it.

16:40.560 --> 16:45.360
All right, one more time, thank you so much to BS.

