Sorry, I did take the time to appreciate how snappy the last update was, but I haven't been vocal about it.
I'm going to toggle a few switches and see what happens. Is it normal if I can't fetch a post through another instance (Firefish)? Is the federation still disabled?
Thanks in advance!
@Oceane We have indeed been optimising the speed of both the backend and UI, glad it is bearing fruit 😅
The other milestone we're working on is federation, for which we introduced 3 different settings: github.com/bonfire-networks/...
Currently federation is locked down on here while we optimise some more things (like limiting how many replies are automatically fetched in threads) and then we'll change it to on-demand.
@silmathoron @mayel @Oceane Yeah, it is definitely waaayyy better. Really nice job. I look forward to switching to this from mastadon once you get out of beta.
@versolalto @mayel @silmathoron Lol, it might happen very soon
@mayel @versolalto @silmathoron I'm not trying to speak on behalf of the Mastodon developers but there seems to be less and less bugs, that's an amazing job
Also if you were to add OpenBadges compat I'd want an “early investor” badge (y'know, “early social investor”)
@Oceane @mayel @versolalto @silmathoron, great idea - @dajb did some great work on thinking how open badges could work in a federated environment docs.google.com/presentation...
def something on our (not really short) list 😊
BTW when the instance is set to on-demand users can still lock down federation for themselves, and when federation is enabled they can set themselves to on-demand or disabled. This is currently the only exception to all admin settings being fully overridable by users [besides the more obvious ones in "instance configuration" such as instance name and max file upload size].
This is a bonfire demo instance for testing purposes
