[SubstackBridge] New Bridge
Might close #3951
Pull request artifacts
| Bridge | Context | Status |
|---|---|---|
| Substack | 1 untitled (pr) | ❌ Bridge returned error 403! (19762)❌ Type: CloudFlareException❌ Message: https://substack.com/api/v1/reader/posts/staff-picks resulted in 403 Forbidden <!DOCTYPE html><html lang="en-US"><head><title>Just a moment...</title><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta http-equiv="X-UA-C... |
last change: Friday 2024-02-09 11:07:08
Worked fine locally, not entirely sure how to proceed.
protected by cloud flare. will not work in public instances
If that's the situation, would you like me to close this Pull request? Otherwise, there's a risk of the user raising issues about this bridge once it's merged.
Moreover, is there an alternative method to notify the user about the possibility that this bridge might function in the self-hosted version or to conceal it from public instances?
im not sure. i guess if bridge is useful for private instances it can be merged.
a better name for this bridge SubstackTrending?