do webRTC STUN servers require SSL?

On top of being ignoring the Linux community and the audio problem caused by their sheer incompetence to use WebRTC and Electron in order to support screen sharing, they now just sent me the whole damn thing again over the span of 2 hours.

This is why I won't pay for discord until they get their shit together.

Not to mention the disastrous android app update recently that still has unaddressed that make daily usage a pain...

Which is the easiest stack of languages to use in order to build a webRTC chat website with basic user account creation and sign in and a text chat alongside a video chat much like chat roulette? I’m thinking obviously html and css and JavaScript. But maybe golang on the back end? And I’m not too sure about the database. Any suggestions would be AMAZING. Thanxxx

For a side project I identified the need for RPC (originally over Websocket but can be extended to WebRTC/DTLS) that supports

- JSON-serializable values
- Promises
- MessagePorts (including shortcut detection for ports that are passed back on a different route)
- async functions

I have ideas for all of these and this is an exciting prospective library, but it's also major scope bloat that will prevent me from ever finishing the project that depends on it.

Would you be interested in such a library if it ever got built?

Building a webRTC website and I could desperately use some advice.

Just to preface im a total beginner at this so apologies if this is dumb but

I am building a p2p cam site using a TURN server. Should I rent two separate Dreamhost servers? One to house my website /webserver and a second to house my TURN server?
Is this possible ? Would Dreamhost server A be able to communicate with Dreamhost server B?

Also is it possible to migrate a dockerized TURN server to Dreamhost in the first place?

Consider an API that uses the HTTP path to represent position in a tree that literally represents a file tree with minimal constraints, and GET/PUT/DELETE methods to read, write and destroy the nodes. How would you encode read/write operations to per-node metadata? The kinds of metadata are static and around 4, so inventing HTTP verbs for each of them is infeasible but filtering is not necessary.

Options considered so far:
- toplevel resources alongside a namespaced /data such as /acl, /lock
- magic keywords to the Range header (this is apparently compliant)
- mimetypes such as text/plain+acl
- SETPROP / PROP methods in the spirit of WebDAV
- headers (I worry this may become an immitigable bottleneck really fast)

I'm looking for any kind of suggestion or insight, not perfect answers.

I read the WebDAV specification and I won't even suggest that I'm trying to align with it, the only protocol I'd seen in the past with comparable scope bloat is WebRTC.

Utility libraries, because I actually get to see my life improve because I have them. Creating new projects becomes easier because I put parts I reuse somewhere else.

There was an old config file generator/manager I kept using for a while, some string conversion libraries between formats, some REST/WebRTC API wrappers, I have a web audio API I create tunes with in various projects. CI/CD scripts for laziness so I never have to know how to set anything up again. Lately the thing I'm most happy about is I turned some free text saving service into a makeshift database and it's been working well for about half a dozen projects now. Wouldn't handle large amount of users but can't beat free and easy.

I also find merit in prototypes/old projects, because I can reference random things I did in them in newer unrelated projects. Things too small to warrant their own utility library, argh!