You don't need an extension for that and allow questionable privacy settings like "access to all websites". Just use a bookmarklet (create a new bookmark e.g. in your top bar and add this code as URL):
Sounds intriguing. I currently copy the URL of any page I am interested in and then open a new tab, click the favourite for archive.is and then paste the URL and hit save. Then I do the same with web.archive.org/save
If shortcuts can make this process faster and require fever steps when I use them, I would like to have a shortcut for each of those two archive sites.
Anyone have good shortcut to share for either of the two archive sites?
I found some but neither of the ones I tried were quite perfect. The one for Wayback Machine navigated there but did not automatically start the save. The one for archive.is activated reader mode after archiving.
I've been doing this for years but missed the run=1 argument in archive.today to go directly to the latest copy instead of the list of all copies. Thank you!
I’ve been using a homemade Shortcut for the same purpose. They’re great when you want a bit of control over such things. For example, expanding the url (following all redirects) before sending it to archive.ph/md/is, 12ft.io, or Reading List, etc. It’s very annoying having t.co urls in Reading List in particular.
You can edit the resulting url before opening it or copying it, and choose between archive.ph, .md, etc. Editing is useful if you want to get rid of utm_source arguments, etc.
Apple’s Shortcuts is just a hodgepodge of built in functions, the best way to learn is just to try build something like this. You’ll be searching a few times for the little function you want until you find the right name for it. As far as discoverability goes, it’s OK, gets the job done. Naming things is weird too — let’s say you make a Text block, then you can only seem to name it when you reference it elsewhere (Select Magic Variable, scroll and tap it, then highlight it and Rename from the menu).
Note: you have to both enable the extension and set its permissions for "All Websites" to "Allow". If you have its permissions set to "Ask" then it will take you to archive.ph but not actually load the current tab's URL.
This explains the behavior folks are commenting on here where it appears not to work.
The issue is that if you do not set permissions in the manifest, clicking allow in the safari UI would only return a blank URI, "". The original extension in this case would also just return an error.
I've modified the manifest so that it is asking Safari for wider permissions, so that when the permission is granted by the user, the proper URL is returned.
Currently the extension will suggest that it needs access to every page the user visits, occasionally opening a popup automatically if I remember correctly.
For something that’s a glorified bookmarklet, that’s a lot to ask.
Yeah, there should be two redirects. The first is searching for the URL you entered, the second should either newly cache the page, or load the cached page. Same behavior as firefox.
Maybe include some more verbose instructions on the screen that displays on my iPad when I attempt to open the app. Following instructions from other posters on this thread has it working beautifully. Thanks!
You need to go into the Extension preference page for the extension, and hit the "Allow Access" permission box for allowing access to web url/link information. I can't remember exact wording, but should essentially be one option here and you have to enable it so that it has permission to pass along URL.
This should be the expected behavior when pressing the button on a new Safari tab. Otherwise, should redirect to the URL your current open tab is displaying.
Then something in the UX is broken. From your store images, I understood that clicking on that tab menu item, it would display last archive date and ask to rearchive, no?
There is a reason why most Safari extensions apps do not just show an icon and a label, but actually explain how to use their embedded extensions.
The extension is open source, I'm open to new ideas on how to improve this further. The current Edge/Firefox extensions just error out, and this was not acceptable for this version of the extension per the AppStore rules.
