willemmerson

It's quite a big deal for people who have been told repeatedly "it's all in the head" by health professionals.

  Location: Newcastle-upon-Tyne, UK
  Remote: Yes
  Willing to relocate: No
  Technologies: Python, Django, React, Node, C, Espressif ESP32, IoT
  Résumé/CV: https://www.linkedin.com/in/will-emmerson-06962340/
  Email: [email protected]

I'm a full stack developer with over 12 years experience using Python/Django/PostgreSQL but also have many years in other areas such as frontend (HTML/CSS/Bootstrap/React), firmware development (ESP32/C), and infrastructure (Linux/Docker/AWS/GCP).

Try using literally any other embedded SDK and you'll realise that idf is actually a dream.

You might be right about scale, but web servers already handle huge amounts of websockets, and already have complicated pub/sub schemes - think about a chat room for instance. I am using Django Channels which lets you define groups that other channels can subscribe to, and I'm sure other web frameworks have similar things. It seems easier to use than MQTT topics because it's all there right inside your webapp and DB, not on a seperate MQTT broker, this is the main thing that's attracting me to the idea.

MQTT does solve this by storing messages on the broker but you can just store messages in your database instead and send them when the client connects, and personally I think this is easier.

So you're saying it's all psychological? If this is true, why are so many with ME/CFS/Long COVID responding so well to LDN? I have had ME/CFS for 25 years and also practised mindfulness and pacing all that time yet it did nothing, but when I took LDN it instantly worked.

I don't have anything intelligent to say about this but it's ALOT of fun making all the samples play at the same time - sort of like the HTML version of Ableton Live.

Could be me/cfs, the defining feature is unrefreshing sleep but also "crashing" after overexertion, usually a day later. As mentioned you should look at r/cfs. Many people with cfs like myself have found Low Dose Naltrexone (LDN) useful, but it's not widely known about.

It's not completely related but I've been thinking that having a router connected via wireguard might be a good way to do IoT deployments.

Generally IoT devices make an outbound connection to a server and use MQTTS for bi-directional data flow, because of the difficulty of inbound connections due to firewalls, NAT etc. But this has some downsides in that you have to run an MQTT server, each device is doing it's own TLS (which uses a lot of ram and increases firmware size on an ESP32), and MQTT doesn't really have end-to-end message confirmation.

It seems like a better way would be for each esp32 device to be in a wireshark network and to be running it's own HTTP webserver (which is easy to do with the SDK). Therefore any device can be sent a message from the server using a simple POST request to its ip address, and can send messages to the server using the servers HTTP api. It's much easier to test HTTP api's than mess about with MQTT, and individual devices don't need to do SSL because all data between the devices and server is encrypted by wireguard.

I suspect there's something I've overlooked, I think addressing individual devices could be difficult if you only know their IP addresses.