Posted by & filed under News.

Thought I would put out there, Conlangery episode #64 will probably publish later than usual.  In my haste to move I apparently had not synced my computer to my backup service before moving.  Hence, after several days of syncing my laptop up to said service, I discovered that Conlangery64_rough.aup was no where to be found.  My hope is that it is, in fact, saved on my desktop computer, which will be sent to me via UPS in a few days, and I don’t end up with a “lost episode” — just a late one.

10 Responses to “Episode 64 is likely to be late”

  1. Anthony Docimo

    Take as much time as you need. Listening to Conlangery is a privledge, not a right.

    Just pay no heed to we poor rain-soaked fans sitting next to our emailboxes. We’re patient.

    seriously, do what need be done, and take as much time as it takes.

    Reply
    • admin

      Honestly, it’s not about not having time. It’s about not having the damn files. Once I get those files, I will publish the episode.

      Reply
      • Anthony Docimo

        however long it takes to get the files. just don’t rush in recovering them. (i speak from experience on that score)

        Reply
  2. smrk

    Good luck with moving and getting settled at school, George! Take as long as you need.

    Reply
  3. MBR

    I’m eagerly awaiting #64, but in the meantime I’m listening more intently to back issues, pondering the topics for my conlangs. Well, except for anaphora and co-reference, which scare me.

    Reply
  4. Mathew Park

    This isnt a oress to get it up or anything,its just something that I thought of today, since its getting close to the weekend, which means monday is right around the corner, Since I know you tape out 3? episodes in advance, if monday comes around before 64 is up, will you post 64 and 65, or will you just post 64 and have episodes 4 weeks in advanced?

    Reply
    • admin

      Actually, due to recent events we have burned away essentially the entire buffer, so I’m thinking I may actually put 64 up Monday, then try to rebuild the buffer as quickly as I can.

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *