Back

@pan we've had "portable" builds since February and id say it's... messy. I can probably write a blog post on it at some point, but I'd split it into 3 stages:

• Getting it to compile and work under msys2 (somewhat easy)
• Fix runtime issues (it gets hard based on your dependencies e.g. libsecret)
• Package it so it works outside msys (very hard, annoying and messy)

You need to collect all your dependencies, and their dependencies and their data files and every single icon ever and anything else related; all while making sure your msys installation doesn't interfere. After making sure it works, you try to automate the whole process, which ends up looking like this:

https://github.com/GeopJr/Tuba/blob/main/Makefile#L32-L79

(Notice how many times I blanket copy every single dependency another dependency might have)

Once you have the portable build, making an installer is pretty straightforward. You need a config for it and branding assets (but you'll end up on forum threads from 2006 only to learn that it accepts 24bit bmp3 files)

@macoud12 I haven't looked into it but it should be possible at least for the portable one!

@Tuba I mean, I can run it right now, it'd just be running using emulation instead of being native arm64 code.

@macoud12 it should be possible to build it for arm too! Msys2 provides arm builds of the libraries we use, it mostly needs updating the CI and packaging scripts from our side.

@Tuba Good to hear that!

@SynAck in a few hours. I updated the flatpak some time before I made this announcement and Flathub publishes them 3 or so hours after!

@Tuba Excellent! Really looking forward to trying out all the new features and fixes!

@esm

I mostly need some way (preferably from the instance endpoint) to know that it supports it (and it's not the akkoma one). It can be api_versions.chuckya, some other key that implies it (e.g. the existence of max_reactions implies that emoji reactions are supported) or even adding a features array like akkoma does.

Overall I've been avoiding enabling features based on nodeinfo or version hints and instead try to do feature detection.

Otherwise from my side I can probably assume that if api_versions.mastodon and max_reactions exist then the backend might support bubble timelines, and enable them after a request to the endpoint succeeds.

Or as another user suggested today for local only posting, add a switch in settings to enable bubble timelines manually.

The rest is already there, I'll only have to add a case for chuckya's endpoint vs the akkoma one and it can probably make it in a patch release.

@GeopJr i've gone ahead and added a chuckya api_version: https://github.com/TheEssem/mastodon/commit/f0453c6ddf2c0d112e945b01fffffd3c6ae51e19

let me know if you need anything else!

@esm Done from my side too! https://github.com/GeopJr/Tuba/pull/1285

@megalodon
https://www.youtube.com/watch?v=t7nONUOYiCI

@Tuba no baby shark :((

@megalodon REDEMPTION ARC!!

https://www.youtube.com/watch?v=gWT53moot-8