tech.lgbt is one of the many independent Mastodon servers you can use to participate in the fediverse.
We welcome all marginalized identities. This Mastodon instance is generally for folks who are LGBTQIA+ and Allies with an interest in tech work, academics, or technology in general.

Server stats:

2.9K
active users

Public

#Tuba v0.9.0 is now available, with many new features and bug fixes!

✨ Highlights:
- Audio Visualizer
- Accent Colors and other GNOME 47 changes
- Focus Picker
- Account Suggestions for new accounts
- Scheduled & Draft Posts
- Hashtag extraction from posts
- Full emoji reaction support for supported backends
- FediWrapped
- Thread Muting
🧵

As always, there are too many changes to list here, if you're more interested, check out the full release changelog:
github.com/GeopJr/Tuba/release

Public

@Tuba as someone that rarely pays attention to gnome/gtk stuff, i gave the latest version of tuba a try and i'm very impressed!

feel free to reach out if you're interested in supporting our bubble timeline implementation :)

@esm :dragnheart:

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.