kbin.social disallows crawlers to index the site. And honest crawlers will honor that.
https://kbin.social/robots.txt

This actually seems to be the standard configuration that kbin ships with, so most instances will have that in place.

You actually can prevent this easily with CSP (content security policy). That header tells your browser which adresses it is allowed to load additional data from when visiting your site. It is an important tool to prevent cross-site scripting attacks, your browser should not load data from random sources when it is on your site.
Of course you would have to funnel all inline images through a site-local proxy that the browser is allowed to load data from.

This also has not only security implications, but also with the GDPR. Some jurisdiction consider ip addresses as personal data. Sending them to e.g. the US without user consent would be a violation. I know it is stupid to consider ip addresses as personal data and it is stupid to consider a browser loading data as sending that personal data somewhere on the sites' behalf. But there is a reason why a lot of websites for example only embed tweets after you explicitely allow it.

There is no guarantee that the delete request reaches all other instances as there is no kind of synchronisation protocol. If that delete request never reaches the other instance for whatever reason, the post stays online.

🤷‍♂️
It is just a decision that every instance owner can make for themselves (if they are aware of it).

It will be a huge headache for search engines anyways, all posts are basically replicated across all instances and look local to a search engine. So for a single post it will have hundreds of copies in its database and probably outputting all of them as results (for now).

I use Docker Mailserver . It is pretty lightweight, but it does not come with any fancy GUI for configuration, that is done on the command line mostly.

If you have configured that tailscale node as Subnet Router or Exit Node then yes, that is supposed to happen.

It is pretty straight forward if you use the provided docker-compose file with the nginx internal proxy in it. Just add traefik as per usual to the internal port 8536 of the proxy container.

They announced to build in plug ins like for WolframAlpha, so maybe that is where it is pulling this data from.

You mean, like a Browser addon?

Seems to throw some errors with Violentmonkey on Firefox. Haven't looked too deep into it yet though.

Maybe some day, when Tampermoney decides to opensource their code again 😉