Ugh, I really tried to stay out of #fediverse drama but I guess I have to say a few things. Most of you know me as a #firefish core team member, so I think I owe it to the admins of almost 500 firefish servers out there and to the almost 5000 members of firefish.social.
So, yeah, if you haven't noticed, things aren't looking good for firefish. Its owner, Kainoa, has practically abandoned the project, which had its last stable release out on July. My last message to them was a week ago, and I haven't heard back since. Firefish.social, besides the other severe technical problems it's had due to mismanagement in the last few months, now also has serious federation issues. I hope Kainoa is well irl, but this is irresponsible and unacceptable.
I hear some of you saying "but you're in the core team too, don't try to put the blame elsewhere!". So I have to explain what being a core team member in firefish meant. Kainoa invited me, Namekuji and a few others to be part of the "core team", but kept all decisions and responsibilities. We didn't co-own this. We never shared donations. We were just volunteers, who were honestly trying to make it a great project. This didn't work well due to concentration of power to one person, who didn't keep their promises. I don't mean to be harsh to Kainoa, I mean we knew they were only 19 when they started the project. Still, it's a bummer to anyone who chose to trust and support Firefish. This includes myself.
I don't know if it's early to consider firefish a dead project, but it sure seems like that for a few months now. Maybe it can be resurrected, idk. It's all up to Kainoa.
In the meantime, Namekuji and I are starting #Catodon, which will have some differences with Firefish, and will include many changes I had discussed with Kainoa but were never implemented. If you decide to stick with us, we promise to be serious about this. I strongly believe in the fediverse and its potential, and I want to build a great platform for it. This was my goal when I chose to be involved in Calckey/Firefish. It's still my goal with Catodon, only this time I can stand behind it 100%, as the project will be co-managed by Namekuji and me. If Firefish left you with a bitter aftertaste, we hope we can build a better relationship and prove ourselves worthy of your trust. Catodon will go public in a matter of days, possibly even hours. We'll have more to say about its direction then.
In the meantime, I just wanted to share my apologies for any inconvenience regarding Firefish, as I'm still technically a core team member, whatever that means. But frankly, I tried so hard to make things go differently - but there's only so much you can do when it's someone else's project. I'm really sorry for how things went.
But this is not the end of the fedi journey for me. I'm super excited about the chance to do some things right this time with Catodon. Life goes on, I guess! Hope to see you soon on our #codeberg repo, so we can start a new creative adventure together =)
#Forgejo 1.20 is released. While we are porting some Codeberg changes and testing the migration, you can already experience the full potential at https://next.forgejo.org - hosted on Codeberg's infrastructure.
Join with your Codeberg account, let your team test-drive the new features, and report the problems you find before other #Codeberg usres experience them.
There’s a special circle of hell for the “This file contains ambigious Unicode characters” overlay on @Codeberg
No, it doesn’t, it uses proper curly quotes and other typographically-correct punctuation in comments and strings.
Thought we’d fixed this in Forgejo but apparently not?
Really making me not want to link to my source code on Codeberg and I don’t want to migrate elsewhere right now when everything else is working so well.
To whomever has launched a denial of service attack on Codeberg, an independent source code hosting cooperative, congratulations, you win at being a most exemplary douchebag (or douchebags, as the case may be).
#Codeberg would not be here without all the free time volunteers donate to our platform and to upstream projects. However, we can give our project a rocket boost with your help. We have compensated a small share of time for their work in #Forgejo, and we have seen immense progress we would waited long for.
Hat jemand eine Ahnung, wie #Codeberg#Pages im Zusammenhang mit #Strato funktioniert? Irgendwie will Strato nicht richtig auf Codeberg umleiten. #CNAME kann ich nicht nehmen, weil sonst mein E-Mail Server nicht mehr funktioniert, aber die zwei anderen Optionen aus der Dokumentation wollen irgendwie auch nicht funktionieren.
Hey Git experts, I'm thinking about moving to #Codeberg because I know Microsoft will scrape and steal everything on Github in the name of AI, if not soon, then eventually, and my question is, when I push and commit changes, how can I be sure it pushes to Codeberg and not Github, since I do have Github CLI installed, or does it push to where I pulled the repo from automatically? #Git
We will check issues on #Codeberg and bookmarked reports on the fediverse.
We should be able to publish a release of #Fedilab with bug fixes and enhancements in the coming days.
Is it possible to verify your #sourcehut repo in your #Mastodon profile like you can in your #Codeberg or #GitHub ??
I tried adding the usual link in my bio but nothing. It's not important TBH just thought I'd try.
I think that every user of software should have the right to report bugs without being forced to sign up for an account on a particular site and take a stance on page after page of clickthrough agreement.
I have no hope that corporate disservices such as Microsoft Github will ever address this, but maybe a benevolent actor like @Codeberg could allow guests to report issues, ask questions and comment without an account?