woke up kind of wanting to "map out" our shared headspace a bit more, or at least list the common elements when we're not just talking in The Void
maybe later
plan for today
- this
- take dog for a walk round the lake and see how flooded it is with the storm
- make a 30GB git repo into a series of not-30GB repos while trying to preserve commit history, because for some reason the cursed combination of git and onedrive for mac do not particularly like trying to work with a 30GB repo
- write out the text for at least one more christmas card, we do not want to be scrambling trying to do that last minute 1
- process and post today's VRChat photos
- maybe rename bones in blender and try setting up the yinglet in resonite again.
- BONUS: π has a comm request to submit after getting jealous of how much biting i got to do yesterday
-
we're also still open to friends adding to our workload here, preferably before we get the card order locked in
- write thing on headspaces
- take dog round lake
- surprisingly not as flooded as we thought
- [?] git repos are in progress, but we've got a process for them. it does feel like they're a lot smaller than they should be, but the process we've had to use is clearing out Unity's cache files due to them being in the
.gitignore, which I guess were taking a lot of space? still taking (another) backup of the original repo; at least it'll be easier to pull off the NAS like that than trying to coax OneDrive that we're definitely sure we'd like all the thousands of individual files. - no christmas cards tonight, too tired to write heartfelt messages. but hey, one dropped isn't bad
- processed the vrc photos, glad for vrclens allowing lots of aerial photos of cuddle piles
- imported the yinglet into resonite. beyond the bone name issue, what also helped here was plugging bad gaming laptop into work laptop dock, meaning that i could use my trackball rather than the touchpad for setting things up. actually exploring more of resonite isn't happening tonight, but i'll feel better world hopping on deck now
- got π's comm request sent off after fighting with our email 1
-
remembering now why my email is set up as a distribution list, we have one mailbox (
<legal entity>@<domain1>), with a bunch of aliases (dex@<domain2>,<π>@<domain2>) - but office 365 doesn't seem to like you sending as the aliases (possibly because we only toggled the option to do so on earlier). though it will let you send as a distribution list. in this case even though we tried to send it as<π>@<domain2>we're pretty sure it's ended up as just the mailbox address.
