|
|
|
|
|
by olejorgenb
969 days ago
|
|
The one they shared is backed by gist which is much better if you want to understand the code. The gist also allow people to comment on the bookmarklet. Of course - now they have a way of injecting arbitrary javascript code into the browser of the people using the service to bookmark the bookmarklet. Lack of trust sucks. And (due to lack of trust) most applications make it hard to share javscripts links - so you need to instead instruct people to create a new bookmark and past the content into instead of right-clicking a link and clicking "bookmark". |
|
The security risk angle is also a concern I share. If you take a look at the disclaimer at the bottom of my project README [1], you'll see this exact issue mentioned. Versioning gists and thus bookmarklets is discussed in the same document [2]. This locks bookmarklet source to a specific commit of the git repo underlying a gist.
[1] https://github.com/ashtonmeuser/bookmarklet-platform?tab=rea...
[2] https://github.com/ashtonmeuser/bookmarklet-platform?tab=rea...