Open Hoi15A opened 7 years ago
I like that idea alot. So basically we'd need to save the current view (in JSON) on the server side somehow.
For the URL that gets generated I suggest something like: https://<host>/share/table/d3a3ff16cdaeee94d3a3ff16cdaeee94
. The last part being an unique ID. 32 Chars should be good enough to prevent bruteforcing, right?
The idea is that you can filter some stuff in the table and then click a share button that would copy an url to share which can be used to display said stuff without requiring the API key of the chat.