Wen Bo Xie

@dshukertjr thanks, definitely something to ponder. We can revisit this when [Enable filters for delete events supabase/realtime#53](https://github.com/supabase/walrus/issues/53) is prioritized. I'll move this over to the `walrus` repo since the changes...

@joshenlim yep, will need this in pg-meta but then we'll need to update the pg-meta functions api in studio to pass in `excludedSchemas`.

@WilliamFalci as an alternative, what if we just overwrite specific configs like: https://github.com/supabase/supabase/pull/5481/files#diff-423deb13b7c401b1a7f41ee91c77f722e11d2f317d6a66b546524e8a04cc8b03R150

> This should be at least clearly documented, it created a major in production for my mobile app... @christophemenager great call, i'll let our Realtime team know and we'll add...

Closing this b/c it's been implemented: https://github.com/supabase/walrus/pull/63. If you would like to use this in Realtime you can check out https://github.com/supabase/realtime/issues/401#issuecomment-1413111707.

@KineticFox feel free to reopen if you're still blocked.

> Putting this here too for comms. It is handling outbound messages already Ah, you're right. It was just non-obvious to me as it was hidden by the catchall of...

@ecchochan thanks for your contribution! this looks great. ~can we keep it simpler for the initial version and just check for the `alg` from the JWT header?~ never mind, see:...

@acupofjose thanks for reporting! we're aware of this issue and we're tracking it here: https://github.com/supabase/walrus/issues/53

@rlee1990 thanks for the feature request! Just to clarify, do you mean a range filter? for example, a client wants to only receive changes when `id` is between 1 and...