ghislainle

71 ms·

1. 1.▲
   by ghislainle 1y ago

   I do not remember all the details, but I think it was during the transition from MQTT 3.1 to 5.0. We only use 3.1 and the 5.0 code was not yet finished, emqtt had a hard coded a dependency with an old lib, which we wanted to upgrade. There
2. 2.▲
   by ghislainle 1y ago

   I want to add that the relay server is never handling any customer secrets (so a low value target), and we have techniques in place to reduce the probability of DoS (increase the cost to the attacker). So even if someone would be able to br
3. 3.▲
   by ghislainle 1y ago

   One criticism I have with elixir is the lack of typing (they are working on it now, but I have yet to use it). So yes, I think gleam would be nice. But when we started, it was not even version 0.1 (and I had not heard of it) I suppose we ca
4. 4.▲
   by ghislainle 1y ago

   We also use a fork of Tortoise, wrapped in some easier to integrate code (for our use case). At first, we used an erlang lib emqtt, but it was left unmaintained and then removed from github. We had to switch to something else. Not completel
5. 5.▲
   by ghislainle 1y ago

   Main developer here. We use MQTT a lot, it is really a central piece of our architecture, but Elixir brings a lot of benefits regarding the handling of many processes which are often loosely coupled. The BEAM and OTP offer a sane approach t