AYRT, I've stared at this response for over five minutes and still don't get how you got "headcanoning lore for a dragon you don't own" out of saving a backup of your writing.
Because I don't see how having written down lore matters at all for a dragon you don't own. I don't see how writing down your lore has any impact on lore other people have written for a dragon you don't own.
You can save a backup of your own writing, that's pretty good practice to have, especially on the internet... but that's not a *solution* to the problem of, to paraphrase the above, 'someone else wrote lore I don't like'. Writing down your own lore is tangential to the topic at hand.
To phrase it another way... The topic is Person A has lore and sold a Lore Dragon to Person B. Person B changed that lore in a way that Person A did not like (in a non-rulebreaking way to simplify things). How does having a backup of the lore that was on the Lore Dragon help this situation?
My interpretation would be that because Person A has their own version of the lore that was on the Lore Dragon they can refer back to that whenever they get upset about Person B's lore, even though Person B's lore is the new canon for that dragon since it is now theirs (hence the headcanon comment). If Person A has their own lore to refer to, technically it doesn't really matter if they have it written down though? How does having a written backup as opposed to ideas floating around in your head really help in this matter? (The original "solution #1" specified that ideas floating in your head did not count. Why is this, what makes them significantly different than a physical backup in this situation? That's my issue.)
I actually do not think the original issue was that. That's what some people turned it to.
It more read as User A sells dragon to user B. Not a lore dragon or anything. Just a dragon. User B writes edgelord lore in dragon's profile saying User A's clan is abusers or sells their kids into slavery which upsets user A. There was nothing about deleting lore from the dragon.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png){kind=small}
Re: SMR Lore Salt
(Anonymous) 2024-12-19 05:07 pm (UTC)(link)Re: SMR Lore Salt
(Anonymous) 2024-12-20 02:02 pm (UTC)(link)You can save a backup of your own writing, that's pretty good practice to have, especially on the internet... but that's not a *solution* to the problem of, to paraphrase the above, 'someone else wrote lore I don't like'. Writing down your own lore is tangential to the topic at hand.
Re: SMR Lore Salt
(Anonymous) 2024-12-20 02:31 pm (UTC)(link)To phrase it another way... The topic is Person A has lore and sold a Lore Dragon to Person B. Person B changed that lore in a way that Person A did not like (in a non-rulebreaking way to simplify things). How does having a backup of the lore that was on the Lore Dragon help this situation?
My interpretation would be that because Person A has their own version of the lore that was on the Lore Dragon they can refer back to that whenever they get upset about Person B's lore, even though Person B's lore is the new canon for that dragon since it is now theirs (hence the headcanon comment). If Person A has their own lore to refer to, technically it doesn't really matter if they have it written down though? How does having a written backup as opposed to ideas floating around in your head really help in this matter? (The original "solution #1" specified that ideas floating in your head did not count. Why is this, what makes them significantly different than a physical backup in this situation? That's my issue.)
Re: SMR Lore Salt
(Anonymous) 2024-12-20 04:26 pm (UTC)(link)It more read as User A sells dragon to user B. Not a lore dragon or anything. Just a dragon. User B writes edgelord lore in dragon's profile saying User A's clan is abusers or sells their kids into slavery which upsets user A. There was nothing about deleting lore from the dragon.