-
Notifications
You must be signed in to change notification settings - Fork 554
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
Remove scenes #483
Remove scenes #483
Conversation
@@ -14,15 +14,7 @@ export default function (server: Server, ctx: AppContext) { | |||
server.app.bsky.actor.updateProfile({ | |||
auth: ctx.accessVerifierCheckTakedown, | |||
handler: async ({ auth, input }) => { | |||
const requester = auth.credentials.did | |||
|
|||
const did = input.body.did || requester |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would not mind getting rid of these did
inputs! I don't think we have a use for them now, and I think we sort of want to redesign that bit of auth anyway next time we come across the same use-case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah yeah that's not a bad idea.
would clean things up & they're the type of param we can add in later (or solve w the auth system)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, and I support keeping assertions and confirmations around. Slightly tempting to keep the getAssertions
endpoint around, even, but I think you did the right thing 👍
* wip * wip * remove getAssertions & fix up notifs test * remove did param on updateProfile
Removing scenes & trends from the PDS.
This also removes the views for getAssertions & getMembers(hips) along with notifications for assertions, however it leaves behind the lexicons for assertion & confirmation records. I'm not opposed to removing those also, but they seem like the most likely candidate to be worked back in soon.
For those listening in: Scenes will be making a comeback! However at the current moment they're a little half-baked & we want to be sure to flesh out the concept a bit before committing to it feature-wise
Not included in this PR:
Have plans to do those in a subsequent PR shortly