@HLChttps://www.w3schools.com/tags/tag_datalist.asp Could use it on fedifinder's login page to prefill all those instances but still accept others. Although it seems like you've deliberately limited it for some reason? If so, why?
@Zerglingman Yea it's setup as a whitelist model because there are some gross instances on the fedi. Most of the time when people say that they mean somebody said the N word but I really don't care about that. I draw the line of acceptable public discourse at child sex. I have had to deny only a couple instances because, among other less offensive deviancy, I saw discussions of children's sexuality. I very quickly check out each user/instance that applies and if I see that kinda stuff it's a no.
@Zerglingman I wish it didn't have to be that way but I don't really see any way around it. I appreciate your volunteering useful coding suggestions regardless though. If you come up with anything else feel free to shout it out I will entertain any possible improvements.
@HLC Can't really solve moderation problems with programming. I think the only possible scenario for opening up access would be to maintain a blacklist of known pedo instances. Which probably wouldn't be that difficult unless one of them decides to go out of its way to fuck with you.
@Zerglingman It actually would be difficult but not because of any intentional fuckery. New instances pop up and old ones disappear constantly. To maintain a functional blacklist I would need to know about the newest pedo instances before they access FF. That's not something I want to do nor would it be easy since #fediblock -ers care more about the N word than MAPs.
I feel like what I have now is the best solution. It's a very low bar to entry. They send info, I vet for obvious pedo stuff, ez.