Move the location of where the status message edit text has the initial debug value set

Move the location of where the status message edit text has the initial debug value set so that the text watcher event listeners are triggered right at the very start of the app
Obtain a reference to the post status button on the main activity
Change the reference to the post status button to a field variable
Initially disable the post status button on the main activity
Disable the post status button if the status message is too long
Enable the post status button if the length is acceptable
Create a function stub to test whether the status message is valid

All this boolean logic to determine if the status message is a valid length is getting complex, let's do a little refactoring
Indicate that all status messages are valid as initial condition
Test for a status message that is too long
Test for an empty status message
Flip the order of boolean tests just in case the status message is null
Fix a silly null pointer logic bug I introduced

I obtain a reference to  the post status message button after I attempt to make use of that reference in the on text changed handler of the status message edit text.
Temporarily permit network communications on main thread

The Android OS does not permit an app to perform long running operations on the main thread such as file access or accessing the network. Apply a temporary fix that will permit us to do this before we show the proper solution later on.
Enable internet permissions

Android manifest prevent access to the internet by default unless granted permission in the manifest
Log any exception when posting to the yamba service
Extract the code that interacts with the yamba service to its own function
Enable or disable post status button depending on whether we have a valid status message to post
Test for network connectivity before we post the status message
Add permission to test network connectivity to manifest
Add a log message about lack of network connectivity