-
-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flatpak Maintainership: the future #4641
Comments
as of writing v5.1.0 has been merged into the repo, going forward this ideally should be the last release I'll work on. I'm willing to continue maintaining it until a suitable replacement maintainer is found |
By the way, Iceshrimp is a fork of Misskey? or a fork of Firefish? |
It is a fork of firefish |
Which Iceshrimp server are you using? I want to check it. |
It is a fork of firefish i'm using a single user instance social.nullrequest.com |
Can you please try 5.1.1? |
just going through the changes it looks like you've set the default instance for iceshrimp to be |
@Lunarequest Hi, I released the new version of Whalebird, 6.0.0. It doesn't contain better-sqlite, so will this make your job easier? |
Finally got some free time I'll update the flatpak. Like I said my time is slowly becoming more and more stretched and will be for the next few years. I will maintain this flatpak until someone is found to replace me or my other commitments become lessened(this is unlikely for a few years) |
Hi, it seems the flatpak version is now really outdated. |
I'm currently the maintainer of the whalebird desktop flatpak. I've had a lot of difficulty since the introduction of better-sqlite prebuilts as a dependency to keep the flatpak up to date. A update of the flatpak involves the following steps
with the recent update I can no longer do step 5. I run iceshrimp a fork of misskey with some of the best mastodon compact out there. v5.1.0 removed support for misskey and seems to have ensured any fork of misskey with mastodon api support will be considered misskey and it will refuse to connect.
This is the straw that broke the camels back for me. With work and such I already had very little time to ensure everything works. I feel it would be a disservice to users to publish software I no longer use and can no longer ensure works. Going forward someone needs to be found who is trusted and more involved upstream and can ensure that the flatpak is up to date.
The text was updated successfully, but these errors were encountered: