Lately, after I reply to a post in a conversation view, all of the scroll events go to the timeline behind the conversation view, so that I cannot scroll to the X and close the conversation view. This is on iOS.

I treat Basecamp as a repository of project history: discussions, decisions, and documents. When it comes to picking what to work on next, though, that is all Pivotal Tracker.

AutoHotkey?

I am halfway expecting to have them enter clientGUID as well for now. Not sure if I might open source this, so I want to avoid having secrets committed into the repo. And having an app on the user's own machine try to keep a secret from the user has always been a fraught endeavor.
//

There's always the old BASIC approach of leaving a gap of 10 between each to allow slotting in new ones later. But a table of contents is definitely a lot more flexible and explicit.

That sed script is going to require me to puzzle over some of the weirder operators. I do wonder if you couldn't just use tr to rewrite newline to space instead.

If you adjust the file naming to sort naturally in the correct order, you should be able to just use a glob in your shell to name the args. I bet Pandoc doesn't worry overly much about it as it's expected you'll rig up a Makefile or similar automation like reflex or fswatch.

@skematica Keyboard only affects input method. You'll have to change the system language preference to prefer a different English to US for it to default to that for spellchecking, though in some apps, you can change the language in force for just a document.

Now it is one more thing. ;)

OK, I give up trying to get a second level of bullets to appear.

Today in Macchiato:

  • Encountered rate limiting
  • Baked in basic streams
  • Made posts show relative timestamps
  • Added support for showing supplemental post info
  • Started working on auth - the UI is there
  • Added in a larval "toast" system

Next:

  • Finish auth:

  • configure SettingsVC with Authenticator

  • save auth info to keychain and restore it
  • save last-account info in defaults
  • add client GUID field to login form
  • prefill if they've logged in already once

  • Feed auth into our post repo

  • Then we can finally access logged-in–only streams

  • Allow to write a new post

  • Swipe on post to jump to thread
  • Pop up action sheet on long-pressing a post to support star/repost/etc