You do need to know it when you're working with subnets and routing tables.
Unless you have anything but a flat network structure with everything in one subnet, working with IPV6 is a giant PITA.
SpaceCadet
joined 1 year ago
It's not even about which view is right or neutral. On .world posts and comments critical of the US aren't mass censored like .ml does with posts critical of China, Russia or the former USSR.
I think it's supposed to evoke an image of an animal getting trapped in a tarpit.
IIRC, originally it was adding a delay on SMTP connections to keep spammers busy.
https://verifalia.com/help/email-validations/what-is-smtp-tarpitting
Honestly, even back in the day I hated the low-poly character model look of early 3D games in the late 1990s and thought it looked worse than the sprites we had before that.
In the old days we called it tar pitting.
Nah, reddit restoring comments is a myth. You just didn't delete all your comments, even though probably you thought you did.
See, Reddit, being the duplicitous bitch that it is, doesn't really show you all your comments when you go to your profile. It's limited to your last 1000 (?) comments or so, any comment that goes beyond that horizon is gone from your view forever, but it still exists in the thread.
The way to solve that is to first do a GDPR request. After a few weeks you will receive a zip file containing a file with all your comments and a link to it. You can then use an overwrite and delete tool and point it to this information. It will likely run for several hours or even days, depending on how many comments you made, because reddit throttles edit and delete requests, but it will effectively delete everything.
So it seems they do indeed clean up the modlog... my bans are still in there, but all mod actions where they removed China critical comments are no longer there.
It's a documentary.
I'm not sure how they accomplish that
If they have database access, which they would have being the admins, they can do anything.
- Red Hat Linux 5.1 - 7.x
- Slackware 7.0 - 12.0
- Ubuntu 6.10 - 9.10
- Slackware 13.37 - 14.1
- Mint 16 - 17
- Arch
It's when you have to set static routes and such.
For example I have a couple of locations tied together with a Wireguard site-to-site VPN, each with several subnets. I had to write wg config files and set static routes with hardcoded subnets and IP addresses. Writing the wg config files and getting it working was already a bit daunting with IPv4, because I was also wrapping my head around wireguard concepts at the same time. It would have been so much worse to debug with IPv6 unreadable subnet names.
Network ACLs and firewall rules are another thing where you have to work with raw IPv6 addresses. For example: let's say you have a Samba share or proxy server that you only want to be accessible from one specific subnet, you have to use IPv6 addresses. You can't solve that with DNS names.
Anyway my point is: the idea that you can simply avoid IPv6's complexity by using DNS names is just wrong.