Age | Commit message (Collapse) | Author |
|
and atom feed generation to some extent, as well as the way mentions are
stored
|
|
|
|
local account
|
|
|
|
(But there are no Atom feed pagination elements yet)
|
|
relations on Status#mentions
|
|
|
|
|
|
|
|
|
|
|
|
related to #20
|
|
|
|
|
|
|
|
|
|
|
|
simplify FanOutOnWriteService, add /api/accounts/lookup method
|
|
|
|
|
|
|
|
|
|
|
|
[skip ci]
|
|
[ci skip]
|
|
fix tests (the recorded Salmon fixture expects LOCAL_DOMAIN to be something
specific unfortunately)
|
|
|
|
|
|
|
|
|
|
|
|
Fixing another mention recording bug
|
|
limiting implementations
|
|
|
|
|
|
|
|
|
|
of those to depend on presence of <thr:in-reply-to /> instead
|
|
[ci skip]
|
|
|
|
the block, even though the last line of a block is an implicit return. I am
confused to say the least
|
|
|
|
|
|
|
|
|
|
|
|
when registering incoming status mentions, add Travis CI file
|
|
|
|
local followers. Remote users' usernames SHOULD be case-sensitive
|
|
|