hmm 1 ipv4 1 registration is what i enforced, but there usually being thousands of ipv6s in one allocation makes that a bad criteria
11:02
Maybe one /64 one registration? But even that has issues, some ISPs are particularly retarded and don't understand the point of ipv6 so they give you only a /67
11:04
some ISPs give out entire /56s, that's 256 /64s you'd be able to register 256 times :D
11:04
heinrich5991: I bet you investigated this problem, did you come up with a scheme?
11:09
(they really should be assigning at the very least a /56 and IETF recommends an entire /48)
heinrich5991: well worst case you can register a server on every port of your ipv4 address, with ipv6 a single /64 contains sextillions of addresses * 65536 ports
Well a /48 is the suggested allocation per end-site as per IETF, and they also suggest that if they allocate a /56 they should still reserve the /48 if the end-site would require more
16:31
However, as I said there are ISPs that ignore the reccomendation and allocate a /64 instead and I'm not sure those people would be responsible enough to reserve atleast a /56 along with it
They are a budget company, I'm guessing their CEO probably doesn't know anything about networking and told the engineers a /64 would be more then enough for anyone
I still don't get the appeal of utf16 though, utf8 is perfectly capable of representing any character without requiring an extra byte for the most common character set and breaking legacy software
eh, some research reveals that utf-8 wasn't available in 1990 when ucs-2 was defined, so I'll only forgive the windowsfolk if they jumped on the ucs2 ship before 1993 when utf8 was released
17:08
I guess there was already utf1 but it was apparently too inefficient
hm, discord sucks, I don't know about ipv6, as I have not come across is enough to know whether servers are even given a whole subrange of ipv6 ips, currently hav enot seen this, so don't know ._.