Show newer

@georgia

So its just his personal opinion, not something quantifiable?

I dunno, dont get me wrong the USA is horrific in terms of inciting war.. but actual war crimes, we arent innocent but I can think of far worse places in that regard.

It also comes down how it is measured. The USA is much younger as a country so weve had far less time to accumulate atrocities if we are talking over the course of the nations life. If we are talking just modern day history then Israel, Russia, Darfur, and many places come to mind that have been far worse in terms of war crimes.

@tuxcrafting @igel

@abloo

But since **you** are not indexed then the only way youd be associated with it is if someone went to said hellthread and actually read it (since any search for your name or references to you wont come up).

People can find you in that thread in that way whether you wanted to be found or not already.

@fedisearch @hansw

@abloo

Sure, but they obey noindex, noarchive, and robots.txt.

So anyone who does not wish to be indexed they honor. So while I agree many people do not wish to be indexed, and I think they should have that right, its hard for me to see what the problem is here, you wont be.

Or are you suggesting indexing the people like me who actually do want to be indexed is somehow harmful to you?

@fedisearch @hansw

@hansw

However if you truly feel the standard we have now is inadequate then I'd say the solution would be to petition to have the standard amended, and then you would still have the task of ensuring instances adopt the standard.

@fedisearch @fedisearch_com

@hansw

If an instance like hubzilla doesnt allow individuals to opt-out then the sys admin still has the ability to opt-in or opt-out the entire server. The users know about that. I agree it is unfair to the users they dont have the power to control that, but the fault lies with the hubzilla developers, not with fedisearch.

I assume by verified opt-in you mean someone going to fedisearch and only being indexed if they specifically ask to be by submitting a form. To me, that is not a good solution I would recommend. Most people either want to be indexed by all search engines, or none at all. By using a system like that it would make it impractical for someone who wishes to be indexed to have the burden of reaching out and contacting every search enginer in existence.

I'd much prefer to stick to standards and where those standards arent implemented, then put the pressure on the people to implement them rather than to put the blame ont he search engines who honor the standards and those standards, when implemented, give you complete power and control over if you are indexed.

@fedisearch @fedisearch_com

@hansw Here is the command you can run to see its in raw html and no need to run or parse js to see it:

# curl -s qoto.org/@hansw | grep noindex

<meta content='noindex, noarchive' name='robots'>

@hansw The header I pasted was **not** from js, it was the header in the HTML from your profile page. I linked you to it. No one has to parse any js.

@hansw

I'm not excluding anyone. The developers didnt add that feature in. They cant and shouldnt expect to magically have the benefits of a feature that doesnt exist on their platform. Obviously if that is important to them they should either use a different platform or add the feature to their own platform (it is open source afterall).

There is a standard in place, fedisearch obeys it (aside from the caveat of that bug they seem to want to fix). Some platforms utilize that standard for the benefit of their users.

The fact that some platforms dont use the standard that is in place and honored by fedisearch, is entierly an issue of the software, and that is where any solutions should come from. It is why we have these standards.

@fedisearch @fedisearch_com

@hansw Was that response intended for me? You didnt reply to me. What exactly is in a js script?

@hansw

Whos fault it is matters because that determines who is going to fix it.

If the wrong party attempts to fix it you wind up with a hacked solution that isnt going to be useful across platforms.

The simple solution to this from fedisearch side, and what I'd personally recommend, would be to check each profile of a reply and see if it has a no-index metatag. If it does then dont index the reply.

This would be an easy solution, standards compliant, and would address your concerns in as reasonable a way as is possible.

@fedisearch @fedisearch_com

@hansw Thats not what I see.

Here is the header to your profile found here: qoto.org/@hansw

Notice it clearly shows the noindex meta tag:

<!DOCTYPE html>
<html lang='en'>
<head>
<meta charset='utf-8'>
<meta content='width=device-width, initial-scale=1' name='viewport'>
<link href='/favicon.ico' rel='icon' type='image/x-icon'>
<link href='/apple-touch-icon.png' rel='apple-touch-icon' sizes='180x180'>
<link color='' href='/mask-icon.svg' rel='mask-icon'>
<link href='/manifest.json' rel='manifest'>
<meta content='/browserconfig.xml' name='msapplication-config'>
<meta content='' name='theme-color'>
<meta content='yes' name='apple-mobile-web-app-capable'>
<script src='/MathJax/MathJax.js?config=TeX-AMS-MML_HTMLorMML'></script>
<title>Hansw (@hansw) - Qoto Mastodon</title>
<link rel="stylesheet" media="all" href="/packs/css/common-e281f04d.css" />
<link rel="stylesheet" media="all" href="/packs/css/default-d020ef5f.chunk.css" />
<script src="/packs/js/common-775c8ec529edaf44f31d.js" crossorigin="anonymous"></script>
<script src="/packs/js/locale_en-f3268010560d3c65b6ad.chunk.js" crossorigin="anonymous"></script>
<meta name="csrf-param" content="authenticity_token" />
<meta name="csrf-token" content="rLJZl3ckevfm8BvgGGhLmdSijRspf33MJwodLHqpPE25lULJrdolnLlPb7xfzNv/AWkC7GgsiFgSAZBHIRSi+w==" />
<link rel="stylesheet" media="all" href="/custom.css" />
<meta content='411 Toots, 31 Following, 26 Followers · See my pinned post :-)' name='description'>
<meta content='noindex, noarchive' name='robots'>
<link href='qoto.org/@hansw.rss' rel='alternate' type='application/rss+xml'>
<link href='qoto.org/users/hansw' rel='alternate' type='application/activity+json'>
<link href='qoto.org/@hansw?max_id=1044124' rel='next'>
<meta content="profile" property="og:type" />
<meta content='411 Toots, 31 Following, 26 Followers · See my pinned post :-)' name='description'>
<meta content="qoto.org/@hansw" property="og:url" />
<meta content="Qoto Mastodon" property="og:site_name" />
<meta content="Hansw (@hansw)" property="og:title" />
<meta content="411 Toots, 31 Following, 26 Followers · See my pinned post :-)" property="og:description" />
<meta content="storage.gra.cloud.ovh.net/v1/A" property="og:image" />
<meta content="120" property="og:image:width" />
<meta content="120" property="og:image:height" />
<meta content="summary" property="twitter:card" />
<meta content="hansw@qoto.org" property="profile:username" />

@hansw

As for the larger issue about indexing in a fedeerated environment, I agree its a tricky one.

Consider this, if this were a manual blog you might make some post about something or another and label it as no-index.. sure that seems great.

But me as a blogger who does have an indexed site might wish to quote you in my reply, perhaps I disagree with you. so now part of your content, and a link to it will be on my indexes site. Your content got indexed by proxy.

Whose fault is this, the search engine? or the blog software, or the blogger? Whats the solution, do we have one?

@fedisearch @fedisearch_com

@hansw

I just checked, it does indeed add a noindex tag.

Go to your profile page and look at the source for it, you opted-out and youll find the following in your header:

<meta content='noindex, noarchive' name='robots'>

Then go to my profile, I opted in to search indexing, you will see there is no noindex tag on my profile page.

So it does in fact seem to work via the noindex standard, which fedisearch is compliant on.

@fedisearch @fedisearch_com

@rw

There are some non-primary colors used int he image as well.

I do find it interesting that red behaves differently, though not surprising. Our eyes do tend to notice red more strongly than other colors.

@Liberonscien

@hansw

Thanks, I looked a minute ago before I asked and somehow missed that.

Let me look into how this works exactly, but my guess is it adds a noindex meta tag to the html of your profile.

If so then @fedisearch would, under most situations, honor your opt-out request and not index you. Admittedly there may still be an issue with replies getting indexed, but as you said they admit that is a problem and intend to fix it.

So seems like with the exception of the bug you mentioned (which they seem to intend on fixing) then your main concern is already addressed on mastodon at least, you do have the ability to opt-out / opt-in

@fedisearch_com

@hansw

Where in the settings in astodon d you see the ability to opt out of search indexing?

@fedisearch_com

Show older
CleverLibre Social

CleverLibre Social is an inclusive social instance for open discussion, learning, and community.
All cultures welcome.
Hate speech and harassment strictly forbidden.