I gave up and got Instagram.

For instance 叱 and 明 both seem to fail in the same way: U+1F996 T-REX in the upper left corner and the URL fragment fails to update.

wat

It seems pretty clear that the "why" is "because it's there"

> they only support a tiny subset of the format

I think Orgro's parser[0] is pretty complete at this point. If you can find an Org syntax that Orgro doesn't support, please let me know.

However I should be very clear here:

> they can't support any of the features that require the rest of emacs to be present which is a lot of of the value

This is absolutely true and unlikely to change anytime soon. As I'm sure you know, parsing the syntax correctly is not at all the same as supporting all of the features built on top of the AST.

[0]: https://github.com/amake/org_parser

The smart thing to do is realize you don't know what you're doing, and don't rely on the genie at all. Or hire someone who knows how to tame the genie. Or whatever; someone else put it better: you fucked around and you found out. lol

People used to criticize the walled gardens for having capricious reviewers and slow review times, but I found F-Droid much more frustrating to get approval from and much slower to get a release out.

So this development is much appreciated. In fact I had an inkling that build times had improved recently when an update made it out to F-Droid in only a day or two.

Where is this happening?

So in other words the strategy in the docs doesn't actually address the issue

Yes there is: https://fonts.google.com/noto/specimen/Noto+Serif+JP

> blowing it up out of proportion is just as toxic

Making a false equivalency of the supposed toxicity of the commenter's post and the toxicity displayed in the article.

You can just take the L; you don't have to be performatively obtuse about it.

And yet the context is extremely important.

> I didn't factor this in

That's how you get to false equivalencies.