{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":429818374,"defaultBranch":"master","name":"synapse","ownerLogin":"famedly","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2021-11-19T14:03:23.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/46558835?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1725551971.0","currentOid":""},"activityList":{"items":[{"before":null,"after":"8daba592503b001d015cb60c5ca8d9c1c52c8d3c","ref":"refs/heads/nico/reliable-spam-check-on-room-create","pushedAt":"2024-09-05T15:59:31.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"nico-famedly","name":"Nicolas Werner","path":"/nico-famedly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/89468146?s=80&v=4"},"commit":{"message":"Run spam checker callbacks for invites early during room creation\n\nThis prevents a partial room from being returned to clients. We can't\ncurrently validate all possible failure cases before sending out invites\n(since invites can fail for arbitrary reasons on the remote side).\nAdditionally there are some other cases that might still create a\npartial room (alias length, third party callbacks, etc probably), that\naren't covered by this change. Third-party invites are ignored as well.\n\nA proper fix to make the room creation atomic will most likely need spec\nchanges.\n\nSigned-off-by: Nicolas Werner ","shortMessageHtmlLink":"Run spam checker callbacks for invites early during room creation"}},{"before":null,"after":"b635246395ffdd93888ca6b6d9c54f06d248d96e","ref":"refs/heads/release-v1.114","pushedAt":"2024-09-05T11:21:43.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"nico-famedly","name":"Nicolas Werner","path":"/nico-famedly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/89468146?s=80&v=4"},"commit":{"message":"chore: update to newest sta version","shortMessageHtmlLink":"chore: update to newest sta version"}},{"before":"4d670318093c600bdf24ddb7246815cb621f7aa4","after":"b635246395ffdd93888ca6b6d9c54f06d248d96e","ref":"refs/heads/master","pushedAt":"2024-09-05T11:21:40.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"nico-famedly","name":"Nicolas Werner","path":"/nico-famedly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/89468146?s=80&v=4"},"commit":{"message":"chore: update to newest sta version","shortMessageHtmlLink":"chore: update to newest sta version"}},{"before":null,"after":"4d670318093c600bdf24ddb7246815cb621f7aa4","ref":"refs/heads/release-v1.112","pushedAt":"2024-08-12T16:26:09.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"nico-famedly","name":"Nicolas Werner","path":"/nico-famedly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/89468146?s=80&v=4"},"commit":{"message":"chore: update to newest sta version","shortMessageHtmlLink":"chore: update to newest sta version"}},{"before":"01f19ea2a437aeeeda4da448ec8aa5cbb137b998","after":"4d670318093c600bdf24ddb7246815cb621f7aa4","ref":"refs/heads/release-v1.111","pushedAt":"2024-07-30T21:55:10.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"nico-famedly","name":"Nicolas Werner","path":"/nico-famedly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/89468146?s=80&v=4"},"commit":{"message":"chore: update to newest sta version","shortMessageHtmlLink":"chore: update to newest sta version"}},{"before":"01f19ea2a437aeeeda4da448ec8aa5cbb137b998","after":"4d670318093c600bdf24ddb7246815cb621f7aa4","ref":"refs/heads/master","pushedAt":"2024-07-30T21:55:08.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"nico-famedly","name":"Nicolas Werner","path":"/nico-famedly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/89468146?s=80&v=4"},"commit":{"message":"chore: update to newest sta version","shortMessageHtmlLink":"chore: update to newest sta version"}},{"before":"4e0222315b99a28c62fc2a53c1f4961f26f576d4","after":null,"ref":"refs/heads/dependabot/pip/sentry-sdk-1.14.0","pushedAt":"2024-07-29T10:19:25.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"dependabot[bot]","name":null,"path":"/apps/dependabot","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/29110?s=80&v=4"}},{"before":"d02353edbd9242826261c3408f3c4a667af38fe8","after":null,"ref":"refs/heads/dependabot/pip/pygments-2.15.0","pushedAt":"2024-07-29T10:19:24.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"dependabot[bot]","name":null,"path":"/apps/dependabot","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/29110?s=80&v=4"}},{"before":"b847a86d5c21a538653ff3878d917da49ca3a691","after":null,"ref":"refs/heads/dependabot/pip/certifi-2023.7.22","pushedAt":"2024-07-29T10:19:24.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"dependabot[bot]","name":null,"path":"/apps/dependabot","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/29110?s=80&v=4"}},{"before":"b362b6de22f1e0c5a4b8cbb06e9995c91d60c158","after":null,"ref":"refs/heads/dependabot/pip/requests-2.31.0","pushedAt":"2024-07-29T10:19:22.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"dependabot[bot]","name":null,"path":"/apps/dependabot","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/29110?s=80&v=4"}},{"before":"808ddd719f2c1124be79e41c0cb67427bb7d45a1","after":null,"ref":"refs/heads/dependabot/pip/cryptography-41.0.2","pushedAt":"2024-07-29T10:19:22.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"dependabot[bot]","name":null,"path":"/apps/dependabot","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/29110?s=80&v=4"}},{"before":"4898696c44a376c5a03fc5567dba692a9b72606a","after":null,"ref":"refs/heads/dependabot/pip/setuptools-65.5.1","pushedAt":"2024-07-29T10:19:22.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"dependabot[bot]","name":null,"path":"/apps/dependabot","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/29110?s=80&v=4"}},{"before":null,"after":"01f19ea2a437aeeeda4da448ec8aa5cbb137b998","ref":"refs/heads/release-v1.111","pushedAt":"2024-07-29T10:14:26.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"nico-famedly","name":"Nicolas Werner","path":"/nico-famedly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/89468146?s=80&v=4"},"commit":{"message":"chore: update to newest sta version","shortMessageHtmlLink":"chore: update to newest sta version"}},{"before":"5e7f140303dfc8c2ae2a9248f3f16a1d479bf851","after":"01f19ea2a437aeeeda4da448ec8aa5cbb137b998","ref":"refs/heads/master","pushedAt":"2024-07-29T10:05:58.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"nico-famedly","name":"Nicolas Werner","path":"/nico-famedly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/89468146?s=80&v=4"},"commit":{"message":"chore: update to newest sta version","shortMessageHtmlLink":"chore: update to newest sta version"}},{"before":"030bc3149999eb7a2124ee0f0fe67836608aa6bb","after":"5e7f140303dfc8c2ae2a9248f3f16a1d479bf851","ref":"refs/heads/master","pushedAt":"2024-07-02T13:01:21.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nikzen","name":"Niklas Zender","path":"/nikzen","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33399346?s=80&v=4"},"commit":{"message":"chore: update to newest sta version","shortMessageHtmlLink":"chore: update to newest sta version"}},{"before":null,"after":"030bc3149999eb7a2124ee0f0fe67836608aa6bb","ref":"refs/heads/release-v1.109","pushedAt":"2024-06-27T13:53:28.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"emgrav","name":"Emelie Graven","path":"/emgrav","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/614975?s=80&v=4"},"commit":{"message":"Allow clients to configure when a refresh token expires\n\nThis allows clients to pass an extra parameter when refreshing a token,\nwhich overrides the configured refresh token timeout in the Synapse\nconfig. This allows a client to opt into a shorter (or longer) lifetime\nfor their refresh token, which could be used to sign out web sessions\nwith a specific timeout.\n\nOpen questions are mostly if there should be a maximum refresh token\nlifetime someone could configure and if this should also be configurable\non login. The latter doesn't seem as necessary, since a client can just\nrefresh immediately after login (although that is racy).\n\nOnce we figure out a nice behaviour for this, we should also write an\nMSC. For now this is just an experiment.","shortMessageHtmlLink":"Allow clients to configure when a refresh token expires"}},{"before":"605cebd5caf6d548ac14e0c66e5bc3401e8fcf32","after":"030bc3149999eb7a2124ee0f0fe67836608aa6bb","ref":"refs/heads/master","pushedAt":"2024-06-27T13:53:26.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"emgrav","name":"Emelie Graven","path":"/emgrav","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/614975?s=80&v=4"},"commit":{"message":"Allow clients to configure when a refresh token expires\n\nThis allows clients to pass an extra parameter when refreshing a token,\nwhich overrides the configured refresh token timeout in the Synapse\nconfig. This allows a client to opt into a shorter (or longer) lifetime\nfor their refresh token, which could be used to sign out web sessions\nwith a specific timeout.\n\nOpen questions are mostly if there should be a maximum refresh token\nlifetime someone could configure and if this should also be configurable\non login. The latter doesn't seem as necessary, since a client can just\nrefresh immediately after login (although that is racy).\n\nOnce we figure out a nice behaviour for this, we should also write an\nMSC. For now this is just an experiment.","shortMessageHtmlLink":"Allow clients to configure when a refresh token expires"}},{"before":"d2dfc5448e0632cd15573b32fc252cb80b877333","after":"605cebd5caf6d548ac14e0c66e5bc3401e8fcf32","ref":"refs/heads/master","pushedAt":"2024-06-10T12:00:53.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"nico-famedly","name":"Nicolas Werner","path":"/nico-famedly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/89468146?s=80&v=4"},"commit":{"message":"Allow clients to configure when a refresh token expires\n\nThis allows clients to pass an extra parameter when refreshing a token,\nwhich overrides the configured refresh token timeout in the Synapse\nconfig. This allows a client to opt into a shorter (or longer) lifetime\nfor their refresh token, which could be used to sign out web sessions\nwith a specific timeout.\n\nOpen questions are mostly if there should be a maximum refresh token\nlifetime someone could configure and if this should also be configurable\non login. The latter doesn't seem as necessary, since a client can just\nrefresh immediately after login (although that is racy).\n\nOnce we figure out a nice behaviour for this, we should also write an\nMSC. For now this is just an experiment.","shortMessageHtmlLink":"Allow clients to configure when a refresh token expires"}},{"before":null,"after":"18e83c25ebbc880d1fe8869d85fed0af0151ce21","ref":"refs/heads/nikzen-patch-1","pushedAt":"2024-06-07T12:26:41.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"nikzen","name":"Niklas Zender","path":"/nikzen","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33399346?s=80&v=4"},"commit":{"message":"chore: update version of sta and sic","shortMessageHtmlLink":"chore: update version of sta and sic"}},{"before":"3ce9fb53504050dafa80dcc24e219d510f7d3c67","after":"d2dfc5448e0632cd15573b32fc252cb80b877333","ref":"refs/heads/master","pushedAt":"2024-06-06T15:04:24.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"nico-famedly","name":"Nicolas Werner","path":"/nico-famedly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/89468146?s=80&v=4"},"commit":{"message":"chore: pin invite checker version (#12)","shortMessageHtmlLink":"chore: pin invite checker version (#12)"}},{"before":"e6ebac172f1ba2d5e9ecc9675a994f8780cda8c0","after":"3ce9fb53504050dafa80dcc24e219d510f7d3c67","ref":"refs/heads/master","pushedAt":"2024-06-06T15:03:18.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"nico-famedly","name":"Nicolas Werner","path":"/nico-famedly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/89468146?s=80&v=4"},"commit":{"message":"chore: pin invite checker version (#12)","shortMessageHtmlLink":"chore: pin invite checker version (#12)"}},{"before":null,"after":"1d67c6f148575f10b0953e43a7f50e3d905fec51","ref":"refs/heads/pin-version","pushedAt":"2024-06-05T10:00:30.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"nikzen","name":"Niklas Zender","path":"/nikzen","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33399346?s=80&v=4"},"commit":{"message":"chore: pin invite checker version","shortMessageHtmlLink":"chore: pin invite checker version"}},{"before":null,"after":"e6ebac172f1ba2d5e9ecc9675a994f8780cda8c0","ref":"refs/heads/release-v1.108","pushedAt":"2024-05-30T11:08:31.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"nico-famedly","name":"Nicolas Werner","path":"/nico-famedly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/89468146?s=80&v=4"},"commit":{"message":"Allow clients to configure when a refresh token expires\n\nThis allows clients to pass an extra parameter when refreshing a token,\nwhich overrides the configured refresh token timeout in the Synapse\nconfig. This allows a client to opt into a shorter (or longer) lifetime\nfor their refresh token, which could be used to sign out web sessions\nwith a specific timeout.\n\nOpen questions are mostly if there should be a maximum refresh token\nlifetime someone could configure and if this should also be configurable\non login. The latter doesn't seem as necessary, since a client can just\nrefresh immediately after login (although that is racy).\n\nOnce we figure out a nice behaviour for this, we should also write an\nMSC. For now this is just an experiment.","shortMessageHtmlLink":"Allow clients to configure when a refresh token expires"}},{"before":"bfd6b12877f9869976537804240bdd1af3731ba6","after":"e6ebac172f1ba2d5e9ecc9675a994f8780cda8c0","ref":"refs/heads/master","pushedAt":"2024-05-30T11:08:28.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"nico-famedly","name":"Nicolas Werner","path":"/nico-famedly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/89468146?s=80&v=4"},"commit":{"message":"Allow clients to configure when a refresh token expires\n\nThis allows clients to pass an extra parameter when refreshing a token,\nwhich overrides the configured refresh token timeout in the Synapse\nconfig. This allows a client to opt into a shorter (or longer) lifetime\nfor their refresh token, which could be used to sign out web sessions\nwith a specific timeout.\n\nOpen questions are mostly if there should be a maximum refresh token\nlifetime someone could configure and if this should also be configurable\non login. The latter doesn't seem as necessary, since a client can just\nrefresh immediately after login (although that is racy).\n\nOnce we figure out a nice behaviour for this, we should also write an\nMSC. For now this is just an experiment.","shortMessageHtmlLink":"Allow clients to configure when a refresh token expires"}},{"before":null,"after":"bfd6b12877f9869976537804240bdd1af3731ba6","ref":"refs/heads/release-v1.107","pushedAt":"2024-05-21T16:32:03.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"nico-famedly","name":"Nicolas Werner","path":"/nico-famedly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/89468146?s=80&v=4"},"commit":{"message":"Allow clients to configure when a refresh token expires\n\nThis allows clients to pass an extra parameter when refreshing a token,\nwhich overrides the configured refresh token timeout in the Synapse\nconfig. This allows a client to opt into a shorter (or longer) lifetime\nfor their refresh token, which could be used to sign out web sessions\nwith a specific timeout.\n\nOpen questions are mostly if there should be a maximum refresh token\nlifetime someone could configure and if this should also be configurable\non login. The latter doesn't seem as necessary, since a client can just\nrefresh immediately after login (although that is racy).\n\nOnce we figure out a nice behaviour for this, we should also write an\nMSC. For now this is just an experiment.","shortMessageHtmlLink":"Allow clients to configure when a refresh token expires"}},{"before":"7598dd4191528fefdd7d0835d41abdb4fdbe98fa","after":"bfd6b12877f9869976537804240bdd1af3731ba6","ref":"refs/heads/master","pushedAt":"2024-05-21T16:32:01.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"nico-famedly","name":"Nicolas Werner","path":"/nico-famedly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/89468146?s=80&v=4"},"commit":{"message":"Allow clients to configure when a refresh token expires\n\nThis allows clients to pass an extra parameter when refreshing a token,\nwhich overrides the configured refresh token timeout in the Synapse\nconfig. This allows a client to opt into a shorter (or longer) lifetime\nfor their refresh token, which could be used to sign out web sessions\nwith a specific timeout.\n\nOpen questions are mostly if there should be a maximum refresh token\nlifetime someone could configure and if this should also be configurable\non login. The latter doesn't seem as necessary, since a client can just\nrefresh immediately after login (although that is racy).\n\nOnce we figure out a nice behaviour for this, we should also write an\nMSC. For now this is just an experiment.","shortMessageHtmlLink":"Allow clients to configure when a refresh token expires"}},{"before":"75a44e0dfcaa9532b80aed71873c9245d7a635c9","after":"7598dd4191528fefdd7d0835d41abdb4fdbe98fa","ref":"refs/heads/master","pushedAt":"2024-05-13T15:39:35.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"jcgruenhage","name":"Jan Christian Grünhage","path":"/jcgruenhage","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6861958?s=80&v=4"},"commit":{"message":"Allow clients to configure when a refresh token expires\n\nThis allows clients to pass an extra parameter when refreshing a token,\nwhich overrides the configured refresh token timeout in the Synapse\nconfig. This allows a client to opt into a shorter (or longer) lifetime\nfor their refresh token, which could be used to sign out web sessions\nwith a specific timeout.\n\nOpen questions are mostly if there should be a maximum refresh token\nlifetime someone could configure and if this should also be configurable\non login. The latter doesn't seem as necessary, since a client can just\nrefresh immediately after login (although that is racy).\n\nOnce we figure out a nice behaviour for this, we should also write an\nMSC. For now this is just an experiment.","shortMessageHtmlLink":"Allow clients to configure when a refresh token expires"}},{"before":"8ea6bd049e47af49c58e90c1a60200a8e4996706","after":"ea28f4b6a2295a10355ba6c474e58b3f2534e469","ref":"refs/heads/pin-sta-version","pushedAt":"2024-05-13T13:57:05.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"nikzen","name":"Niklas Zender","path":"/nikzen","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33399346?s=80&v=4"},"commit":{"message":"chore:update version","shortMessageHtmlLink":"chore:update version"}},{"before":null,"after":"8ea6bd049e47af49c58e90c1a60200a8e4996706","ref":"refs/heads/pin-sta-version","pushedAt":"2024-05-13T13:39:43.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"nikzen","name":"Niklas Zender","path":"/nikzen","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/33399346?s=80&v=4"},"commit":{"message":"chore: pin sta version","shortMessageHtmlLink":"chore: pin sta version"}},{"before":null,"after":"75a44e0dfcaa9532b80aed71873c9245d7a635c9","ref":"refs/heads/release-v1.106","pushedAt":"2024-05-08T16:26:08.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"nico-famedly","name":"Nicolas Werner","path":"/nico-famedly","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/89468146?s=80&v=4"},"commit":{"message":"Allow clients to configure when a refresh token expires\n\nThis allows clients to pass an extra parameter when refreshing a token,\nwhich overrides the configured refresh token timeout in the Synapse\nconfig. This allows a client to opt into a shorter (or longer) lifetime\nfor their refresh token, which could be used to sign out web sessions\nwith a specific timeout.\n\nOpen questions are mostly if there should be a maximum refresh token\nlifetime someone could configure and if this should also be configurable\non login. The latter doesn't seem as necessary, since a client can just\nrefresh immediately after login (although that is racy).\n\nOnce we figure out a nice behaviour for this, we should also write an\nMSC. For now this is just an experiment.","shortMessageHtmlLink":"Allow clients to configure when a refresh token expires"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"Y3Vyc29yOnYyOpK7MjAyNC0wOS0wNVQxNTo1OTozMS4wMDAwMDBazwAAAASuC70S","startCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wOS0wNVQxNTo1OTozMS4wMDAwMDBazwAAAASuC70S","endCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wNS0wOFQxNjoyNjowOC4wMDAwMDBazwAAAARE1UxS"}},"title":"Activity · famedly/synapse"}