{"action":"created","issue":{"url":"https://api.github.com/repos/jdormit/pterotype/issues/5","repository_url":"https://api.github.com/repos/jdormit/pterotype","labels_url":"https://api.github.com/repos/jdormit/pterotype/issues/5/labels{/name}","comments_url":"https://api.github.com/repos/jdormit/pterotype/issues/5/comments","events_url":"https://api.github.com/repos/jdormit/pterotype/issues/5/events","html_url":"https://github.com/jdormit/pterotype/issues/5","id":377152663,"node_id":"MDU6SXNzdWUzNzcxNTI2NjM=","number":5,"title":"Federation with Mastodon is broken?","user":{"login":"jdormit","id":6351890,"node_id":"MDQ6VXNlcjYzNTE4OTA=","avatar_url":"https://avatars1.githubusercontent.com/u/6351890?v=4","gravatar_id":"","url":"https://api.github.com/users/jdormit","html_url":"https://github.com/jdormit","followers_url":"https://api.github.com/users/jdormit/followers","following_url":"https://api.github.com/users/jdormit/following{/other_user}","gists_url":"https://api.github.com/users/jdormit/gists{/gist_id}","starred_url":"https://api.github.com/users/jdormit/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jdormit/subscriptions","organizations_url":"https://api.github.com/users/jdormit/orgs","repos_url":"https://api.github.com/users/jdormit/repos","events_url":"https://api.github.com/users/jdormit/events{/privacy}","received_events_url":"https://api.github.com/users/jdormit/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2018-11-04T13:25:54Z","updated_at":"2018-11-05T03:43:28Z","closed_at":"2018-11-05T03:43:28Z","author_association":"OWNER","body":"I can't tell if this is an issue with Mastodon or Pterotype.\r\n\r\nI deleted and re-created the QA instance. Now, when I search for it in the Mastodon search bar, both on mastodon.technology and a locally running instance, no results come up. From the local Mastodon server logs I can see that the webfinger request is made and receives a 200 back from Pterotype, and I've confirmed manually that the webfinger endpoint and the blog actor endpoint are both working.\r\n\r\nSo what's going on here? Is Mastodon doing some sort of weird caching thing?"},"comment":{"url":"https://api.github.com/repos/jdormit/pterotype/issues/comments/435746846","html_url":"https://github.com/jdormit/pterotype/issues/5#issuecomment-435746846","issue_url":"https://api.github.com/repos/jdormit/pterotype/issues/5","id":435746846,"node_id":"MDEyOklzc3VlQ29tbWVudDQzNTc0Njg0Ng==","user":{"login":"jdormit","id":6351890,"node_id":"MDQ6VXNlcjYzNTE4OTA=","avatar_url":"https://avatars1.githubusercontent.com/u/6351890?v=4","gravatar_id":"","url":"https://api.github.com/users/jdormit","html_url":"https://github.com/jdormit","followers_url":"https://api.github.com/users/jdormit/followers","following_url":"https://api.github.com/users/jdormit/following{/other_user}","gists_url":"https://api.github.com/users/jdormit/gists{/gist_id}","starred_url":"https://api.github.com/users/jdormit/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jdormit/subscriptions","organizations_url":"https://api.github.com/users/jdormit/orgs","repos_url":"https://api.github.com/users/jdormit/repos","events_url":"https://api.github.com/users/jdormit/events{/privacy}","received_events_url":"https://api.github.com/users/jdormit/received_events","type":"User","site_admin":false},"created_at":"2018-11-05T03:43:28Z","updated_at":"2018-11-05T03:43:28Z","author_association":"OWNER","body":"Ha, figured it out. The problem was that I was serving the WordPress instance over `https`, but it had its site URL configured to `http://qa1.getpterotype.com` (not `https`). This meant that the actor's `url` was mismatched between Mastodon and Pterotype, so Mastodon couldn't find the actor when it received an update. Once I updated the WordPress site URL (in settings) to `https://qa1.getpterotype.com`, the federation worked just fine.\r\n\r\nThis means that the WebFinger discovery problem mentioned in the first issue comment is almost certainly a caching problem on Mastodon's side. I'm going to close this issue out, since it's not a problem with Pterotype, and think more about what to do about Mastodon's aggressive caching."}}
{"actor":{"display_login":"jdormit"}}