3 ms·
How would encoding help? It's already encoded! That repo contains the bits: 0b11001100b11101010b11011100b11000110b11101000b11010010b11011110b11011100b11000010b1
by dschep 9y ago
How would encoding help? It's already encoded! That repo contains the bits:
0b11001100b11101010b11011100b11000110b11101000b11010010b11011110b11011100b11000010b11011000b11000110b11011000b11000010b11011010b1011100b11000110b11011110b1101101
which is the ASCII _encoding_ of the forbidden string.
Just because these bits are an EBCDIC cp500 encoding of that string doesn't make it less forbidden than an ASCII encoding:
0b100001100b101001000b100101010b100000110b101000110b100010010b100101100b100101010b100000010b100100110b100000110b100100110b100000010b100101000b10010110b100000110b100101100b10010100
Here's how I made both.. shows reasonably (IMO) that encoding is.. nothing.
> ''.join(bin(c) for c in 'functionalclam.com'.encode('ascii'))
> # vs this:
> ''.join(bin(c) for c in 'functionalclam.com'.encode('cp500'))
- tyingq 9y agoBecause of the light touch string matching that providers do before complying with a frivolous DMCA request. Most will deny the request if they dont see "the text". And reduced discoverability that your url is on my page in the first place. Even though a url isn't something you can copyright.