Last-Modified and so the hit on a web server is minimal at best. -- And as you just found, _many_ clients don't yet actually even respect this field, only really yarnd does (I believe). -- And if you set it too big well then maybe nobody sees your post for a while 😅I would offer documentation on our use of the WebSub protocol, however this is not possible to implement for feed authors in _all_ cases, especially on multi-user hostrs like many of the tilde(s) I think... -- Is this something we _should_ document as an optional client feature? (I feel most feed authors probably wouldn't care all that much)
Last-Modified and so the hit on a web server is minimal at best. -- And as you just found, _many_ clients don't yet actually even respect this field, only really yarnd does (I believe). -- And if you set it too big well then maybe nobody sees your post for a while 😅I would offer documentation on our use of the WebSub protocol, however this is not possible to implement for feed authors in _all_ cases, especially on multi-user hostrs like many of the tilde(s) I think... -- Is this something we _should_ document as an optional client feature? (I feel most feed authors probably wouldn't care all that much)
Last-Modified and so the hit on a web server is minimal at best. -- And as you just found, _many_ clients don't yet actually even respect this field, only really yarnd does (I believe). -- And if you set it too big well then maybe nobody sees your post for a while 😅I would offer documentation on our use of the WebSub protocol, however this is not possible to implement for feed authors in _all_ cases, especially on multi-user hostrs like many of the tilde(s) I think... -- Is this something we _should_ document as an optional client feature? (I feel most feed authors probably wouldn't care all that much)
Last-Modified and so the hit on a web server is minimal at best. -- And as you just found, _many_ clients don't yet actually even respect this field, only really yarnd does (I believe). -- And if you set it too big well then maybe nobody sees your post for a while 😅I would offer documentation on our use of the WebSub protocol, however this is not possible to implement for feed authors in _all_ cases, especially on multi-user hostrs like many of the tilde(s) I think... -- Is this something we _should_ document as an optional client feature? (I feel most feed authors probably wouldn't care all that much)
refresh field could be easily replaced with Expires HTTP header (I realize that users on neocities.org cannot control this header, for example). And clients should also respect headers like Last-Modified/If-Modified-Since (304), you're right about that. P.S. twtwt doens't have a caching mechanism for now, but I plan to implement it in generic way using HTTP headers.
1. rewriting the spec (which @mckinley has done a nice job of, but I still want to host that at https://dev.twtxt.net in Markdown 😅)
2. start writing "client recommendations" (like what we did with extensions)
1. rewriting the spec (which @mckinley has done a nice job of, but I still want to host that at https://dev.twtxt.net in Markdown 😅)
2. start writing "client recommendations" (like what we did with extensions)
1. rewriting the spec (which @mckinley has done a nice job of, but I still want to host that at https://dev.twtxt.net in Markdown 😅)
2. start writing "client recommendations" (like what we did with extensions)
1. rewriting the spec (which @mckinley has done a nice job of, but I still want to host that at https://dev.twtxt.net in Markdown 😅)
2. start writing "client recommendations" (like what we did with extensions)