{"id":51963,"date":"2026-05-20T14:13:42","date_gmt":"2026-05-20T18:13:42","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=51963"},"modified":"2026-05-20T14:13:42","modified_gmt":"2026-05-20T18:13:42","slug":"updating-shared-shortcuts","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2026\/05\/20\/updating-shared-shortcuts\/","title":{"rendered":"Updating Shared Shortcuts"},"content":{"rendered":"

Manuel Grabowski<\/a>:<\/p>\n

\n

No actual concept of versioning or upgrades for shared shortcuts. Sharing shortcuts happens via weird iCloud URLs rather than being an actual aspect of the system. So to update a shortcut, do you just add it again? No indication of what that will do before you press the button. Will it error out? Will it create a duplicate? Will it update\/replace the existing one?<\/p>\n

[…]<\/p>\n

Of course this Playmobil-ass UI doesn’t show anything<\/em> that would be remotely useful for serious people. Imagine wanting to sort<\/em> your shortcuts by date or see the last modification date<\/a>, like some rocket scientist.<\/p>\n<\/blockquote>\n\n

Needless to say, there’s no version control or diffing, either. There’s so much stuff that apps can get for free if they use the file system instead of opaque storage. Bypassing it in the name of simplicity makes some things easier but blocks a long tail of possibilities—as well as basic stuff like sorting, if the app doesn’t provide it.<\/p>\n\n

Previously:<\/p>\n