Espen Klem

Here is an app that is served over HTTP but is DAT at the core: https://olafchat.netlify.com/

I'll make something working here, but it will be simpler. So index still stored the same way as before. It's the data to index that will actually be distributed. And...

I think the norch-usecase for this is to have the full index searchable instantly and then use either replication to swap to a browser-based, or use DAT for the replication....

Just put it here, so people browsing would know that something will happen at a later stage =)

Yes, that was the old version running, it's updated now to the newest version of norch.

No, try once more now.

So, it's fixed for `search-index`, but not for `norch` before we get it to build with the newest version?

I love the indexing part of the stream API on search-index, but since we're talking about the server-side here, I don't think it's a problem. But maybe be able to...

Yes, sounds good to have `add` as the standard choice with easy-to-use arrays as input. Also have some [dirty tricks to parse streams](http://www.inbeta.no/) in the browser when querying a norch-instance....

Ah, nice! A little unclear issue. I was also thinking of when the post request comes from i.e. Zapier and I can only rely on the regular /add functionality. A...