Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make SwiftarrClientApp mean something #132

Open
cohoe opened this issue Feb 14, 2023 · 3 comments
Open

Make SwiftarrClientApp mean something #132

cohoe opened this issue Feb 14, 2023 · 3 comments
Labels
enhancement New feature or request

Comments

@cohoe
Copy link
Member

cohoe commented Feb 14, 2023

We have some kind of differentiation for clients.

public enum SwiftarrClientApp: String, Content, CaseIterable {

We should do something with it.

@cohoe cohoe added the enhancement New feature or request label Feb 14, 2023
@cohoe
Copy link
Member Author

cohoe commented Feb 26, 2023

Consider a X-Swiftarr-Client header required for any API client. Not the most secure, but gets the job done.

@cohoe
Copy link
Member Author

cohoe commented Mar 14, 2023

Add this header to the INFO log string. Very helpful for debugging.

@cohoe
Copy link
Member Author

cohoe commented Nov 24, 2023

Expanding on my own commentary, we currently delegate responsibility to the clients to "turn themselves off" when we disable a feature/client. I don't love this as it's basically client-side security. However it's probably fine?

Adding the X-Swiftarr-Client header would be nice to get a sense of client proportions. Should be an easy insert for the site UI here:

cohoe added a commit to cohoe/swiftarr that referenced this issue Jan 9, 2024
cohoe added a commit that referenced this issue Jan 18, 2024
* resolve #189, you spin me right round

* resolves #250, partially addresses #135

* resolves #214, adds pagination to moderator log

* resolves #177, allows admin and tho in site ui with certain disable conditions

* resolves #135, adds about processing via api

* resolves #239, fixes pagination for joined fez and mod log

* resolves #251, brings back new und alertwords and makes UI less surprising

* The guts for #136

* more seamail muting

* resolves #136, finalized mute of seamail I think

* resolves #182, adds support for accessing mentions of twitarrteam and moderator

* #206 bumps up minimum Vapor version, adds notes for concurrency checking

* resolves #216, fixes seamail unread for special users (I think)

* add dummy schedule generator

* resolves #240, makes all lfgs not be perma-unread for moderators

* resolves #173, implements late day flip setting

* resolves #211, adds release calendar documentation

* #132 make the site ui identify itself

* comment

* resolves #183, enables one context button for lfg and seamail

* resolves #179, make open chat the default state

* resolves #176, adds links to profiles for seamail participants

* resolves #217, adds unread forum handlers

* resolves #168, site ui marks new forum read for creator

* resolves #199, correct forum counts after calendar update

* resolves #188, adds team field to user profile

* resolves #180, improves page titles for most common things

* resolves #181, improves user mention and hashtag detection

* resolves #210, moves preferredPronoun to UserHeader for wide consumability

* add username to profile page titles

* continues #231 add timeZoneID to FezData and ForumListdata to match EventData

add timezoneID to forumlistdata like fezdata and eventdata

* improve pronoun display by limiting to useful contexts

* improve pronoun display by limiting to useful contexts

* improve pronoun display with no displayname

* resolves #167, adds view forum posts by user to mods

* dedicated jobs for event schedule update

* address occasional redis connection timeouts
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant