• brsrklf@jlai.lu
    link
    fedilink
    arrow-up
    19
    arrow-down
    1
    ·
    10 hours ago

    It’d still be a mess anyway. How do you subdivide your two year halves? What do your months look like? If they still exist.

    Assuming you use equinoxes too, you can split your year in 4… Except since you’ve got 365 days to split, it will never be a perfect split.

    And turns out the Earth doesn’t care about synchronizing rotation and revolution and the year is actually about 365.24 days. so you still have freaking leap days every four years, except not every hundred year, except yes please every 400. Or whatever rule you make to fix the inevitable deviation.

    • Val@anarchist.nexus
      link
      fedilink
      English
      arrow-up
      13
      arrow-down
      1
      ·
      9 hours ago

      I mean we define year as being from one spring equinox¹ to the next, no matter if it’s 365 or 366 days. So if we made next year 1 it would be from 20th of March 2026 14:46 UTC to the next 20th of march 2027 20:25 UTC (The first day of the year could be day 0, the last of the old year but still also in new year, to account for the fact that it’s not midnight.). The months would be replaced with quarters(seasons), ending on: June 21, September 23, December 21. Every year the dates would slightly shift because of the way orbits work, but there is no leap year math.

      The first quarter, spring, has 93 days, the second, summer, 94 and so on. These will probably be subdivided a multitude of ways. Quickly sketching I found 6 * 4 * 4 - (3 or 4) which seems to work, though I’m naturally draw to base6 due to it being highly composite. This makes 24 days in a quarter-season. A nice analogue to the hours.

      A sketch of a calendar. Spring 01 is written on the top. The days are marked by white squares. The days are split into four sections. There are "S1", "S2", "S3" and "S4" written next to the sections. An arrow points to the first day with the text "This would be March 21". There is another arrow with the text "This would be June 21" pointing to the last day.

      I think this calendar works better because it doesn’t attempt to add any human control over a completely chaotic system: Earths orbit speed and rotational period. The underlying principle is chaotic and humans should build systems that are build on top of this natural disorder. By attempting to define and control disorder you must create so many convoluted rules (Like the leap day rule). Our calendar is an example of the human desire to “fix” nature to our own way of life instead of leaning to coexist with the natural disorderly processes that govern our lives. It’s the same mindset that gives us the blatant disregard for the natural resources or climate.

      This is a rather anarchic position but that’s because I cannot help but inject anarchic rhetoric into my thought process due to so much of the way we live has been in blatantly build using archic concepts, even the calendar is dripping with it.

      ¹: Accidentally called it solstice sense I forgot there’s a different word.

      • Val@anarchist.nexus
        link
        fedilink
        English
        arrow-up
        5
        ·
        5 hours ago

        Because I don’t really have anything better to do today I made a JS generator for this calendar: https://codeberg.org/anaVal/misc/src/branch/main/cal.

        Here is the full year 1 I generated using it: A calendar on a black background. On the top is the header Year 1. There are four columns titled "Season of Green", "Season Of Warm", "Season of Color", "Season of Light". Each column has four groups of numbers. The groups have 4 lines of 6 numbers counting up. The last group of every column is cut short. Each column has 88 to 94 numbers.

        Interestingly the 1st days of the 4th quarters are quite close to the starts of Gregorian months (June 1st, September 2nd, Dec 5th, March 4th).

        • Val@anarchist.nexus
          link
          fedilink
          English
          arrow-up
          1
          ·
          23 minutes ago

          And because I really can’t help myself here is a static file version of the same calendar: https://files.catbox.moe/idfrdf.html. Running this is as easy as downloading the file and dragging it into your browser. Thanks to being able to quickly move between the years you can really see how little actually changes between them. I think this could actually be a viable calendar.

      • Clent@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        3
        ·
        4 hours ago

        The 365.2422 days per celestial year is a math error we can fix.

        We need to adjust the length of days and seconds but we can get rid of it completely if we wanted to.

        It’s not like noon means the maximum of the suns arc or sunset and sunrise don’t already shift throughout the year.

        The only thing that stops it is the momentum of a human measurement error.

        If we use 366 we just get slightly shorter days by about 3 minutes. All of these time measurements are more arbitrary than feet and inches. Science back filled the bullshit with physical constants and there is no reason we cannot tie a proper system into alternative physics constants.

        • Val@anarchist.nexus
          link
          fedilink
          English
          arrow-up
          1
          ·
          4 hours ago

          A year is a rotation of seasons. It has nothing to do with the day-night cycle. That should absolutely be separate.

          And the 365.2422 isn’t a math error. It’s a mathematic ratio, rotation around the sun / rotation around itself. and it should absolutely be upheld.

          • Clent@lemmy.dbzer0.com
            link
            fedilink
            English
            arrow-up
            1
            ·
            4 hours ago

            The mathematical error os not basing our time counting on that ratio. The number is only 365.2422 because our second, hours, days are too long/short.

            We can just decide we want one rotation to be exactly 366 units and then work backwards from there to determine new units.

            • brsrklf@jlai.lu
              link
              fedilink
              arrow-up
              2
              ·
              3 hours ago

              So you’d support a “day” unit of time that has no relation with the times the sun is rising and setting?

              if your “day” is exactly a 365th or 366th of a year, you’ll have to work with with the fact a specific hour like 12PM would gradually deviate to be any time from sun’s zenith to the middle of the night.

            • moonshadow@slrpnk.net
              link
              fedilink
              arrow-up
              3
              ·
              3 hours ago

              Days are defined by a different natural cycle, that of the earth’s rotation around its axis. That happens 365.2422 times every time we go around the sun. You can’t just assign the length of a day to something more convenient

            • Val@anarchist.nexus
              link
              fedilink
              English
              arrow-up
              3
              ·
              3 hours ago

              A day is defined as a single rotation around earths axis. A year is a single rotation around the sun. The 356.2422 is the result of those two definitions. Earth takes 356.2422 rotations around its axis to rotate around the sun. That is a fact. You could define a unit to be 366th of a rotation around the sun, you could even call it a day, but as a result you lose the reason a day is a useful unit: It’s the time it takes for earth to spin around its axis, a far more useful definition than 366th of a year.

              • erusuoyera@sh.itjust.works
                link
                fedilink
                arrow-up
                1
                ·
                37 minutes ago

                I propose we make the calender a nice round 360 days, then have a roughly 5-6 day holiday for new New year around the spring equinox.

      • moonshadow@slrpnk.net
        link
        fedilink
        arrow-up
        2
        ·
        5 hours ago

        Excellent calendar idea, excellent post. What do you think about using solar noon instead of time zones?

        • Val@anarchist.nexus
          link
          fedilink
          English
          arrow-up
          2
          ·
          4 hours ago

          If you like the idea you’ll probably appreciate the comment I just left were I made a program to generate it.

          Time zones are complicated. One one side I like them because 12 is always noon which means you can get used to the sunset times. On the other hand I think the time shouldn’t be related to sunrise at all and everyone should use UTC (or equivalent). Let sunrise and sunset be their own thing. Again let’s not try and contain nature but instead define a simple method and just use that. Let the natural world tick according to it’s own clock. We have our own atomic ones.

          This also brings me to the idea that we should just use a single clock. Take an atomic clock, make it start counting and build all timekeeping around it. Basically the same thing computers are doing but for everyone. Let Sunrise, Noon, Year all be it’s own thing and have a single timestamp for most timekeeping. Due to liking base6 I’d advocate for this timestamp to be in base6 instead of base10. By using it we are going to get an intuition of how much some length of time is that is separate from days.

          • moonshadow@slrpnk.net
            link
            fedilink
            arrow-up
            3
            ·
            4 hours ago

            Thanks, I’ll check that out. A big part of what I liked about your calendar is the direct correlation to a natural cycle though, and I like the idea of solar noon for the same reasons. The idea isn’t to constrain nature but acknowledge it and adapt ourselves, centering days on the sun’s zenith at ones location just makes intuitive sense to me and lines up with my own perception of time when disconnected from infrastructure. Completely useless and impractical computationally, but very well aligned with a human sense of place in both time and space