conduit

Commit Graph

Author	SHA1	Message	Date
Timo Kösters	df727688ef	remove rocksdb	5 years ago
Timo Kösters	902404d48d	improvement: save member count + sled fixes	5 years ago
Timo Kösters	b813c34642	improvement: more auth chain caching	5 years ago
Timo Kösters	ab7835dedb	fix: early return from state res	5 years ago
Timo Kösters	9bb4c3cd01	improvement: batched inserts for tokenids	5 years ago
Timo Kösters	fce22362d4	improvement: better auth chain calculation	5 years ago
Timo Kösters	0eeba86b32	fix: improve locks	5 years ago
Timo Kösters	bd63797213	improvement: make better use of sqlite connections	5 years ago
Timo Kösters	5e924227b6	feat: add threadpool for iterator threads, bug fixes, tracing_flame support	5 years ago
Timo Kösters	918df9ca6d	feat: support room version 5	5 years ago
Timo Kösters	f121978897	fix: state bug	5 years ago
Timo Kösters	80533bfab2	fix: improve code when skipping /state_ids	5 years ago
Timo Kösters	728e176a06	feat: /keys/query and /keys/claim over federation	5 years ago
Timo Kösters	68cc743f2a	fix: use get_auth_chain method more often	5 years ago
Timo Kösters	0f8ecdc625	fix: state res fixes	5 years ago
Timo Kösters	cfaa900e83	improvement: auth chain cache	5 years ago
Timo Kösters	f5273f7eb1	improvement: upgrade ruma and implement blurhashes	5 years ago
Timo Kösters	0fcefa4125	fix: ruma	5 years ago
Timo Kösters	e12b1ff863	improvement: locks	5 years ago
Timo Kösters	e15e6d4405	improvement: efficient /sync, mutex for federation transactions	5 years ago
Timo Kösters	1c25492a7e	fix: stuck messages Conduit did not send the event in /sync because of a race condition. There is a brief moment in time where Conduit accepted the event, but did not store it yet. So when the client /syncs it updates the since token without sending the event. I hope I fixed it by significantly shortening the race-condition period.	5 years ago
Timo Kösters	ac0027756e	improvement: more efficient state res	5 years ago
Jonathan de Jong	9d4fa9a220	Sqlite	5 years ago
Devin Ragotzy	1bb84a8e2d	Fix docs for fetch_and_handle_events	5 years ago
Devin Ragotzy	98f1480e2b	Remove auth_cache using a closure to fetch events in state-res	5 years ago
Timo Kösters	05821d6fd5	improvement: pdu cache, /sync cache	5 years ago
Devin Ragotzy	09a8737f24	Export conduits Config struct and fix clipp warningsy	5 years ago
Jonas Platte	808741bcb6	Remove unnecessary Option-wrapping and successive unwrapping	5 years ago
Jonas Platte	b291e76572	Use try operator for Option more	5 years ago
Jonas Platte	f3e630c064	Fix lots of clippy lints	5 years ago
Jonas Platte	f6046871f4	Upgrade Ruma	5 years ago
Timo Kösters	67f9592b17	feat: /event_auth	5 years ago
Timo Kösters	3c9ea55938	feat: /state	5 years ago
Timo Kösters	cd4bc520d8	improvement: feature flags for sled, rocksdb	5 years ago
Timo Kösters	d0ee823254	feat: swappable database backend	5 years ago
Timo Kösters	5b5cc0574e	feat: implement /claim, handle to-device events	5 years ago
Gabriel Souza Franco	7db59c550f	fix: also return successful PDUs in /send/:txnId	5 years ago
Timo Kösters	daa1fc90a7	fix: state resolution bugs	5 years ago
Timo Kösters	e5c7119516	feat: forward federation errors to the client	5 years ago
Timo Kösters	989d843c40	fix: unauthorized pdus will be responded to with FORBIDDEN	5 years ago
Timo Kösters	09157b2096	improvement: federation get_keys and optimize signingkey storage - get encryption keys over federation - optimize signing key storage - rate limit parsing of bad events - rate limit signature fetching - dependency bumps	5 years ago
Timo Kösters	ae41bc5067	fix: run state res with old current state again I'm a bit torn on the "auth check based on the current state of the room". It can mean multiple things: 1. The state of the room before the homeserver looked at the event at all. But that means if a message event from a user arrives, but we didn't see their join event before, we soft fail the message (even though we would find the join event when going through the auth events of the event and doing state res) 2. The state of the room after doing state-res with the event and our previous room state. We need to do this state resolution to find the new room state anyway, so we could just use the new room state for the auth check. The problem is that if the incoming event is a membership leave event, the new room state does not allow another leave event. This is obviously the wrong option. 3. The state of the room after doing state-res with the state before the event and our previous room state. This will mean a lot more calculations because we have to run state-res again We used 2. before and now use 1. again	5 years ago
Timo Kösters	f62258ba35	improvement: bug fixes and refactors - power level content override adds to the default event instead of replacing it - sending code refactored to make edus possible - remove presence events when restarting conduit - remove room_id field from read receipts over /sync - handle incoming read receipts - fix array bounds bug in server_server.rs	5 years ago
Jonas Platte	a0457000ff	Upgrade Ruma	5 years ago
Timo Kösters	cf94b8e712	improvement: uiaa works like in synapse	5 years ago
Jonas Platte	8bfaf09f37	Clean up reqwest::Response to http::Response conversion	5 years ago
Jonas Platte	2e1d7d12ca	Refactor usage of CanonicalJsonValue	5 years ago
Timo Kösters	58463bba93	feat: send invites over federation	5 years ago
Timo Kösters	226045ea4b	improvement: warning on misconfigured reverse proxy	5 years ago
Jonas Platte	d8b484beed	Upgrade ruma	5 years ago

1 2 3 4

189 Commits (76660bf1892fcd66cb2bced49c4e1b0f4e64d75a)