I used Wondershare demo creator to create a RCF video in 2021 seemed ok to use at the time, I'm not a power video editor though

thanks Adrian 😄 will check it out now

https://www.loom.com/ is worth a look

Vimeo has a pretty good free recorder these days as well

currently represented as session id in my knowledge

in the examples^

ideally the access token is stored... clientside in browser storage, in header of every request? both?

tangentially related: i'm using tuple <timestamp, username> to derive a <userhash> and pass all three when the user does stuff. Probably a better way exists.

I was pretty sure that you can’t use headers with a websocket connection, and have to rely on a query-string or some other mechanism. How do you supply these headers?

I believe the session ID used in the examples is just the standard session ID attached to all websocket connections.

As far as I know, it is not possible to set headers on the WS UPGRADE request. Is it ok to pass your token as a query param? If no, then you need a two-step mechanism: 1. Issue a request to /set-token, a. pass your token as a header b. generate a unique id (e.g. uuid), c. store the pair (uid, token) into some hash-map i. ensures the pair is short-lived - clean it up after a few seconds (e.g. with a missionary task or make your map a TTL cache) d. return the uid 2. pass the UID as a query param in the WS connection url a. get the corresponding token from the map

In this case, a third party (Auth0) handles all the storage etc., so I literally only have to find a non-insane way to have the access-token travel along with the WS connection request.

But 2 assumes that I can manipulate *ws-server-url* in Electric. Is this supported?

Not in Electric, but you can rebind *ws-server-url* before calling hyperfiddle.electric/boot , so before the program starts.

oh that looks like a very elegant solution (!)

maybe you can write a blog post about how you achieve it

What about the cookie?

Not the kind of thing you want to leave hanging around in a cookie. It’ll go stale if your cookie lives longer than the access token it holds.

Yeah a dialed in Electric GPT would be amazing for helping with the minutia

https://clojurians.slack.com/archives/C7Q9GSHFV/p1699392001098329

I’m doing this:

(defn make-reactive-query [path pstate]
  (->> (m/observe
        (fn [!]
          ;; Init
          (! nil)
          (let [cp (r/foreign-proxy-async path pstate {:callback-fn (proxy-callback !)})]
            #(.close @cp))))
       (m/relieve {})))

thank you. and what is proxy-callback in your :callback-fn?

(my guess is, it's not needed if i'm observing the whole collection and not looking at diffs?)