about summary refs log tree commit diff
path: root/spec
AgeCommit message (Collapse)Author
2016-11-28Adding embedded PuSH serverEugen Rochko
2016-11-26Update hub URL and re-subscribe if hub URL changesEugen Rochko
2016-11-24Remove Neo4JEugen Rochko
2016-11-20Adding unified streamable notificationsEugen Rochko
2016-11-18Fix OAuth authorization page and add a spec for itEugen Rochko
2016-11-17Fix #148 - Devise mailer fixed, test spec added so it won't slip past againEugen Rochko
2016-11-16Remove broken testEugen Rochko
2016-11-16Localizations for most server-side stringsEugen Rochko
2016-11-13Fix #142 - Escape ILIKE special characters from Account.find_remoteEugen Rochko
2016-11-12Upgrade ruby to 2.3.1Eugen Rochko
2016-11-10Discard misattributed remote statuses, improve timelines filterEugen Rochko
2016-11-08Move timelines API from statuses to its own controller, add a check forEugen Rochko
resources that require a user context vs those that don't (such as public timeline) /api/v1/statuses/public -> /api/v1/timelines/public /api/v1/statuses/home -> /api/v1/timelines/home /api/v1/statuses/mentions -> /api/v1/timelines/mentions /api/v1/statuses/tag/:tag -> /api/v1/timelines/tag/:tag
2016-11-06Add test for FanOutOnWriteServiceEugen Rochko
2016-11-05Improve @mention regexEugen Rochko
2016-11-05Adding hashtagsEugen Rochko
2016-11-04Adding hashtag modelEugen Rochko
2016-11-03Add tests for recently added API end pointsEugen Rochko
2016-10-20add/update specs for Button, DisplayName, DropdownMenuKai Schaper
2016-10-18Adding application/jrd+json webfinger resourceEugen Rochko
2016-10-15Exclude blocked users from follow suggestions, fix testsEugen Rochko
2016-10-14Merge branch 'kschaper-avatar-component-testing' into developmentEugen Rochko
2016-10-14Merge branch 'avatar-component-testing' of ↵Eugen Rochko
https://github.com/kschaper/mastodon into kschaper-avatar-component-testing
2016-10-14E-mail preferences pageEugen Rochko
2016-10-13Shorten rendered links (strip protocol and www, truncate to 30 chars), redirectEugen Rochko
to sign in page after sign up instead of root path which redirects to /about
2016-10-12actually use constKai Schaper
2016-10-12add chai-enzyme; add/improve Avatar component specsKai Schaper
2016-10-10use ES6 arrow functionsKai Schaper
2016-10-10add sinon; add basic Button component testKai Schaper
2016-10-10add jsdom; add basic Avatar component testKai Schaper
2016-10-10set up Mocha/Chai/Enzyme for React component unit testingKai Schaper
2016-10-10Adding test for ProcessFeedServiceEugen Rochko
2016-10-09Adding domain blocksEugen Rochko
2016-10-07Adding public timelineEugen Rochko
2016-10-03API for blocking and unblockingEugen Rochko
2016-10-03Adding a block model and filter mentions from blocked users (fix #60)Eugen Rochko
2016-10-03Adding e-mail confirmationsEugen Rochko
2016-10-02Add API for getting info about authenticated user: ↵Eugen Rochko
/api/v1/accounts/verify_credentials
2016-10-02Preparing feeds for better filteringEugen Rochko
2016-09-30Fix tests, update goldfinger to catch XML errorsEugen Rochko
2016-09-27Fix testsEugen Rochko
2016-09-27Adding landing pageEugen Rochko
2016-09-27Fix #52 - Add API versioning (v1)Eugen Rochko
2016-09-26Replace logo, fix #57 - delete/unreblog/unfavourite API, fix #45 - appEugen Rochko
registration API
2016-09-26Fix #54 - Fetch remote accounts by URL from mentionsEugen Rochko
Fetching atom extracted from FetchRemoteAccountService and FetchRemoteStatusService into FetchAtomService. Mentions of the constant "http://activityschema.org/collection/public" skipped as it's not a real URL/user.
2016-09-21Fix notifications in UI, added new API for fetching account relationshipsEugen Rochko
2016-09-21Fix #24 - Thread resolving for remote statusesEugen Rochko
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.
2016-09-20Upgrade to PubSubHubbub 0.4 (removing verify_token)Eugen Rochko
2016-09-18Small rubocop offences removedEugen Rochko
2016-09-18Fix #43Eugen Rochko
2016-09-16Test case for new api endpointEugen Rochko