Yes, that would be the safest path. While also focusing on taking care of yourself in other ways. Sounds like you’re already doing great in that area, with not drinking or smoking.

Important factors that come to mind:

1) Purity - Is it tested to be verifiably free of contaminants?

2) Dose - What is the CBD/THC ratio? (I.e. 10:1, 1:1, 1:10)

Higher CBD content with lower THC levels tends to be more effective as sleep aid. While some find that balanced or higher THC ratios are more effective for pain relief.

Although THC is often associated with pain relief, it is through a different mechanism (mood and psychological) than painkillers which block pain receptors in brain.

3) Consumption practice - How often is it consumed? Is it being mixed with consumption of other substances? Alcohol consumption should generally be avoided for optimal health, but particularly when CBD or THC are present in the bloodstream, as liver and kidney toxicity will be amplified.

Appreciate your response and explanation regarding the reason for that restriction. Seems as though my understanding regarding the root cause of it was lacking. Also good to know about the android client, I will be verifying that functionality.

Hmm Amethyst, interesting as I recall having a similar issue when testing it a while back. Wish I could help, but it’s not my daily driver.

Not sure, if you changed/removed relay(s) recently try changing/adding them back. May also resolve itself over time.

Yeah it was unfortunately. Can confirm from experience. Nothing personal, just every time I see @current mentioned, have to call it out. Effectively KYCing you through in app subscription to use essential features other clients don’t put behind paywalls. No bueno.

As far as I know, could be a caching issue with the client, or a result of relay connection changes.

Even if that mainstream nostr cleint requires a name, email address, and country of residence to enable? Regardless of whether you can just spoof it, still not ideal.

Not if it’s an integrated wallet that defaults to a client created Lightning Address that’s locked behind a Premium subscription paywall.

Perhaps..

Both can co-exist in harmony ;)