Hey, I’ve noticed that when working on some large notebooks I sometimes break smaller sub notebooks off during refactoring. I also sometimes take my own notebooks, fork them, and spinn them off into completely different directions. It would be really nice if I could remove the fork information, b…

Yes, there’s nothing preventing you from deleting your notebook whenever you like. The license grant to other users in the terms of service simply means that by publishing, you’re allowing other users to make copies of your published content, say by forking or importing. When you delete your noteboo…

Related: Notebook clone instead of fork Unfork

You can already copy a notebook without creating a fork, because any two notebooks can be merged . The steps are not intuitive, so bear with me: Open the notebook that you want to copy. This is the ORIGINAL. Access the notebook ID: for private or shared notebooks: The part in the URL after “/d/”. f…

Nice Hack! But so close, yet so far, as the notebooks are already published, their URL is already burned :confused: So it’s either the annoying fork, or the annoying notebook/2 thing. I find the reasoning behind all of this pseudo persistence to be really lacking. If they don’t want to have you …

[image] j-pb: So it’s either the annoying fork, or the annoying notebook/2 thing. I’m not following. You can give the new notebook (and any fork) any unused URL you like. The slug (URL version of the notebook title) is generated from the first <h1> that Observable finds in your notebook the m…

Yeah but I don’t like any unused URL :wink: I like the one it has :smiley:

I see, you’re talking about published forks. Yeah, those are a lost cause (for the moment).

[image] mootari: Afaik they’re already working on that (notebooks staying accessible, automatic version pinning). Tbh I don’t see how they could implement this in any meaningfully legal way. They don’t own the licence to the stuff uploaded, so if you change your mind and unpublished it, it h…

[image] j-pb: They don’t own the licence to the stuff uploaded, so if you change your mind and unpublished it, it has to go. You might want to reread the terms that you agreed to when you signed up. :wink:

Excerpts from the licence agreement. We need these rights for both public and private notebooks because these rights are necessary for providing the Service. This license does not grant Observable the right to sell Your Content or otherwise distribute or use it outside of our provision of the Se…

[image] j-pb: Even GDPR alone should completely safeguard you from this. The GDPR covers personal data, i.e., personally identifiable information. I’m fairly certain that it doesn’t cover copyright. Be that as it may, let’s not derail the discussion further. Should this feature require changi…

Feature Request: Allow the Removal of Fork Inheritance

Feedback

mootari May 2, 2020, 12:29pm 2

Notebook clone instead of fork
Unfork

Topic		Replies	Views
Unfork	8	2051	January 25, 2020
Forks of link-shared notebooks are not marked as fork Feedback	11	1030	July 25, 2021
Remove time limit on unsharing public notebook Feedback	6	1076	January 7, 2020
Feature request: import observablehq js notebook as New Feedback	2	501	August 29, 2018
lost notebook Community Help	8	1669	September 17, 2018

Feature Request: Allow the Removal of Fork Inheritance

Related topics