Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics. If you need to do this, try [email protected]
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
There are two main theories about why dreams occur.
(Explained in computing terms)
First is scheduled maintenance.
Your brain essentially runs a defrag when you dream, trimming useless information. Most times, you forget about the dream, but other times you'll wonder why you recalled that memory from 15 years ago. Your brain needs to inspect the file before sending it to the trash, but you managed to recover it before it got zeroed (unrecoverable).
Second is threat model assessment.
Your brain is randomly compiling memories while you dream, scanning for useful information. Sometimes a certain combination will leave a strong impression, which gets cached (saved to RAM). These memories are usually bad, and get saved to disk because we're slow at debugging, but are invested in fixing it to avoid a kernel panic (blue screen). We spend so much time thinking about it, that the bad memory's directory gets added to $PATH(bookmarked)
Sleep is where the multiverses meet, man.