Is there an emoji[^1] that is recognised to mean any genitalia, sexual organ, erogenous zone or the like in a wildcard or reader's-choice kind of way?
[^1]: It doesn't necessarily have to be a fruit or a vegetable or flower or anything particular. The question can be interpreted more generally.
We all know about brinjals, peaches and certain blossom emoji but I'm looking for a single emoji, likely a little suggestive, that people in the LGBTQ+, non-binary, sexually freed and queer community interpret as meaning their parts – whatever those happen to be, whether expressed or observed at birth or chosen, freely, in life – and welcomes their own free will to choose what that means, for them.
Although I have recently chosen new levels of acceptance of the ways in which I deviate from the "traditional"[^trad] gender binary I remain, alas, uneducated in how others talk and communicate about their sexuality and so I find myself scared to express my own sexuality for fear of perpetuating the very indoctrination from which I feel I escape, unwillingly and likely unconsciously. Yet I have Thoughts to share and so I seek, now, to learn how to communicate sympathetically – symbiotically – on these topics.
Help me.
[^trad]: Even here, I know that "traditional" is actually only a descriptor for very recent human history. I actually don't know if it is right to use this descriptor and I wonder. Are there better terms for 20th century cis-het. binary strictures, sexual suppression, prudishness and culture-wars?
Zed is very interesting. I know it.
Very recently, I found a fork of Zed that gutted the AI Assistant integration and Telemetry. I forked that, myself, and took it further: gutting automatic updates, paid feature-gating, downloading of executable binaries and runtimes like Node.js (for extensions that don't compile to WASI), integration with their online services, voice-calling, screen sharing, etc.
My branch ended up down 140 000 lines[^1] of code and up less than 300! It was educational and the outcome was absolutely brilliant, to be fair. In all honesty, forking it and engaging in this experiment took less than 24 hours even though I restarted three times, with different levels of "stringency" in my quest.
[^1]: No word of a lie! The upstream repo is well over 20k commits and over 100 MB in volume. Zed is not a nice, small, simple code-base: it is VAST and a huge percentage of that is simply uninteresting to me.
This experiment was very realisable. Forking Zed and hacking on it was quite possible – the same cannot be said for just "forking Electron" or "forking VS Code" or even getting up to speed on those projects to the point of being able to fix the underlying issues (like this OP) and submit merge-requests to those projects. They have a degree of inscrutability that I absolutely could overcome but would not, unless I was paid to at my usual rates. (I have two decades of professional development experience.)
I shelved the effort – for the time being – for a few reasons I don't particularly want to extenuate, today, but I shall continue to follow Zed very closely and I truly, deeply hope that there is a future in which I see hope (and, thus, motivation) in maintaining a ready-to-go, batteries-included, AI-free, telemetry-free, cloud-free fork.
Part of maintaining a fork would include sending merge-requests upstream even though I should hardly expect that my fork would be viewed favourably by the Zed business. But, from what I can tell, Zed seem to act true to the open-source principles – unlike many other corporate owners of open-source projects – and I see no reason (yet) to believe they would play unfairly.