On Tue, 11 Mar 2014 09:26:17 +0000, Rob Kendrick wrote:
> It requires some careful thought about where to put the encoding and
> decoding. Should it just be in the GUI? In the fetch layer? Or
> somewhere between?
I was adding it to the URL normalisation code (so "somewhere
inbetween"), as that seemed the logical place. You make a good point
about if it is in the GUI code, then the UI could show the encoded
version, which flags up scam addresses. However, one RFC I was
reading advises that the user ought to see the non-encoded version, so
in this respect the frontend only needs to deal with decoding the
addresses (although I'm not sure that's sensible without some advisory
warning icon).
Chris
No comments:
Post a Comment