Clean all URLs in clipboard
-
As a WebDev... URL parameters are definitely not the place to keep state... Were not in the 00's anymore. They do have legit uses, but we have JS localStorage nowadays.
They have pretty different use cases. Localstorage is for when you want persistence across page loads, not necessarily specific to any particular page but specific to a browser. An example would be storing user-selected light or dark mode.
Query parameters are specific to a page/URL and you get a lot of things for free when you use them:
- back/forward navigation
- bookmarking
- copy-paste to share
- page level caching
- access on both server and client
Query parameters are good for things like searches, filters, sorting, etc
-
They have pretty different use cases. Localstorage is for when you want persistence across page loads, not necessarily specific to any particular page but specific to a browser. An example would be storing user-selected light or dark mode.
Query parameters are specific to a page/URL and you get a lot of things for free when you use them:
- back/forward navigation
- bookmarking
- copy-paste to share
- page level caching
- access on both server and client
Query parameters are good for things like searches, filters, sorting, etc
I disagree. I definitely prefer REST APIs that use the file path for searches, filters, sorting. You get most if not all benefits from query parameters, and if done correctly it is just as clearly readable as query params.
-
I disagree. I definitely prefer REST APIs that use the file path for searches, filters, sorting. You get most if not all benefits from query parameters, and if done correctly it is just as clearly readable as query params.
But what if you have multiple optional parameters?
-
But what if you have multiple optional parameters?
have multiple routes point to the same endpoint, dynamically adding the parameters serverside
-
have multiple routes point to the same endpoint, dynamically adding the parameters serverside
That sounds harder than just using query parameters. What are the benefits?
-
That sounds harder than just using query parameters. What are the benefits?
Having more beautiful and structured URLs. I suppose for those cases it's more of a preference, and with the tooling I use (.NET) it's not too difficult to achieve.
I guess my gripe with your original statement was that I was thinking mostly of state like user login etc. I have to concede it's not totally garbage for the cases you mentioned.
-
I know firefox has the very useful "Copy clean Link" option in the context menu, but I would like a similar feature for copying links from any other software, like spotify for example. So I am looking for some software that hooks into the clipboard pipeline, and cleans any URL that gets added. I tried googling for something like it, but was completely unsuccessful. Does anyone have a clue how I might go about achieving this?
Thanks in advance
Looks like https://old.reddit.com/r/kde/comments/d3m0fz/how_to_open_links_in_mpv_with_klipper/ is a good starting point, i.e
- Open menu in system tray.
- Right click on Clipboard => Configure Clipboard.
- Go to Actions Configuration => Add Action.
then... to try!
I'm just discovering this too but seems like the right way.That said I'd be cautious and limit the use case to only what you have, e.g. Spotify links, at least at first because I imagine one can get into hairy edge cases quickly.
Keep us posted!
-
System shared this topic on
