julian on Nostr: just clearing something up, Authorized Fetch is the Mastodon name for requiring HTTP ...
just clearing something up, Authorized Fetch is the Mastodon name for requiring HTTP Signatures for retrieving content, even public content.
However, you *already* did the hard work once to sort out http signatures for *publishing* content, sending one to retrieve content is trivial by comparison. It took me 5 minutes.
Right now the rationale behind using it is mainly about protecting publicly visible content from being consumed by blocked servers, which is actually a side effect of the feature. There's more potential in supporting it because it then allows fine-grained access over who gets to see a resource (think private groups, DMs, etc.)
However, you *already* did the hard work once to sort out http signatures for *publishing* content, sending one to retrieve content is trivial by comparison. It took me 5 minutes.
Right now the rationale behind using it is mainly about protecting publicly visible content from being consumed by blocked servers, which is actually a side effect of the feature. There's more potential in supporting it because it then allows fine-grained access over who gets to see a resource (think private groups, DMs, etc.)