me, thinking to myself about #ProjectMonday while working:

Having both of those booleans determining the state of registration on an instance isn't really great to work with… Also, you have this weird state where registrations could require approval, but not even be open, so it wouldn't matter!

What if we just modeled it as a custom type, did away with that one bad state, and then we collapsed two boolean fields down into one custom type field? A slightly more involved decoder, but way nicer!

Showing off some base work for my #MastoClient, which is being called #ProjectMonday, after #MastoMonday.

https://68kheart.com/app/monday

Spoiler: it's not terribly exciting yet! I've been trying to get down a solid flow for OAuth and cache management via LocalStorage before moving forward. Both are new to me! Also not been feeling too hot lately, but slowly chugging along with this.

I also included the #Elm time-traveling debugger so people could poke at it and see how the program changes over time.