1. 21 Sep, 2016 4 commits
  2. 20 Sep, 2016 6 commits
    • Eugen Rochko's avatar
      Fix #24 - Thread resolving for remote statuses · 4bec6138
      Eugen Rochko authored
      This is a big one, so let me enumerate:
      Accounts as well as stream entry pages now contain Link headers that
      reference the Atom feed and Webfinger URL for the former and Atom entry
      for the latter. So you only need to HEAD those resources to get that
      information, no need to download and parse HTML <link>s.
      ProcessFeedService will now queue ThreadResolveWorker for each remote
      status that it cannot find otherwise. Furthermore, entries are now
      processed in reverse order (from bottom to top) in case a newer entry
      references a chronologically previous one.
      ThreadResolveWorker uses FetchRemoteStatusService to obtain a status
      and attach the child status it was queued for to it.
      FetchRemoteStatusService looks up the URL, first with a HEAD, tests
      if it's an Atom feed, in which case it processes it directly. Next
      for Link headers to the Atom feed, in which case that is fetched
      and processed. Lastly if it's HTML, it is checked for <link>s to the Atom
      feed, and if such is found, that is fetched and processed. The account for
      the status is derived from author/name attribute in the XML and the hostname
      in the URL (domain). FollowRemoteAccountService and ProcessFeedService
      are used.
      This means that potentially threads are resolved recursively until a dead-end
      is encountered, however it is performed asynchronously over background jobs,
      so it should be ok.
    • Eugen Rochko's avatar
    • Eugen Rochko's avatar
      Since GNU Social hubs don't seem to return a hub.lease_seconds param in the... · 1d2856c2
      Eugen Rochko authored
      Since GNU Social hubs don't seem to return a hub.lease_seconds param in the subscription confirmation request,
      we'll have to default that value to the GS "minimum" (from their code) which is 24 hours.
    • Eugen Rochko's avatar
      More debugging for PuSH confirmations · 24633049
      Eugen Rochko authored
    • Eugen Rochko's avatar
      Add more logging to PuSH callback · a66d3487
      Eugen Rochko authored
    • Eugen Rochko's avatar
  3. 19 Sep, 2016 6 commits
  4. 18 Sep, 2016 10 commits
  5. 17 Sep, 2016 7 commits
  6. 16 Sep, 2016 1 commit
  7. 15 Sep, 2016 2 commits
  8. 13 Sep, 2016 1 commit
  9. 12 Sep, 2016 3 commits