You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are instances where the configuration of a Micropub endpoint can change. Currently both the Media Endpont url and the syndication values are in the Micropub's config query. Because the Media Endpoint is an external service it makes sense that at times this url may change, and the user shouldn't have to log out and back in to update that value.
One option is that a Micropub server could provide a time after which the config values should be refetched. This is particularly useful in the scenerio I discuss in chat where I might have to update my Media Endpoint url every 7 days due to Amazon s3 restrictions. In this case the server could add a new configuration value called "expires_in" similar to the access token's attribute (#17) that defines the number of seconds that the configuration values are valid for, after which the Micropub client should refetch the configuration values before using them.
If no expires_in is provided, we might come up with a suggested default timeframe to refetch the config values or just recommend a button in settings that allows a user to refetch all the config values without having to log out and back in essentially refreshing their Media Endpoint url and syndication links.
The text was updated successfully, but these errors were encountered:
Even if there's no expiration set, I feel like q=config should be such a lightweight call that it's fine for a client to hit it frequently. In Micro.blog, I think I refresh the config right before someone uploads a photo, just to make sure I have the right media endpoint. Web apps could cache it for a few hours or a day.
I’m thinking about leaning on conventional HTTP stuff here and setting Cache-Control in Koype and then using that when present in Lwa and other tools. The thing being tracked/timed feels like the configuration at hand and instead of having make something new for it, I think leaning into existing stuff here would make sense for me.
There are instances where the configuration of a Micropub endpoint can change. Currently both the Media Endpont url and the syndication values are in the Micropub's config query. Because the Media Endpoint is an external service it makes sense that at times this url may change, and the user shouldn't have to log out and back in to update that value.
We did some brainstorming about this in chat.
One option is that a Micropub server could provide a time after which the config values should be refetched. This is particularly useful in the scenerio I discuss in chat where I might have to update my Media Endpoint url every 7 days due to Amazon s3 restrictions. In this case the server could add a new configuration value called "expires_in" similar to the access token's attribute (#17) that defines the number of seconds that the configuration values are valid for, after which the Micropub client should refetch the configuration values before using them.
If no expires_in is provided, we might come up with a suggested default timeframe to refetch the config values or just recommend a button in settings that allows a user to refetch all the config values without having to log out and back in essentially refreshing their Media Endpoint url and syndication links.
The text was updated successfully, but these errors were encountered: