Today I’m making yet another variation of my witbier, this time with kweik and lemon balm.

Oh thanks, I’ll check it out.

I tried running the tgz a few months ago. It needed a shitload of deprecated python dependancies, I’m not well versed in python so after the 10th pip install I gave up.

Version 4 is unfortunately closed source and paid.

The way I feel it, and maybe I’ve got this wrong is that federation works in an outbound fashion. Every instance sends to all its federation “hey, this thing just happened on my side”.

But if an instance goes down and it becomes “incompatible” like what happened to us for the past week or so, I feel that everything that happened in the meantime got irremediably lost.

I think there should be a contingency plan if one instance goes down. Something proactive along the way of “hey, I was down, I haven’t heard from you since xxxx seconds, could you send me an update?” Depending on the activity and the timespan the could trigger massive amounts of data being sent and has the potential to be abused so safeguards should be put in place, but maybe that could be a solution. Keep the real-time exchanges as the primary method but have a full sync once in a while.

I think (hope) the slowdowns are less upgrade related and more massive uptick in activity related. But maybe I’m wrong.

Seriously tho. Wefwef is incredible. Every instance should install it and give the choice to its users between the two frontends. PLus it would solve the rate limitation problems as both would be hosted on the same server.

I use Mlem ATM and I like it but Wefwef is crazy good.