{"id":38508,"date":"2023-02-17T16:24:52","date_gmt":"2023-02-17T21:24:52","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=38508"},"modified":"2023-07-13T11:51:40","modified_gmt":"2023-07-13T15:51:40","slug":"homecoming-for-mastodon-2-0","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2023\/02\/17\/homecoming-for-mastodon-2-0\/","title":{"rendered":"Homecoming for Mastodon 2.0"},"content":{"rendered":"

Jeff Johnson<\/a>:<\/p>\n

As before, when you’re viewing a Mastodon page in another instance, clicking the extension icon in Safari’s toolbar opens that page in your own instance. On the other hand, when you’re viewing a Mastodon page in your own instance, clicking the extension icon in Safari’s toolbar opens that page in the original instance.<\/p>

[…]<\/p>

Returning to motivation, why would you want to open a Mastodon page in its original instance when you’re already reading it in your instance? The answer is that a Mastodon instance is a kind of island. It can only show you the data stored locally. Unlike a centralized network such as Twitter or Facebook, Mastodon is decentralized and distributed: no individual instance has a copy of all<\/em> the data encompassing the federation of Mastodon, only a subset of the data. Every Mastodon instance has gaps in its data, blind spots. An instance stores all of the posts of its local accounts, and it downloads new posts of anyone followed by its local accounts, as notified by the ActivityPub protocol<\/a>, but your instance doesn’t download old<\/em> posts from other instances. This is why when you view someone else’s account profile in your instance, you might not see their older posts (unless someone else on your own instance was already following that account).<\/p>

The data gaps are especially problematic on smaller Mastodon instances with fewer accounts, because on a smaller instance it’s less likely that another account on your instance was already following someone you’re interested in.<\/p><\/blockquote>\n

This is a great new feature, since the built-in Open original page<\/strong> menu command is not in a convenient location. It’s also useful for finding the RSS feed of a user.<\/p>\n

Unfortunately, there is no way to assign keyboard shortcuts to extension buttons in Safari. So I wrote an AppleScript to click the button:<\/p>\n

tell application \"System Events\"\n    tell application process \"Safari\"\n        set _items to entire contents of toolbar 1 of window 1\n        repeat with _item in _items\n            if _item's class is button and _item's description is \"Homecoming for Mastodon\" then\n                click _item\n                return\n            end if\n        end repeat\n    end tell\nend tell<\/pre>\n
and used FastScripts<\/a> to assign the script a keyboard shortcut.<\/p>\n
Unfortunately, the script has yet to work for me when run from FastScripts<\/em>, even though I gave Accessibility access to both FastScripts and FastScripts Script Runner. It always fails with:<\/p>\n
Error Number: -1719<\/p>\n
System Events got an error: Can’t get toolbar 1 of window 1 of application process \"Safari\". Invalid index.<\/p><\/blockquote>\n
I assume this is some sort of TCC issue since the script sometimes works from Script Debugger but sometimes fails with a similar error.<\/p>\n\n
Previously:<\/p>\n