Revert "feat: add ipfs.pinksheep.whizzzkid.dev"

[whizzzkid]

Reverts #326

Turns out someone loaded a phishing form and reported the site for phishing to google, this is now blocking public gateway checker from testing everything. The cid that's problematic is: QmaMMPbpjEBqQMfksDTrto1usRpNat9xL6J6ocJ7YNSz3k

I am not sure what's the best way to block certain routes, is this functionality not built into kubo?

[lidel]

I am not sure what's the best way to block certain routes, is this functionality not built into kubo?

Not yet. A wider problem of vendor-agnostic way for distributing denylists was discussed in Lisbon during IPFS Camp.

@2color FYSA there is ongoing work around this:

• Filtering commands are missing in Kubo, tracked in IPFS filtering to allow node operators to decide on content they are willing to serve kubo#8492 (but blocked by the lack of list format for import/export – we need to do this correctly, and not have 99 competing formats)
  • Spec work to standardize composable llow/deny list format in IPIP 298: (allow|deny)lists for IPFS Nodes and Gateways specs#340
• (TBD, very wide brush strokes for now) When we have it, we can set up community services which detect phishing and add malicious CIDs to lists, and have implementations like Kubo ship with some lists enabled by default (while respecting user agency and leting users to change the lists, similar to EasyLists being enabled in adblocks like uBlock)

@whizzzkid you may want to move gateway to a different domain name, separate from whizzzkid.dev – see cautionary tale in https://nft.storage/blog/post/2022-04-29-gateways-and-gatekeepers/