Caching should be handled by the proxy in front of your server in that case. Adding another host is unlikely to improve performance, especially with HTTP/2.
This uses the same control surfaces as a v-tail RC airplane ;-) . I built one like this, fairly simple controls using an aileron mix (as elevons) to combine the traditional aileron, elevator, and rudder controls. Note that you can find a lot of RC projects like this online under keywords like "RC flying wing plans".
Since the Microsoft Teams client is well known for being quite frankly, terrible, as many have pointed out in this thread, I am working on my own, alternative Teams client: OperCom.
I'm building it as a simple, vanilla JS web application, in a SaaS model (since I need to keep bending to Microsoft's will). The Teams API isn't great to reverse engineer, but it's do-able and has been done (partially) before, but never to the extent required to create a full-featured app.
If anybody's interested, you can see its current status at [1] and keep updated with its progress at [2].
Microsoft Graph requires the organisation administrator to enable extra user permissions or to add an app to allow users to use this, whereas by reverse engineering users don't need organisation administrator permission.
They do have a React version on WebView2 that is (supposedly) much better, but it's only for personal accounts right now, though that could change [1].
Thankfully their internal API is fairly self-documenting, so I've been looking into creating my own Teams client if you're interested [2]. We'll see if it'll have been an effort in vain depending on how well Microsoft Teams 2.0 goes.
“so I've been looking into creating my own Teams client if you're interested”
thanks for the link, looks good. styling and eye candy can be added later. first i think it just needs to be optimised for low memory and speed - not using react is a good step in this direction.
I agree that the client's performance is important. I'm hoping to avoid frameworks so that any issues will be as clear as possible, but maintenance will tell if that's a good decision.
Maintenance may be pita but the issue with using web specific ui frameworks for a desktop electron app is that web frameworks arent meant to be run for a long time. They take a lot of memory. One has to find the right balance between what to do in the renderer process (ideally nothing more but really basic css and js, maybe a web worker or two), and everything else in the main process.
I threat the main process as a backend api and use ipc as a broker between that and the ui. The renderer process does nothing but show text and icons. From that point on one can have fun with threads and all :-)
The "free SSL" meant adding your domain as a sub of theirs, i.e. https://yourdomain.namecheap.com. I fell for it and was pretty salty to see how much they charge and the lack of a letsencrypt integration.
An alternative Microsoft Teams client. It's cool because it doesn't warm your computer as the official client does. (https://www.opercom.co.uk/) the website needs a complete revamping and the UI is being changed to be more modern.
This certainly looks scary, but it's a bit difficult to understand right now even with their explanations, hopefully this bill will have more attention.
Avoid buying a GrapheneOS phone being advertised specifically for privacy with encrypted chat. They are specifically for selling to criminals, be it from a government or an enterprising young adult.
Many people have tried to pay me to make them a custom ROM based on GrapheneOS but with their name and reskinning notepads and encrypted chat apps. They'll claim it's for privacy-focused businesses of course.
