URLFormJS

I'm concerned about the `#` character in the URL. # means fragment and that's kept local and not sent to the server unless client side Javascript sends it to the server. I would use an identifier that doesn't already mean something to the URL. See the URL spec here: https://www.rfc-editor.org/rfc/rfc3986#section-3.5 We are using this in a lot of our projects, like https://github.com/Cyphrme/URLFormJS#query-parameters-fragme... (and https://github.com/Cyphrme/Path) For an example where this is relevant: https://cyphr.me/ed25519_tool/ed.html#?msg_encoding=Text&msg...

We wrote a library for storing application state in the URL. Its novel feature is using fragment query, which prevents the information from being sent to the server. https://github.com/Cyphrme/URLFormJS I would love to see it get more use. Here's a small demo: https://cyphrme.github.io/URLFormJS/#?first_name=Bob&last_na... See my other comment on this page for some other examples of its use.

I wrote a library based on that very idea. It supports fragment query, just like normal queries. https://github.com/Cyphrme/URLFormJS I use it in a lot of places, like: https://convert.zamicol.com/#?inAlph=Text&in=Hello%20world!&... https://cyphr.me/ed25519_applet/ed.html#?msg=Hello%20World!&... https://cyphr.me/coze#?verify&input={%22pay%22:{%22root%22:%...

As it stands today, the spec has issues when considering other pre-existing options and future compatibility. For example, there is no way to get the URL if the protocol is `file://`. For a real world example: https://github.com/mozilla/standards-positions/issues/194#is... See the stack overflow issue: https://stackoverflow.com/questions/67039633/get-the-text-fr... (See also the currently "conflicting" library for URL fragment queries: https://github.com/Cyphrme/URLFormJS) I think it can be easily fixed, using solutions like a delimiter, but that discussion probably needs to be apart of a wider discussion concerning URL extensibility.