Hacker News new | ask | show | jobs
by Todamont 2727 days ago
> So I think it's great to have these kind of blocklists available to pods / servers / whatever instances, but I would like to see it as opt in, and selectivley able to opt out of whichever ones for any reason by the server / instance operator, and I think it should be optional for the users to opt out of whichever blocklists as well.

Yes, I agree with this. The end effect of this will be self-partitioning of the network, however, I think.

There are actually some pods who do a great job of tracking down bad users, and they have a full staff, and I trust their podmins. I should be able to offload a lot of the work of gatekeeping a TOS standard, to them, if I desire.

I totally agree it should be optional too. I clearly stated that in my posts to the D* github issues. But they just banned me, said trying to take action to moderate CP off the network was censorship, and they were going to ban me for it, ironically. That's when I started suspecting the D* core devs may actually be protecting their CP network, or even possibly profitting from the CP on their network.