Agreed, such a great structure in NYC's skyline. Lived on 73 for a few years. The contoured windows and benches inside were just as fun as the exterior.
Still don't understand why they stuck a red brick school in the middle and didn't contour it with the stainless steel panels like the rest of the building.
I toured that building when I was looking for a place, and just so happened to be there when there was recess or something. The loud noise of kids was definitely a significant factor in me not signing a lease.
> The big problem that we kept running into was keeping everything in sync all the time. Every time we add a new user, organization, repository, etc. in our database, we also had to add the corresponding tuples in OpenFGA.
This is a fundamental problem with all Zanzibar-inspired authorization systems[0] that require centralizing ~all authorization data and led us @ Oso to build a more flexible system[1] that grants more control over what authorization-relevant data you centralize vs. decide keep locally.
Yes, similar discussion across two separate articles:
(1) article from General Analysis on "Supabase MCP can leak your entire SQL database"
(2) article from Oso talking about why authorization in AI is hard, what to do about it, which references the General Analysis article
Right, because otherwise you end up with a split discussion and people miss stuff, moderators end up having to merge them, etc. Immediate followups count as dupes (in HN's weird dupery algebra), they're better off linked in the active thread.
reply