The data model behind Notion's flexibility (2021)
notion.soLanguage based redirect is useless when the article doesn't exits in that language.
My `Accept-Language` looks like `en-GB,de-DE;q=0,8,…` and for some reason Notion:
The HTTP semantics RFC[1] is quite clear that an unqualified value should be equivalent to 1.0, and I don't think content negotiation should ever prefer a non-existent resource to one that exists.- interprets this as me preferring German - tries to retrieve a non-existent German version of the page[1]: https://www.rfc-editor.org/rfc/rfc9110#field.accept-language
Sorry about that, will investigate
Notion’s data model is so good and the UI is great. I have read their privacy/data collection terms and it’s borderline acceptable. But it leaves a bad taste on my tongue whey I learned that they never wanted to implements e2ee with some bs explanation.
Author here, happy to answer questions. You can also email me at jake@makenotion.com
Were there substantial changes to the data model? Especially in terms of how child ordering works
Related question: if there were no changes, for instance, because it is too costly to change it now, would you choose a different model for this now?
Awesome. Is it possible to put this into Claude 3 Opus and create an open source import and rendering system? Or is that already a thing.
I would think that used together, the block model and RFC 1896 make a pretty complete setup.
This is great and all but notion is slow. After being a paying user for a number of years, i pulled the plug because of its atrocious performance.
Should add (2021)
Site not found…