Michiel de Jong

See https://github.com/cs3org/OCM-API/issues/121#issuecomment-2333416021 for a draft of how this could look

I'll reword the section about discovery so that: * the fallback to SRV is only described in the context of 'Vanity OCM Addresses' * it is required to first try...

Code is working in development but merging this PR to main is still blocked on https://github.com/tosdr/edit.tosdr.org/issues/1186 since (we think) that would trigger a deploy to production - don't merge this...

superseded by #661

What we could do is pull in the schema from its URI during the build. That way it doesn't always have to be accessible at runtime, and doesn't need CORS...

opened https://github.com/remotestorage/modules/issues/36 in relation to this

The following deno test passes unless you comment out one of the commented lines: ```ts import BottleneckLight from "npm:bottleneck/light.js"; Deno.test("BottleneckLight", async () => { const limiter = new BottleneckLight(); //...

Even with `console.log('hi'); resolve(null);` in the `schedule` callback it fails intermittently, about 20% of the time on my laptop.

A pretty consistent workaround seems to be the following: ```ts import BottleneckLight from "npm:bottleneck/light.js"; Deno.test("BottleneckLight", async () => { const limiter = new BottleneckLight(); await new Promise((resolve) => limiter.schedule(() =>...

writing works now, but reading back does not.