Ticket Login for Applications #170
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It's now more intelligent to not return SwiftLeeds on the KotlinLeeds API and vice versa
Right now if you knew the ID of a SwiftLeeds event you could request it from the KotlinLeeds domain, I don't like that
github-actions
bot
temporarily deployed
to
kotlinleeds-login-stuff
github-actions
bot
temporarily deployed
to
kotlinleeds-login-stuff
adamrushy
reviewed
Nov 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@adamrushy please use Cloudflare to define a strict rate limit on the endpoints of
/api/v1/login/ticketin both Kotlin and Swift domains. (https://developers.cloudflare.com/waf/rate-limiting-rules/create-zone-dashboard/)