diff --git a/index.html b/index.html index 7de7040..21dadb2 100644 --- a/index.html +++ b/index.html @@ -30,10 +30,10 @@ polyphasic URL shortener. You can use it too for quick navigation: For schedules, write eep.li/<schedule name>, and for snippets, write eep.li/!<name>. Schedules are parsed in great detail and unified, so any notation a human can understand will almost -certainly work. /e3ext, /e3e, /eex, /everyman-3-extended, etc, all -work to redirect you to [[+E3-Extended]]. To see the interpretation -of eep.li, add an ampersand before the schedule name to simply get -the expanded and shortened name back. +certainly work. /m3ext, /m3e, /mex, /monoco3, /everyman-3-extended, +etc, all work to redirect you to [[+M3-Extended]]. To see the +interpretation of eep.li, add an ampersand before the schedule name +to simply get the expanded and shortened name back.

Contributing

diff --git a/schedule/M0.html b/schedule/M0.html index b545462..e4ae126 100644 --- a/schedule/M0.html +++ b/schedule/M0.html @@ -1,18 +1,20 @@ <
> -

Monophasic

+

[[!MonoCore]] 0 / Monophasic

-Monophasic sleep is, together with [[+Segmented-Extended]] and +Mono refers to this schedule (M0), NOT the MonoCore lineup. +

+Monophasic sleep is, together with [[+DC0-Extended]] and [[+Siesta-Extended]] (though also possibly others) one of the natural sleeping patterns of humans. It reached widespread adoption in the western world during the industrial revolution, as a result of -unforgiving jobs with long hours, where [[+SegEx]] used to be more +unforgiving jobs with long hours, where [[+DC0e]] used to be more common.

- - - + + + @@ -25,8 +27,8 @@ restore all of the required sleep for a day within a single phase.

Difficulty

-Some people may have trouble with Mono, which can be due to being pre- -programmed for [[!biphasic]] sleep (usually [[+SegEx]]). Other times, +Some people may have trouble with mono/M0, which can be due to being pre- +programmed for [[!biphasic]] sleep (usually [[+DC0ext]]). Other times, the environment may not be conducive to [[!consistent]] mono or not allow for one sleep phase of enough length at once.

diff --git a/schedule/M0rec.html b/schedule/M0rec.html deleted file mode 100644 index 7302b8f..0000000 --- a/schedule/M0rec.html +++ /dev/null @@ -1,5 +0,0 @@ -<

> - - -

Redirecting to [[!MonoRec]]

- diff --git a/schedule/M0sho.html b/schedule/M0sho.html index 47b96e4..ee39319 100644 --- a/schedule/M0sho.html +++ b/schedule/M0sho.html @@ -1,6 +1,6 @@ <
> -

Mono-Shortened

+

[[!MonoCore]]-0-Shortened / Mono-Shortened

In people with [[!RSR]], [[+mono]] may be shortened compared to the normal 7-9h and still be fully restorative (at the very least with [[!DP]]). diff --git a/schedule/M1.html b/schedule/M1.html index f2d3dea..630e785 100644 --- a/schedule/M1.html +++ b/schedule/M1.html @@ -1,8 +1,9 @@ <
> -

[[!Everyman]] 1

+

[[!MonoCore]] 1

-[[!Everyman]] 1 is a [[!biphasic]] schedule in the reducing [[!Everyman]] +[[!MonoCore]] 1 is a [[!biphasic]] schedule in the reducing [[!Everyman]] +(here referred to as MonoCore for consistency with other schedules) lineup created by Puredoxyk in Ubersleep (see [[!naps]]). It removes one cycle of sleep from the default 7.5h [[!core]] and replaces it with a [[!nap]]. As a biphasic schedule, it is one of the best for beginners. @@ -19,12 +20,12 @@ cycle of sleep from the default 7.5h [[!core]] and replaces it with a

Mechanism

As described in [[!Naps]], the nap is meant to largely replace one -of the [[!core]] cycles. In E1, it often does not contain [[!vitals]], +of the [[!core]] cycles. In M1, it often does not contain [[!vitals]], simply restoring some homeostatic [[!pressure]].

Difficulty

-As a biphasic schedule with TST above 6h, E1 is quite easy to [[!adapt]] +As a biphasic schedule with TST above 6h, M1 is quite easy to [[!adapt]] to. While not [[!non-reducing]], it is a very low reduction and no [[!repartition]] of [[!vitals]] into the nap is necessary for most. This means the adaptation only relies on reducing [[!light-sleep]] @@ -33,21 +34,21 @@ point of failure.

*However:

Some people also have more difficulty than with more reducing -[[!everyman]] schedules like [[+E3ext]] or [[+E2]]; due to the low -amount of sleep debt accumulation in E1, the required threshold for +[[!monocore]] schedules like [[+M3ext]] or [[+M2]]; due to the low +amount of sleep debt accumulation in M1, the required threshold for [[!stage-3]], and thereby adaptation, might never be reached, leaving one stuck in [[!stage-2]]. [[!DualCore]] schedules, especially -[[+Segmented]] are a great alternative if this happens. +[[+DC0]] are a great alternative if this happens.

-In people with [[!RSR]], E1 often turns into [[+Mono-Shortened]] -or [[+Biphasic-X-Shortened]]. +In people with [[!RSR]], M1 often turns into [[+M0-Shortened]] +or [[+MX-Shortened]].

Adaptation

-[[!Adaptation]] to E1 from [[+Mono]] is best done cold turkey - just +[[!Adaptation]] to M1 from [[+Mono]] is best done cold turkey - just jump in, don't skip a night, and don't do any kind of gradual change.

Extension

-[[+E1-Extended]] is largely only useful if you have increased sleep -requirements, otherwise, [[+Biphasic-X]] is far preferable. +[[+M1-Extended]] is largely only useful if you have increased sleep +requirements, otherwise, [[+MX]] (aka. [[+Biphasic-X]]) is far preferable. diff --git a/schedule/M3.html b/schedule/M3.html index 22dc60c..879195e 100644 --- a/schedule/M3.html +++ b/schedule/M3.html @@ -1,9 +1,10 @@ <
> -

[[!Everyman]] 3

+

[[!MonoCore]] 3

-[[!Everyman]] 3 is a [[!single-core]] schedule with a 3h core, usually in -the [[!SWS]] peak. It was invented by Puredoxyk and is extremely or +[[!MonoCore]] 3 is a schedule with a 3h [[!core]], usually in +the [[!SWS]] peak. It was invented by Puredoxyk as [[+Everyman]], +later [[!E3]], now [[!M3]], and is extremely or impossibly difficult for people with around-average sleep needs.
TST8h ± 1h
Cores1
Naps0
[[!TST]]8h ± 1h
[[!Cores]]1
[[!Naps]]0
[[!Difficulty]]0 / 5
[[!RSR]] [[!Difficulty]]0-1 / 5
Flex-potentialNatural
@@ -17,25 +18,27 @@ impossibly difficult for people with around-average sleep needs.

(Im)possibility

-Unlike what past messaging suggests, to the majority of individuals, E3 is not +Unlike what past messaging suggests, to the majority of individuals, M3 is not [[!adaptable]]. This is because its total sleep time is too low for most to gain all of their vitals given 20-40% minimum [[!light-sleep]]. Individuals with [[!RSR]] may attempt this schedule and have a decent chance of succeeding.

-A more detailed explanation can be found at [[!E3impossible]]. +A more detailed explanation can be found at [[!M3impossible]].

3.5h Variant

-Originally, this variant was called E3.5, but is now referred to as E3 as +Originally, this variant was called E3.5, but is now referred to as M3 as well. Here, the core is extended to 3h30, resulting in 4h30 of [[!TST]]. This variant has a [[!difficulty]] of 4/5 instead of 5/5, being possible for some people without [[!RSR]].

Extension

-Extension can make E3 much more viable, in the form of [[+E3ext]]. +Extension can make M3 much more viable, in the form of [[+M3ext]].

Origin

This schedule is based on [[!nap]] theory and was coined by Puredoxyk. It -was originally just called Everyman. +was originally just called Everyman before being termed Everyman 3 (based +on the 3h core) and then Everyman 3 (based on the number of naps). Polyinfo +refers to it as MonoCore 3 for consistency with other names and clarity. diff --git a/schedule/M3e.html b/schedule/M3e.html index d203be6..2deddf7 100644 --- a/schedule/M3e.html +++ b/schedule/M3e.html @@ -1,8 +1,8 @@ <
> -

Everyman 3 Extended

+

[[!MonoCore]](/Everyman) 3 Extended

-A variant of [[+Everyman-3]] that contains a 4.5 hour core (like [[+E2]]), +A variant of [[+MonoCore-3]] that contains a 4.5 hour core (like [[+M2]]), that is most commonly placed starting at midnight.
diff --git a/snippet/biphasic.html b/snippet/biphasic.html index 5b3c2be..066ebd6 100644 --- a/snippet/biphasic.html +++ b/snippet/biphasic.html @@ -4,15 +4,15 @@ Biphasic schedules are the easiest polyphasic schedules you can choose. These may consist of two cores, or one core and one nap, in which case -they are also [[!Everyman]] schedules. +they are also classified as [[!MonoCore]] schedules.

These are the tested and working ones:

diff --git a/snippet/dp.html b/snippet/dp.html index dcac286..cc541af 100644 --- a/snippet/dp.html +++ b/snippet/dp.html @@ -6,10 +6,10 @@ Dark Period is the practice of not letting any blue or green light enter your eyes, and it is usually practiced from before the first [[!core]] until the end of the next sleep at least 7h after the start.

-In schedules like [[+E1]], this means DP is only done before the core, +In schedules like [[+M1]], this means DP is only done before the core, because the core end is already >7h after the start of DP.

-In schedules like [[+E2]], this means DP lasts from before the core until +In schedules like [[+M2]], this means DP lasts from before the core until the end of N1.

Here's a way to determine when to end: diff --git a/snippet/e3impossible.html b/snippet/e3impossible.html index 5c349eb..74bb362 100644 --- a/snippet/e3impossible.html +++ b/snippet/e3impossible.html @@ -1,29 +1,4 @@ <

> -

[[+E3]] and average sleep needs

- -If you’re an average person, you need between 7-9 hours of [[+monophasic]] -sleep, which contains on average between 90-120 minutes of slow wave -sleep, and 90-120 minutes of [[!REM]]. Together this accounts for an -average of 210m of [[!vital]] sleep (vital meaning necessary), which -is more than the base [[+E3]] [[!core]]’s length. -

-The average person cannot easily reduce their [[!light-sleep]] percentage -below 50-20%, meaning that if you achieve the (highly unlikely) -minimum of 20%, you’d need to fit 210m of [[!vitals]] into the remaining -144m of core sleep, which is obviously not mathematically possible. -

-It is possible you could also get [[!REM]] in your [[!naps]], but the -REM [[!peak]] (period of time where you have the highest likelihood -of getting REM) is from 06:00-09:00, and likelihood for getting -REM is lower the farther away from that time period you get. As a -result, it’s unlikely you’d get REM in all of your naps (if you get -any at all, as many poly sleepers never achieve REM naps).
-Even if you were incredibly -prone to REM naps and you manage to have 20m of REM in each of your -three naps (again, highly unlikely, and that assumes no light sleep -or [[!SWS]] and instantaneous sleep onset), that would account for 60m -out of the average 105m of REM, leaving you with 150m of vitals -remaining to fit into the remaining 144m of your core (still -mathematically [[!impossible]]). - + +

Redirecting to [[!M3impossible]]

diff --git a/snippet/m3impossible.html b/snippet/m3impossible.html new file mode 100644 index 0000000..27e8274 --- /dev/null +++ b/snippet/m3impossible.html @@ -0,0 +1,29 @@ +<
> + +

[[+M3]] and average sleep needs

+ +If you’re an average person, you need between 7-9 hours of [[+monophasic]] +sleep, which contains on average between 90-120 minutes of slow wave +sleep, and 90-120 minutes of [[!REM]]. Together this accounts for an +average of 210m of [[!vital]] sleep (vital meaning necessary), which +is more than the base [[+M3]] [[!core]]’s length. +

+The average person cannot easily reduce their [[!light-sleep]] percentage +below 50-20%, meaning that if you achieve the (highly unlikely) +minimum of 20%, you’d need to fit 210m of [[!vitals]] into the remaining +144m of core sleep, which is obviously not mathematically possible. +

+It is possible you could also get [[!REM]] in your [[!naps]], but the +REM [[!peak]] (period of time where you have the highest likelihood +of getting REM) is from 06:00-09:00, and likelihood for getting +REM is lower the farther away from that time period you get. As a +result, it’s unlikely you’d get REM in all of your naps (if you get +any at all, as many poly sleepers never achieve REM naps).
+Even if you were incredibly +prone to REM naps and you manage to have 20m of REM in each of your +three naps (again, highly unlikely, and that assumes no light sleep +or [[!SWS]] and instantaneous sleep onset), that would account for 60m +out of the average 105m of REM, leaving you with 150m of vitals +remaining to fit into the remaining 144m of your core (still +mathematically [[!impossible]]). + diff --git a/snippet/monocore.html b/snippet/monocore.html index 0014a4e..416fab9 100644 --- a/snippet/monocore.html +++ b/snippet/monocore.html @@ -1,6 +1,6 @@ <

> -

Everyman / Monocore schedules

+

MonoCore / Everyman schedules

These schedules are what Puredoxyk came up with originally as an alternative to [[+Uberman]]. They use the ubersleep formula diff --git a/snippet/nap.html b/snippet/nap.html index 52dc6d0..bf59ec8 100644 --- a/snippet/nap.html +++ b/snippet/nap.html @@ -44,8 +44,8 @@ If you don't have the ability to take 20m naps, two 15m naps could replace one The ubersleep formula, originally described by Puredoxyk in her book "Ubersleep: Nap-Based Sleep Schedules and the Polyphasic Lifestyle", asserts that a nap -can replace an entire sleep cycle of 1.5h. This is what created the [[!Everyman]] -and [[+Uberman]] schedules. +can replace an entire sleep cycle of 1.5h. This is what created the [[!MonoCore]] +(then [[!Everyman]]) and [[+Uberman]] schedules.

In truth, the [[!core]] still has to undergo [[!compression]], as [[!vital]] requirements do not total the 2h that the formula would suggest - diff --git a/snippet/objectives.html b/snippet/objectives.html index 75d40ab..09c9a16 100644 --- a/snippet/objectives.html +++ b/snippet/objectives.html @@ -26,9 +26,9 @@ is random sleep, the ultimate of flexibility, leaving no space for health.

  • For healthy flexibility: Choose something with a 4.5h core at the very - least. Something like [[+E3Ext]] is quite good for flexibility once + least. Something like [[+M3Ext]] is quite good for flexibility once adapted, but [[!consistency]] is key during adaptation still. - [[+BiphasicX]] on the other hand is near-[[!non-reducing]] but flexible + [[+MX]] on the other hand is near-[[!non-reducing]] but flexible from the start!
    • diff --git a/snippet/rsr.html b/snippet/rsr.html index e967215..e4ecd7f 100644 --- a/snippet/rsr.html +++ b/snippet/rsr.html @@ -25,8 +25,8 @@ with RSR: On any schedule with [[!naps]] that has a TST of 6h or higher may leave you constantly tempted to skip the nap, and you might not get any repercussions from it. In some cases, this can even happen for 5-6h schedules like - [[+E3ext]]. If this happens, the schedule is very similar in mechanics to - [[+BiX]], and likely close to [[!non-reducing]] for you. + [[+M3ext]]. If this happens, the schedule is very similar in mechanics to + [[+MX]], and likely close to [[!non-reducing]] for you. @@ -38,7 +38,7 @@ cases, even double-shortened [[+Mono]] at 4h30 TST has been possible, whereas any such [[+Mono-Short]] schedule is usually completely unadvisable.

      -
    • You can probably attempt schedules with a TST of 4h, like [[+E3]].
      • +
    • You can probably attempt schedules with a TST of 4h, like [[+M3]].
    • You can probably be significantly more flexible on schedules above 5h of TST.
    • You can probably flex before [[!adaptation]] on schedules above 6h of TST (as opposed to 7).
    • You can maybe even do [[!NapOnly]]. But this is rare nonetheless.
      • diff --git a/snippet/sleep-requirement.html b/snippet/sleep-requirement.html index 629c266..11994fd 100644 --- a/snippet/sleep-requirement.html +++ b/snippet/sleep-requirement.html @@ -25,6 +25,6 @@ consistent mono at all (common with RSR). If you suspect that this is happening, especially if you feel like you're oversleeping the whole time, there's only really one method left:

      -This other method is: Try it and see. If you can adapt to [[+E3]] +This other method is: Try it and see. If you can adapt to [[+M3]] for example, you almost certainly have [[!RSR]]. If you can adapt -to [[+E2]], you probably don't have ISR, etc. +to [[+M2]], you probably don't have ISR, etc.