this post was submitted on 23 Oct 2025
73 points (100.0% liked)
196
4675 readers
1678 users here now
Community Rules
You must post before you leave
Be nice. Assume others have good intent (within reason).
Block or ignore posts, comments, and users that irritate you in some way rather than engaging. Report if they are actually breaking community rules.
Use content warnings and/or mark as NSFW when appropriate. Most posts with content warnings likely need to be marked NSFW.
Most 196 posts are memes, shitposts, cute images, or even just recent things that happened, etc. There is no real theme, but try to avoid posts that are very inflammatory, offensive, very low quality, or very "off topic".
Bigotry is not allowed, this includes (but is not limited to): Homophobia, Transphobia, Racism, Sexism, Abelism, Classism, or discrimination based on things like Ethnicity, Nationality, Language, or Religion.
Avoid shilling for corporations, posting advertisements, or promoting exploitation of workers.
Proselytization, support, or defense of authoritarianism is not welcome. This includes but is not limited to: imperialism, nationalism, genocide denial, ethnic or racial supremacy, fascism, Nazism, Marxism-Leninism, Maoism, etc.
Avoid AI generated content.
Avoid misinformation.
Avoid incomprehensible posts.
No threats or personal attacks.
No spam.
Moderator Guidelines
Moderator Guidelines
- Don’t be mean to users. Be gentle or neutral.
- Most moderator actions which have a modlog message should include your username.
- When in doubt about whether or not a user is problematic, send them a DM.
- Don’t waste time debating/arguing with problematic users.
- Assume the best, but don’t tolerate sealioning/just asking questions/concern trolling.
- Ask another mod to take over cases you struggle with, if you get tired, or when things get personal.
- Ask the other mods for advice when things get complicated.
- Share everything you do in the mod matrix, both so several mods aren't unknowingly handling the same issues, but also so you can receive feedback on what you intend to do.
- Don't rush mod actions. If a case doesn't need to be handled right away, consider taking a short break before getting to it. This is to say, cool down and make room for feedback.
- Don’t perform too much moderation in the comments, except if you want a verdict to be public or to ask people to dial a convo down/stop. Single comment warnings are okay.
- Send users concise DMs about verdicts about them, such as bans etc, except in cases where it is clear we don’t want them at all, such as obvious transphobes. No need to notify someone they haven’t been banned of course.
- Explain to a user why their behavior is problematic and how it is distressing others rather than engage with whatever they are saying. Ask them to avoid this in the future and send them packing if they do not comply.
- First warn users, then temp ban them, then finally perma ban them when they break the rules or act inappropriately. Skip steps if necessary.
- Use neutral statements like “this statement can be considered transphobic” rather than “you are being transphobic”.
- No large decisions or actions without community input (polls or meta posts f.ex.).
- Large internal decisions (such as ousting a mod) might require a vote, needing more than 50% of the votes to pass. Also consider asking the community for feedback.
- Remember you are a voluntary moderator. You don’t get paid. Take a break when you need one. Perhaps ask another moderator to step in if necessary.
founded 9 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Just to be pedantic, but was this a valid IPv4 address before IPv6 came out? That mechanism of collapsing a single set of repeating octets of "0" is a feature of IPv6.
So the behavior we're seeing here, does this only result because that machine also supports IPv6?
No, this has been a part of IPv4 for a very long time. The behavior is defined here. There are also differences in how the collapse white space, primarily in that IPv6 can collapse multiple zero sections
While many systems support these funky IPv4 address formats, not all do. It's a bit of a quirk in that intimate knowledge of IPv4 addressing has largely been lost. If you search for validating IPv4 addresses on StackOverflow, most answers will simplistically check for 4 octets between 0 and 255
The only place I've seen these IPv4 address formats be relevant in the last 10 years is in security. If you're using a block list to block specific IP addresses (which is pretty dumb to do these days), you have to account for someone sending a request with their IP address in hex, octal, or shortened formats. If you block 127.69.69.69 (yes, I know that's a loopback), and are getting a request from 2135246149, will your block list recognize it as a blocked address? Many won't, but that's something you have to engineer for from a security perspective
What do you mean by that? The example did collapse multiple zero sections for IPv4 as well (127.69), and IPv6 can also only collapse one block, namely the longest one, otherwise it'd be ambiguous as to how to pad each. Or am I misunderstanding?
In IPv4, there is no way to indicate which octet is being skipped. Think of the address 127.0.69.69, which we'll use the equivalent of 1270:0000:0000:0000:0000:0000:0000:6969:6969 in IPv6 (yes, I realize that address space doesn't make sense. It's just for illustration)
In IPv4, you cannot shorten 127.0.69.69 to 127.69.69. The assumption with 3 octets is that the last two have been merged into one. 127.69.69 would be equivalent to 127.69.0.69
In IPv6, this ambiguity is removed. Double colons are used to indicate missing zeros. 1270::6969:6969 is equivalent to the above IPv6 address. Double colon simply pads out the address at that point until it is the correct length. I seem to recall some other interesting features of it, but I don't use IPv6 enough to remember them exactly
Ninja edit: There is also a bit of weirdness in IPv4 because it's not technically white space expansion as (I think) it is in IPv6. It's just putting multiple bytes into a single octet. That's why 127.257 or 127.0.257 would both resolve to 127.0.1.1
The IPv4 example collapsed two "blocks", ".000.000.", or rather octets, and could do so because they were next to one another, which looks to behave the same way IPv6 does. In IPv6 the largest number of all zero hextets can be removed and replaced with double colons. So multiple hextets ( .0000) can be removed in shortening as long as they are next to one another in the IP address.