Dealing with indexed resources that go offline

[joepio]

The error below is ocurring because a previously online resource has been removed:

It's showing, because the AtomicData.dev server has an external resource cached in its store, which no longer is online. The client gets the URL to this resource from AtomicData.dev, and then discovers that it does not exist over there.

There are various ways to prevent this kind of issue:

Use the /path endpoint as fallback / primary resolve mechanism

• see Fetching from /path proxy instead of source atomic-data-browser#28
• This is something the client needs to do
• Makes sure the server acts as a usable backup

Use IPFS for everything #66

Add a removeLocally endpoint

• Requires a manual action by the user

Let collections (and tpf queries) default to local resources only

• Is kind of what you expect to see, most of the time
• Maybe pass an optional parameter to TPF queries (external=true) to search through all items

Use incoming links / foreign keys updates

• When a resource is changed or removed, a message should be sent to all subscribers about this event. Incoming references / foreign keys #111