@helene @meeper It's not in #PleromaFE? Weird.

I know it's in #PleromaBE because #Soapbox has always had it, before the creation of #SoapboxBE

@thatguyoverthere @dsfgs @batalanto

> Soapbox also makes a backend. This implies that it would be possible for a 3rd party to grab the code for both FE & BE (or maybe just the FE) and self-host it as a service to the public. In that case, then only the 3rd party is forced into CF’s walled garden. They can take a hit for the team. Probably not the general case though. Is anyone hosting Soapbox outside of CF?

I admit that I use fe.soapbox.pub as the FE for all the instances I use, since I thoroughly enjoy the #SoapboxFE experience. But my main acc ATM, social.teci.world, uses both the #SoapboxFE and #SoapboxBE, apparently doesn't use #Cloudflare, and I recommend it because it's usually as close to the latest #Soapbox commits without being on #Gleasonator. Since its a smaller instance, it's less blocked and you get a more complete view of the #Fediverse IIRC

@verita84 @thatonecalculator

> Pleroma is barely worked on and it's own creator abandoned the project for over a year so far.

Oh I'm referring to #Soapbox, not just #SoapboxFE. I get the impression that #SoapboxBE development is active.