raffy

Slack doesn't even have a functional input field.

why are we debating ai slop from a [dude](https://www.coindesk.com/author/omkar-godbole) who wrote about XRP in the last 2 of 4 articles?

I created a bunch of Unicode tools during development of ENSIP-15 for ENS (Ethereum Name Service)

ENSIP-15 Specification: https://docs.ens.domains/ensip/15

ENS Normalization Tool: https://adraffy.github.io/ens-normalize.js/test/resolver.htm...

Browser Tests: https://adraffy.github.io/ens-normalize.js/test/report-nf.ht...

0-dependancy JS Unicode 15.1 NFC/NFD Implementation [10KB] https://github.com/adraffy/ens-normalize.js/blob/main/dist/n...

Unicode Character Browser: https://adraffy.github.io/ens-normalize.js/test/chars.html

Unicode Emoji Browser: https://adraffy.github.io/ens-normalize.js/test/emoji.html

Unicode Confusables: https://adraffy.github.io/ens-normalize.js/test/confused.htm...

oh look, another highly-compressible, hn circle jerk about the "crypto" boogeyman

tbh, i'm always impressed by no-coiner and armchair bitcoiner comments -- it's like listening to a straight-edge discuss psychedelics -- how can you comment on a space you *clearly* don't understand?

>SEC has already provided clarity on crypto

oof, so...is Ether a security?

Is this tweet an exchange? https://twitter.com/hoffmang/status/1515797969802436608

ENS has DNS import via TXT Record verification proof, so the entire DNS tree can coexist in ENS trustlessly as long as future ENS-only TLDs are chosen wisely (seems simple: just use 0x80+ Unicode.) For example, try resolving my domain, "raffy.antistupid.com" in ENS.

I believe, the ENS registry only contains "eth" as an rogue node (also "[0-9a-f]{40}.addr.reverse" is used for wallet names). Recently, ".art" started offering tokenized names, where you get both DNS and ENS.

> I hope this idea catches on

This already exists with Ethereum Name Service (ENS) https://ens.domains and Sign-in With Ethereum.

I have tool which lets you scroll through all characters in a large document. It also shows names, scripts, and IDNA-like status.

https://adraffy.github.io/ens-normalize.js/test/chars.html

I've created a bunch of Unicode tools for Ethereum Name Service (ENS).

https://adraffy.github.io/ens-normalize.js/test/resolver.htm...

Also:

https://adraffy.github.io/ens-normalize.js/test/emoji.html

https://adraffy.github.io/ens-normalize.js/test/chars.html

https://adraffy.github.io/ens-normalize.js/test/confused.htm...

https://adraffy.github.io/punycode.js/test/demo.html

Here is a video of another failure case:

https://twitter.com/adraffy/status/1629262969581473792

FYI, there is a new ENS normalization spec on the horizon: https://github.com/adraffy/ens-normalize.js

https://adraffy.github.io/ens-normalize.js/test/resolver.htm...

>and also a reasonably good explanation of why, at least in my opinion, crypto is still completely non-viable as a real medium of exchange

I understand HN is a shit-on-crypto echo chamber but it's naive to think crypto is just settlement.

Settlement is simply a low-level primitive. With smart contracts, you can build whatever mechanism you want before making something final. Multisig, clawbacks, timed-delays, time-locks, escrow, recovery wallets, etc.

For a .eth name, this is trivial: provide operator approval to N-additional wallets

Unfortunately, this is only single-character confusables. There are an enormous number of permutations missing (ѐ [450] vs è [E8]). The confusable matching isn't even reflexive (A confuse B, but B doesn't confuse A).

I've been developing a normalization library for Ethereum Name Service: https://adraffy.github.io/ens-normalize.js/test/resolver.htm...

Kinda related: I am developing a library for ENS (Ethereum Name Service) name normalization: https://github.com/adraffy/ens-normalize.js

I'm trying to find the best combination of UTS-46, UTS-51, UTS-39, and prior work on IDN resolution w/r/t confusables: https://adraffy.github.io/ens-normalize.js/test/report-confu...

Personally, I found the Unicode spec very messy. Critical information is all over the place. You can see the direct effect of this when you compare various packages across different languages and discover that every library disagrees in multiple places. Even JS String.normalize() isn't consistent in the latest version of most browsers: https://adraffy.github.io/ens-normalize.js/test/report-nf.ht... (fails in Chrome, Safari)

The major difference between ENS and DNS is emoji are front and center. ENS resolves by computing a hash of a name in a canonicalized form. Since resolution must happen decentralized, simply punting to punycode and relying custom logic for Unicode-handling isn't possible. On-chain records are 1:1, so there's no fuzzy matching either. Additionally, ENS is actively registering names, so any improvement to the system must preserve as many names as possible.

At the moment, I'm attempting to improve upon the confusables in the Common/Greek/Latin/Cyrillic scripts, and will combine these new grouping with the mixed-script limitations similar to IDN handling in Chromium.

Interactive Demo: https://adraffy.github.io/ens-normalize.js/test/resolver.htm...

Also this emoji report is pretty cool: https://adraffy.github.io/ens-normalize.js/test/report-emoji...

> But this is actually good, nuanced stuff.

What's good about it? Half the post is about Bitcoin. A large chunk is about the ENS token distribution.

There's no link to any of the contracts or code. There's no comparison with existing providers and the trade-offs. There's no discussion on how DAOs are still very immature and evolving. There's no acknowledgement of how ENS has behaved since inception.

Flash loan voting? Clueless.

> This is 100% correct.

I think you forgot to divide by s.

It's cheaper to pay for 2 years in 1 tx, than 1 year twice in 2x, because that's 2 vs 1 modifications to global state.

The price of gas is not constant. Wait for lower demand.

I get frequent migraines and they almost always correspond to physical transitions: hot-cold temperature changes or bright-dark.

I can reliably induce a migraine by looking at alternating black-and-white lines. I have never experienced more than one migraine in a 24-hr period.

For treatment, I've always used a combination of early identification (sudden awareness of own body temperature gradients) plus quick caffeine and marijuana supplementation.

When I was younger, the aura was short and the primary issue was the debilitating, long-lasting headache.

For the last 5 years or so, I only get the headache-part maybe 25% of time. In exchange, the auras have become instantly debilitating, nauseating, and almost incapacitating. My vision goes from normal, to mangled, to "I can see-but-not-comprehend" what I'm looking at. After some time, the aura lightshow slowly moves offscreen and then I feel fine again.

Initial pick: 1/3 chance of winner

Question: did you pick the correct door?

  - If correct, both remaining doors are losers, eg. {loser, loser}.   
  - Otherwise, the remaining doors are {loser, winner}.
    And the loser must be revealed according to the game rules.

If you don't change your answer, you're stuck with the initial chance: 1/3

If you change your answer: (1/3) * 0 + (2/3) * 1 = 2/3

  - (1/3) you initially picked correct, then change to a guaranteed loser.
  - (2/3) you initially picked incorrect, then change to a guaranteed winner.

I guess if we're sharing fitness plots, here's 1300 measurements and 7 DXA scans:

http://i.imgur.com/J4Ls2bQ.png

BIA is pretty bad. Here are ~1300 Fitbit Aria measurements matched against 7 DXA scans. The Fitbit bodyfat data (teal) is just random noise and can barely detect considerable changes in body composition.

http://i.imgur.com/J4Ls2bQ.png

Simple solution in Mathematica: http://i.imgur.com/2iBIRwN.png

Mathematica greatly expanded the space of things I can efficiently prototype. It's my starting point for almost any problem. If you find yourself saying "I don't want to waste my time coding that" or you resort to gut-feelings when data is available, Mathematica is an awesome tool to have in your problem-solving toolkit.