Miserlou
Sasl python3.6
Additionally for sasl package there are some .so files added to lib folder. To use them properly one must add:
os.environ['SASL_PATH'] = os.path.join(os.getcwd(), 'lib')
Needs README and build instructions, especially for a security package from a guy with no avatar or GH history.
For a dynamic site potentially every page is dynamic. Every logged in page might display the user's name or avatar. Even the ToC and Privacy Policy pages.
Also consider that for us, we (should) be compiling static parts to strings. On a truly static page that only uses Astro components the __render() will just return a string, can't get better perf than that. Next has to deal with the cost of React components always.
I think we're saying the same thing: when we add support for dynamic, runtime pages, then they should definitely have access to querystring. But for now, in the static-only world, granting static pages access to querystring would only be a footgun since our build command would always build the page with an empty querystring.
Ah ok, I didn't realize this was a short term request. I'm fairly certain we're not currently adding any dynamic url or header information to the request object.
Awesome. Would love to get @drwpow & @natemoo-re 's eyes on this to confirm there's buy-in, then would be fine to close if this isn't actionable.
Happy to leave this open for now. I don‘t really have any thoughts on this, but it’s a good reminder of the question: “How do users expect an Astro page to behave?” In a world where we have both side-by-side, obviously. I’m not really sure, but we should have some answer to this before we get there.
I think we have a clearer story on this now, at least until we explore dynamic pages & routes. We‘ll just start new discussions for those with new insights. Closing this for now.