adamwulf

Hi! I'm the Adam that's continuing Muse after this transition. It's definitely not too late for Muse - the sustainable business in that context is the full team of 7. Scaled down, I fully expect to support and grow Muse for years to come.

Swift's `NotificationCenter` leaves the possibility for code-errors with mistyped `userInfo` keys or observer method types. PonyExpress enforces observer method and notification types at compile time.

The sync server itself also acts as an online backup too - if you lose all of your devices you can login with the same account and re-download.

not yet - but this is very high on our priority list! If we had built in encryption in this first step, then it wouldn't extended development time by many months. Instead, we chose to release sync first, prove the core local-first technology works and is scalable, and add in encryption in phase 2. The basic protocols and data structures are designed with encryption in mind, so we're excited to start work on that very soon.

Muse team member here :) Existing accounts are still 100% supported for both customers and free accounts, including our sync service. This only affects new downloads.

I've actually been wondering the same thing. I've found SyncSpace and TalkBoard on iOS. On the pricier end, ConceptBoard is web-based option.

A good friend of mine has been using TalkBoard and hates it, we might try SyncSpace soon instead.

We're using this to sync up a remote team of developers during morning standup. What's your use for remote whiteboard? have you found anything either?

How do we report spam users?

jackson_1 seems to be both "final year of studying computer science" and "So I'm a 3rd year electrical engineering student" (https://news.ycombinator.com/item?id=11825550)

the text from both of those questions mentions reddit, and can be googled and traced to ~2010...

I've been blocking 3rd party cookies for over a year and haven't noticed any downsides or broken websites.

First year CS can be boring, the more interesting classes come later. I highly recommend sticking with it, I was in a similar place freshman year and really enjoyed the later years of the degrees.

I also recommend talking to the TA's and professors to see if you can get involved in any of their research or projects. That's something I was able to do junior year, and if I'd known about it I probably could've gotten involved much sooner.

When I lived in Portland OR, an org called Free Geek let volunteers rebuild computers for folks who couldn't afford them. Even if you're not near them, maybe they can point you somewhere similar in your area

http://www.freegeek.org/#volunteer

awesome - looking forward to your dev guide too! for in-app purchase, i don't have any in the app yet, but will soon. that's how i'll monetize going forward. the last + next updates are geared towards fixing some on-boarding issues, my tutorials were too vague. another good reason to get real user testing asap :)

Good question, that might be a good thing to add into the guide too. Here's a short take: From a tax perspective, they're the exact same. There won't be any difference in your tax rate at all between the two. So unless you need the added liability protection b/c you're working on something like a healthcare related app, then going w/ just your own name should be fine.

yep, conversion to ratings has been super low. I don't ask for that very well at all inside of the app. A good % of downloads were bulk education downloads as well, which don't convert. If I'd done better at asking for reviews inside the app, I think that number would be much higher.

sort like the normal 80/20 rule - i'm mainly pointing out that the estimate for that last 20% is nearly always way under estimated :)

awesome, glad you like it!