Post
The thing is though, there are several projects for servers out there. As a decentralized FOSS project, you don't need to rely on one source for either servers nor clients.
I don't know anything about the protocol itself. I don't know if there's anything there that is fundamentally broken, but if it's an implementation issue, that can be fixed by others.
I use #FluffyChat for my client, and though I don't use it often, it is a fairly pleasant client to use I must say.
That, and it being too much trouble getting access from more than one device. Your account being deleted for not using it for a few months. Everytime I wanted to use it for something I had to sign up again.
And as you mention, the whole app experience.
I鈥檓 done too.
The thing is though, there are several projects for servers out there. As a decentralized FOSS project, you don't need to rely on one source for either servers nor clients.
I don't know anything about the protocol itself. I don't know if there's anything there that is fundamentally broken, but if it's an implementation issue, that can be fixed by others.
I use #FluffyChat for my client, and though I don't use it often, it is a fairly pleasant client to use I must say.
Will be interesting to see if #Sup is going to make any difference with this issue though, of finding a common way for the fediverse to communicate with instant messaging. But it'll still be years before we see the fruits of that initiative I think.
#Loops is still a broken mess, and they still need to maintain and expand Pixelfed. That's not a lot of time/resources for developing Sup.
A space for Bonfire maintainers and contributors to communicate
