Closed turt2live closed 3 years ago
To break the tasks down a bit further:
user_id=
param.In terms of users, Application Services specifically:
/path?access_token=$token&user_id=$userid
.Just for tracking purposes, here's the PR progress so far:
If I'm not mistaken, what's left to do is:
?user_id
query parameter for appservice access tokensorigin_server_ts
value of events through the ?ts
query parameter/transactions
route)Thanks for your amazing progress so far on this @anoadragon453! It's looking pretty good, and I'm really excited to see it implemented.
Edit: Update with current progress - @anoadragon453
@turt2live Thanks for summing it all up! I plan to add AS support to endpoints next (hopefully in some transparent fashion that future endpoints can use without hassle), then work on communicating directly the AS's.
And tests, need to start writing those :)
More for tracking purposes:
I'm also tracking progress in the spreadsheet fwiw.
Modulo #468 being verified as fixed, I don't know if this issue is very useful going forwards. All the basic AS features have landed and we can track the thirdparty endpoints / misc things as issues.
Any votes for keeping this open?
Ah memories...
I'm fine with closing it now that basic support is there. @turt2live?
yea, I think this is done enough. Is there someone who is able to accept the bounty or should I get it moved to another issue? (not sure how many people are involved, and whether it would count as conflict of interest/non-compete)
I think the PRs have come over several years, some of which have since been broken and unbroken. Suggest you move the bounty, unless I am forgetting someone (please ping loudly).
Currently this is under phase 4 for dendrite, however I'd certainly like to see it in an earlier phase. This includes:
An incredibly nice to have feature of this would also be documentation on how this API works.