Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the amp domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home2/sisikunm/public_html/wp-includes/functions.php on line 6131

Notice: Function amp_has_paired_endpoint was called incorrectly. Function cannot be called before services are registered. The service ID "paired_routing" is not recognized and cannot be retrieved. Please see Debugging in WordPress for more information. (This message was added in version 2.1.1.) in /home2/sisikunm/public_html/wp-includes/functions.php on line 6131

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home2/sisikunm/public_html/wp-includes/functions.php on line 6131

Notice: Function amp_has_paired_endpoint was called incorrectly. Function cannot be called before services are registered. The service ID "paired_routing" is not recognized and cannot be retrieved. Please see Debugging in WordPress for more information. (This message was added in version 2.1.1.) in /home2/sisikunm/public_html/wp-includes/functions.php on line 6131

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home2/sisikunm/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the worth-the-read domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home2/sisikunm/public_html/wp-includes/functions.php on line 6131

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home2/sisikunm/public_html/wp-includes/functions.php on line 6131

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home2/sisikunm/public_html/wp-includes/functions.php on line 6131

Warning: Cannot modify header information - headers already sent by (output started at /home2/sisikunm/public_html/wp-includes/functions.php:6131) in /home2/sisikunm/public_html/wp-includes/feed-rss2.php on line 8
Living free Archives - SISIKUNMI https://www.sisikunmi.com/tag/living-free/ Live. Learn. Inspire Sun, 14 Jul 2019 12:41:09 +0000 en-US hourly 1 https://wordpress.org/?v=6.9.4 https://www.sisikunmi.com/wp-content/uploads/2020/10/cropped-cropped-cropped-wp-1604087001228-1-32x32.png Living free Archives - SISIKUNMI https://www.sisikunmi.com/tag/living-free/ 32 32 Living free! https://www.sisikunmi.com/musings/living-free/?utm_source=rss&utm_medium=rss&utm_campaign=living-free https://www.sisikunmi.com/musings/living-free/#respond Sun, 14 Jul 2019 12:41:09 +0000 https://sisikunmi.wordpress.com/?p=411 As much as I detest WhatsApp statuses, I’ve actually learnt quite a lot from reading people’s thoughts on there. It makes for a simple medium to share thoughts without much of a hassle. I selectively view statuses and I’m almost always happy with those I choose. Today’s post was inspired by the status updates of two people on my contact list. Both of them are complete strangers to each other having just me as their mutual contact, but they managed to post something similar on their statuses within hours of each other. I decided to share some of my reflections based on their posts. The main point of both posts is avoiding ‘riding on the praises of people.’ The posts caught my attention because I realized that I sometimes did just that, ride on the praises of people, even when I know deep down that some are not as true as stated. As one of the posters said, sometimes, it’s people’s belief in us (through their comments about who they think you are) that give us that extra push to be more. Still, it is imperative that we recognize who we really are and dissociate it from who people think we are so that we can get from we are now to where we hope to be. One example of living for people’s praises is evident on social media platforms these days, where a lot of us post things on social media and get engagements (likes/retweets/comments; it’s so easy to lose yourself in this and begin to do things solely for the approval of others. I am relatively active on twitter and this is a trend I see almost every time I log into my account. The thing about doing things for the approval of others is that, you basically imprison yourself and are no longer free to be truly you based on the fear of losing your following. Also, humans can be fickle, the same people who rooted for you and made you do certain things are the ones that can turn on you and begin to criticize you when things don’t go well. Sometimes, it can be hard to look deeply and assess yourself, devoid of people’s praises but that is something we should do more regularly, in other to truly truly be our best selves. I’m learning to do what I stated above and I hope you will too. xOxO, Sisikunmi

The post Living free! appeared first on SISIKUNMI.

]]> https://www.sisikunmi.com/musings/living-free/feed/ 0