Andrew Raffensperger

Found this thread via search. I have a BN-Link Smart Plug w/ Energy Monitoring and I have the same problem: my DPS values appear almost static. My query messages look...

adding myself to this thread

[@adraffy/ens-normalize.js](https://github.com/adraffy/ens-normalize.js) has been pretty stable. This repo now contains the minimal data necessary for operation and validation conformance. It is a direct replacement for the prior library except it is...

Updated to match [@adraffy/ens-normalize.js](https://github.com/adraffy/ens-normalize.js) 1.9.0

https://discuss.ens.domains/t/draft-approval-of-ens-name-normalization-standard/16957/7 This should now be a zero-change drop-in replacement for the old library.

There are some thoughts here: https://github.com/adraffy/ens-normalize.js/issues/21#issuecomment-1589986960 With browser detection, it would be possible to use features (like Unicode regex patterns.) I'll update this when I get some time.

Possible ideas: 1. Compress [spec.json](https://github.com/adraffy/ens-normalize.js/blob/main/derive/output/spec.json) using ANY technique * My current implementation takes this from `2.99 MB` → `14673 bytes` for ENS data and `5588 bytes` for Unicode NF data....

I greatly appreciate this PR but this would be a breaking change. I will consider this for a future update.

Probably related: `drawImage()` is leaking in 0.1.52 with `globalCompositeOperation = copy`

The extra data is so `is_combining_mark()` can be correct independent of ENSIP-15. For example, it useful to know if a character is a CM inside of an error message for...