I am going to limit my ladybird posts here (mainly because I think I might have an inkling of an idea for scribbling on a couple of the others) but I like this one because I think the wood can be misread as a rocky mountain, and if that were the case they ladybirds would be HUGE.
Me: Must not post all the photos of ladybirds. Must not post all the photos of ladybirds. Must not post all the photos of ladybirds. Must not post all the photos of ladybirds.
Also me: Maybe just this one.
(I like this one, it's like the other bug has had a paint job to fit in)
Things I unequivocally took too many photos of over the last couple of weeks (part one)
Ladybirds.
So, so, soooooo many ladybirds.
PS My apologies @nicktaylor, now that I've read more into Ladybird I see they're doing both. Creating a new browser and a new not-for-profit for it. I'll be intrigued to see how they plan to structure the org to avoid Mozilla's fate.
Also why they decided to start from scratch, instead of forking at least some components of a working libre browser. Even if only to swap them out over time, as Chromium did.
Me:
> Also why they decided to start from scratch, instead of forking at least some components of a working libre browser
Again, further reading has allowed me to answer my own question. SerenityOS was an itch-scratching project where the goal was to try out entirely new approaches. One of the reasons for spinning Ladybird into its own entity is to move away from that, and start making use of existing code where it makes sense.
"I love SerenityOS, and I love the community that has formed around it. I don’t want to hold it back anymore by being a distracted BDFL. This is why I’ve also decided to step down. Effective immediately, SerenityOS is now in the hands of its maintainer group. They’re a lovely bunch of people, and I trust they’ll take good care of it."
#AndreasKling, 2024
https://ladybird.org/posts/fork/
This is what servant leadership looks like.
(2/2)
@nicktaylor
> re: "From the ground up" - Ladybird is having a go
Awesome, thanks for the tip. @alcinnz has been developing a browser from scratch for a while.
But again, my question is focused on replacing Mozilla, as a coordination and funding scaffolding. FireFox could easily be hard forked if Mozilla is irrecoverable. The question is how to fund that properly, and how to set up governance to hedge against enshittification (eg a platform co-op owned by devs).
PS My apologies @nicktaylor, now that I've read more into Ladybird I see they're doing both. Creating a new browser and a new not-for-profit for it. I'll be intrigued to see how they plan to structure the org to avoid Mozilla's fate.
Also why they decided to start from scratch, instead of forking at least some components of a working libre browser. Even if only to swap them out over time, as Chromium did.
A space for Bonfire maintainers and contributors to communicate
