Won't "running function only once" also result in stale data?

once per dom event

maybe model this as a missionary flow for direct control? dom/on is the primitive we are unhappy with for nontrivial situations

I think what you want can be achieved with e/snapshot but it's definitely complicated and dumb

if it can't, I don't see why

will try the above. I wonder if because the value (`cell-ent`) in my case is a e/watch(ed) value electric would rerun even the missionary code

when I tried snapshot it resolved the repeated runs of the dom handler at the price of stale data

you can also snapshot higher, e.g. the whole vector passed to db/transact

finally boiled down this issue! https://github.com/hyperfiddle/electric/issues/64

it does look like a bug / unintended behavior to me

authentication strategies would be helpful for me

I know you’re focussed on back office apps but I was very impressed with the industrial robot demos and I’d be interested to hear about whether electric (especially with differential) is is still only suitable for back office things or if it might be suitable for more front-end / client-facing use cases

Optimistic updates, missionary documentation website

I’d second @U055PQH9R4M’s authentication request. That is not the sort of thing you want people to have to get right on their own, if it can be avoided.

Im interested in fine grained state construction and manipulation to do bret victor stuff. This is maybe less about the network if not doing multiplayer, but im interested to see strategies from electric context (ie, is an atom enough? Need something like electric datascript or rules engine, etc?)

I'm just getting started with this, and love the idea in the always-online scenario. I'm interested to hear more about the intermittent-online possibilities. I'm about to try out scenarios to see how losing connectivity is handled currently - I understand that there are upcoming plans for this - maybe more info on this would be of wider interest?

Late here, but yes, what about choppy wireless connectivity, is resiliency for this on par with regular frameworks, or is there some more automatically done for users?