I use Lammy Connect for my client. I can block on user and instance. For a blocked instance, user comments from that instance are collapsed be default. This is useful since you can still see the context of a thread without getting exposed to any potential weirdness while still being able to see normal conversations. (There may be ways to fully block the comment, but I am too lazy to dig into the settings.)

Report this slop spammer.

It’s useful to keep the 16 million IoT devices you have running on WiFi segregated a bit.

Thanks for the correction on the the broadcast address, btw. The details are important.

At home, I have 172.16/12 scoped out for my cluster subnet and just use the second and third octet to denote service function. It’s excessive scoping, but it’s an internal scope for a private network and broadcasts are generally contained to the cluster network. It would be trivial to split that into a 172.16/16 if I ever had the desire. (Speaking bluntly, it really doesn’t matter much in this case. I’ll need to split it out to keep Longhorn traffic segregated later, but it’s not an issue now.)

The rest of the network is reasonably scoped out across 192.168 ranges and chopped up across a few VLANs.

My addressing scheme is split into “public” and “stay the fuck out”, with most 172 addresses being the latter. At home this is great. In a large network, scoping out such a large 172 subnet could be detrimental. (“It depends” on the detrimental bit and requires proper planning and understanding about why subnets were even built into IPv4 from the get-go.)

Edit: Most addressing is static on my cluster network, with DHCP only handing out addresses based on MAC address. The 172 subnet has very restricted dynamic IP ranges.

Regardless of what is what, it’s a scheme I recognize and that is the more important bit.

255 is reserved for broadcast.

Edit: Yes, 255 is technically not ‘reserved’ by itself. I was only thinking about the addresses scoped to /24 for a simple answer. A broadcast address is reserved, though.

When in doubt: https://www.calculator.net/ip-subnet-calculator.html

Feature detection in images is extremely light weight so it seems that it would be fairly trivial to detect someones wang before the stream is encrypted in the first place. There is likely already a ton of processing done on raw camera data before it’s encrypted and sent off-device anyway.