Don’t eat shit, mulch the rich.

Friends don’t let friends use Facebook.

Predestination [2014]

IBM : Nazi Party :: Google : IDF

https://www.techwontsave.us/episode/235_no_tech_for_apartheid_w_mohammad_khatami__gabi_schubiner

Advertising needs to become as socially acceptable as smoking.

It indiscriminately pollutes whatever environment it’s conducted within, and causes secondary harm to non-participants by incentivising hoarding of PII in the cheapest and least secure manner.

I create unique email addresses for every organisation and service I deal with, including an obfuscated date, so when an address is compromised I can nuke it with a hard rejection, and regenerate as needed. This all feeds into a catchall mailbox, with server-side sieve rules to filter the stuff I actually care about.

I besides some account specific and burnt addresses, I don’t actively track of any of the addresses I’ve created, it would be in the hundreds by now.

One benefit of this crazy setup is there’s one less common identifier to match across disparate data stores.

Finally, no one should do any of The above. From experience I consider it pathological.

Configuring multiple v4 addresses on an interface is a kludge, typically only used on hosts which apply inter-network routing logic. It’s an explicit, primary function of the standard v6 specifications.

With v4, you would use either RFC1918 and NAT, or plumb a public address to the host.

With v6 you should use a ULA and an address with a public prefix, and selectively open ports/services to on appropriate address.

An example is the file sharing and administration daemons on my NAS are only bound to its ULA. I don’t need to worry whether it will accidentally be exposed publicly through fat fingering my firewall config, because it will never route beyond my gateway.

I use ULA prefixes to ensure the management interfaces of my devices don’t leak via public routes.

It’s one of the unique parts of the standard IPv6 stack not back ported to IPv4, that an interface on any host can be configured with multiple addresses. It permits functional isolation with the default routing logic.

IPv6 is far from perfect, but the majority of the arguments I’ve seen against deploying it are a mixture of laziness, wilful ignorance, and terminal incuriosity.