Bruno Škvorc

Yes, the idea is to feature freeze the remark implementation and upgrade only EVM and pallets going forward. I have already added this as a requirement to both.

I suggested upgrading RESADD with an optional ID target to overwrite an existing resource

> name: According to standard this should match [A-Za-z0-9_] (\w in JS) however, 99% of users want also space. Agreed, this is a bit of a bother for me too....

Bot is in, but it fails on forks. The secrets need to be passed in as ENV or inputs, otherwise forks cannot read them.

from 3.4.1: https://github.com/polkadot-js/api/releases/tag/v3.4.1 (breaking change it seems)

This will actually become unnecessary soon: https://github.com/paritytech/substrate/pull/8120

Needs a spec change, and a whitelist for callback ops to LIST, SEND, RESADD. Otherwise fine, but needs to be aware of possible double curlies in the resource fields, if...

Can you give some examples of such behavior?

What does it mean to "mis-gender someone", this sounds too vague to me? Perhaps a specific example of an exchange would be helpful.

It does, thank you. So, does constantly having to think about removing gender non-neutral pronouns from every uttered sentence not equate to walking on eggshells? To me, that's just too...