>It sounds like the consensus in this thread is that Amfora should not be >using the cache when the user "clicks" a link. I suppose that makes sense, >but I find that for a lot of cases using the cache improves the browsing >experience. Most content on Gemini is static, and so it's nice when the page >loads instantly, it really makes a noticeable difference, despite how fast >Gemini is. I think calling anything on this thread a consensus is being generous ;) I say since it is your app and you are not doing anything to break the spec that you are free to implement cache however you want. I think that your reasoning and method for caching makes a lot of sense. If I recall correctly, amfora has an option to disable caching. In my mind that's good enough. I think that in absence of any guarantees in the spec, that it is incumbent on the capsule owner to put a cache disclaimer on dynamic content (Dynamic content doesn't seem to be the focus of gemini anyway) I love amfora btw. Hands down my favorite gemini browser. Thanks for all your work on it. I follow it on GitHub (I'm sudobash1 there btw) and wow, is it busy :) ~Stephen
---
Previous in thread (11 of 13): 🗣️ colecmac (a) protonmail.com (colecmac (a) protonmail.com)
Next in thread (13 of 13): 🗣️ colecmac (a) protonmail.com (colecmac (a) protonmail.com)