Hacker Newsnew | past | comments | ask | show | jobs | submit | forks's commentslogin

Worked fine on Safari on macOS.

> Processing begins August 1, 2026.

By that time the data brokers might have sold off the data to others outside USA. may they already have. This is just US law, it will not affect India, China, Russia, etc data brokers

Out of curiosity, why does the Algolia result for this submission show '4 days ago', the submission timestamp '3 hours ago', and the metadata on the submission timestamp '2025-12-18T15:34:11 1766072051'?

Is this an example of an article being resubmitted (by the same user?) or otherwise boosted back onto the front page?



Ah neat, thank you for sharing!


RIP. 8 Spruce is a personal favorite.


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.


If you click through to the article shared yesterday[0]:

> Microsoft denies report of lowering targets for AI software sales growth

This Ars Technica article cites the same reporting as that Reuters piece but doesn't (yet) include anything about MSFT's rebuttal.

[0]: https://news.ycombinator.com/item?id=46135388


Semantics + Spin


> Remember: Always disable sourcemaps in production!

I wish I could downvote this comment from the README.

Minification to reduce bandwidth is noble. But to obfuscate? Why?


> 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.

0: https://www.osohq.com/post/authorization-for-the-rest-of-us

1: https://www.osohq.com/docs/develop/facts/local-authorization

disclosure: founding engineer at Oso



Comments moved thither. Thanks!


- Polar, the authorization DSL created by Oso

It's a common name


So, back to BM25?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: