@mirabilos@oil Is there a technical mechanism that needs to be created to make it clearer how these are meant to be treated? How can search engines understand what you'd like to have happen better?
@johnmu@mirabilos@oil Protocols for this already exist and are very clearly defined, John, and if you work on search for Google, as you say, you are 100% aware of that already.
@johnmu Are you saying public search is explicitly allowed for profiles that opt out of public search? Because if that's the case that is a problem. But as far as I know, it is not the case and there is no problem with the current configuration. cc: @Gargron
@tokyo_0 Yes, those protocols exist - my team recently standardized some of them as an RFC. And Mastodon implements some of them too. The problem is that as they're implemented now, public search is explicitly allowed. If this is not what's wanted, something needs to change.
@johnmu Yes, that is how it works. Why do you keep taking @Gargron out of these messages, John? He's the most knowledgeable, informed person on the very issue you say you came here to talk about, in your professional capacity working for Google. He (or someone he delegates this too, as he is a busy man) is the exact person you should be engaging with, and yet it seems you don't want to and instead are posting alarmist messages that Mastodon isn't working correctly
@tokyo_0 No. If a page has a noindex meta tag, it won't be indexed. However, if your reply appears on a page that isn't noindexed, then yes, your reply can be indexed, regardless of your profile settings.
@tokyo_0 For example, if you open this thread in an incognito window ( https://mastodon.social/@johnmu/109624277067784119 ) and use view-source, you'll see there's no "noindex" and your reply is there. As far as I can tell, you have the noindex option enabled, I don't.
@johnmu@Gargron Not sure about that. It doesn't match what I've seen on the clients I've used, but there are many differences across the federated servers and various interfaces. I do really think it's him or someone on his team you should be addressing some of these points to. There are some improvements that could be made to how Mastodon works right now. The channel for that is suggestions on Github or, for security based issues, there's an email address there.
@tokyo_0@Gargron The UI is set to overwrite the other folks mentioned, I thought that was on purpose, perhaps to avoid annoying people with notifications once they've received it once?