Open mjordan opened 2 years ago
The existing "private_shoulders" config option can already handle this use case.
Closing.
The main use case for private shoulders is to support offline content. larkm should check to see if a target starts with http
and if so attempt to resolve the request. If the target does not start with http
, the resource's info should be returned instead (i.e., larkm's response should be the same as if ?info
was requested).
The whole private shoulders functionality is not necessary at this time. I'm going to tag the issue_5 branch and remove that functionality from main until we have a use case for private shoulders.
Tag with_private_shoulder
at d04584a884fa061e81ba821c19a22975712f42f5 .
We will want to be able to use paths on non-publicly accessible storage, or offline storage, as "where" values. These ARKs should not be visible publicly. Probably the best way to enact logic to not show the metadata or to resolve for these ARKs is to reserve one or more shoulders for them.