facebook VS hedera-sdk-go

My Facebook bridge constantly locks up my account. [1]

[1] https://github.com/mautrix/facebook/issues/236

Sure, I use this bridge (https://github.com/mautrix/facebook) to bridge synapse server to my facebook account, so I can use facebook messenger through my synapse server. I like it mainly so I don't have to install facebook messenger on my phone.

It's unrelated, except for the fact that I used the reverse engineering of the facebook messenger protocol by the mautrix team. [1]

I may add a "matrix plugin" [2] if I feel like it someday, but probably after I implement group chat support. Then you'll be able to use XMPP<->Matrix<->some-other-thing for extra over-engineering points. ;)

I prefer XMPP because it's lighter on resources, server-wise at least, and it's managed through a democratic process, which has it upsides and downsides. As someone I like said "democracy is boring, dictatorship works faster".

[1] https://github.com/mautrix/facebook

There exists a Matrix-Facebook bridge, but unfortunately it requires a home server to run it and many people can't afford that.

I've recently set up a synapse instance on my home server using the official docker image, and a mautrix-facebook bridge also using docker. So far it's all working great! However, I've had issues setting up mautrix-whatsapp: when I follow the setup instructions on the GitHub I get the following error:

like this?

The bridges can get a little more complicated, here's the facebook setup instructions for python, but if that's too much for you then I'd reconsider beeper (p.s. they said thanks for the feedback on the sign-up form). I don't know anything about their payment options, but I know that you can always just use the Element chat client, available for web, android, ios, desktop in the usual stores.

I don't think this is a big deal, they outline the issue and the solution in the Github issue. Basically, they were storing data in a map (which is an unordered data structure) and then serializing (converting to a form for data transmission, e.g., JSON, XML, or in this case Protobuf) and getting different results at different executions. They needed to update the serialization process to be deterministic, i.e., produce the same output every time.