|
|
|
|
|
by 90minuteAPI
1939 days ago
|
|
Live-but-throttled is a decent compromise between the first two. Maybe something that submits a notification directly to you, as chance to approve/deny/respond, moderate what gets published, and be generally aware of what you’re publishing for that matter. |
|
- use edge workers to fetch and insert data as the page is being returned to the client
That would work in browsers with JS disabled.
You could also have client-side code to update with live data as it comes in.
The downside is that it’s not very portable code, but that’s the same for most serverless stuff, and it’s probably not that difficult to re-implement on another platform.