| Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
persist_event check if we already have the event, if so then update instead of replacing so that we don't cause a bump of the stream_ordering.
|
|
|
|
check. If an event does fail a signature check, look in the local database and request it from the originator.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
from pip install
|
|
|
|
room
|
|
|
|
|
|
|
|
|
|
|
|
|
|
implemented if the client attempts to do a gapless sync
|
|
Means that now you can't do exact matches even in override rules,
but I think we can live with that. Advantage is that you'll now
always get back what was put in to the API.
|
|
|
|
|
|
|
|
|
|
|
|
only 2 people.
|
|
|
|
|
|
|
|
|
|
/query_auth/ so that we don't duplicate events in the response.
|
|
|
|
|
|
|
|
|
|
sync with a gap
|
|
|
|
|
|
removed in 15.
|
|
|
|
|
|
event graph
|
|
|
|
|
|
sender display names where they exist.
|
|
your username / display name
|
|
|
|
|
|
split the storage and management of filters from the actual filter code
and don't have to load a filter from the db each time we filter an event
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
changes is small
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
for the clients that made those requests
|
|
|
|
constructor
|
|
|
|
|
|
of the filter, rather than the complete json
|
|
|
|
identifier
|
|
|
|
device_id in the internal meta data for the event along with the transaction id when sending events
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ports 80/443 and the web client defaults to that now. Fixes email validation (including signing up with an email address).
|
|
|
|
|
|
|
|
|
|
|
|
out in the REST-level tests
|