With #HolosDiscover we checked multiple criteria before indexing: "indexable" enabled, account not locked, no #nobot or #noindex in bio, not in opted-out list, only public posts.
-
With #HolosDiscover we checked multiple criteria before indexing: "indexable" enabled, account not locked, no #nobot or #noindex in bio, not in opted-out list, only public posts. Every deletion, edit or block was processed instantly via #ActivityPub.
Google uses that same "indexable" flag but ignores everything else, keeps deleted content cached for weeks.
We shut it down after pushback. Was that the right call? Don't hesitate to share, this concerns the whole Fediverse.@apps I see no problem with this approach
generally opt-in is better than opt-out, so if there's a way to make it opt-in even for people on servers that allow indexing by default that would probably decrease the backlash, but like... If we don't want our posts indexed, we can turn indexing off and it seems y'all were respecting that so I don't mind -
With #HolosDiscover we checked multiple criteria before indexing: "indexable" enabled, account not locked, no #nobot or #noindex in bio, not in opted-out list, only public posts. Every deletion, edit or block was processed instantly via #ActivityPub.
Google uses that same "indexable" flag but ignores everything else, keeps deleted content cached for weeks.
We shut it down after pushback. Was that the right call? Don't hesitate to share, this concerns the whole Fediverse.We were caught off guard by the reactions and acted quickly. But we want to give the community a voice. We'll follow the result of this poll: if it should have stayed up, we'll reopen the source code and bring the service back.
-
With #HolosDiscover we checked multiple criteria before indexing: "indexable" enabled, account not locked, no #nobot or #noindex in bio, not in opted-out list, only public posts. Every deletion, edit or block was processed instantly via #ActivityPub.
Google uses that same "indexable" flag but ignores everything else, keeps deleted content cached for weeks.
We shut it down after pushback. Was that the right call? Don't hesitate to share, this concerns the whole Fediverse.@apps if an account is marked as indexable, just index it. If the default is wrong, that's the instance admin fault, nit yours.
If Google can index it you can too.
If people are unhappy with the setting of their profile, they can change it or blame the software or the admin and not people of good faith like you.
Public toots are talking to the world in a megaphone by design, expecting privacy is absurd
-
@lexinova
The debate goes beyond that. The real question is why developers chose to enable "indexable" by default when creating an account. A default opt-in is effectively an opt-out. That's where the conversation should start.@apps this 100℅ the wrong people in being blamed here
-
@apps if an account is marked as indexable, just index it. If the default is wrong, that's the instance admin fault, nit yours.
If Google can index it you can too.
If people are unhappy with the setting of their profile, they can change it or blame the software or the admin and not people of good faith like you.
Public toots are talking to the world in a megaphone by design, expecting privacy is absurd
@lutindiscret
We panicked quickly because things escalated beyond what we expected. But we still believe our approach was far more respectful than what's already happening: the same data is being exploited by others without users even knowing. At worst, we raised awareness. -
With #HolosDiscover we checked multiple criteria before indexing: "indexable" enabled, account not locked, no #nobot or #noindex in bio, not in opted-out list, only public posts. Every deletion, edit or block was processed instantly via #ActivityPub.
Google uses that same "indexable" flag but ignores everything else, keeps deleted content cached for weeks.
We shut it down after pushback. Was that the right call? Don't hesitate to share, this concerns the whole Fediverse.@apps Tough one: I feel like you did set it up respectfully, so it should have stayed up. BUT taking it down when people voice concerns and objected was also the right thing to do, both morally and for the reputation of the Holos project.
-
We were caught off guard by the reactions and acted quickly. But we want to give the community a voice. We'll follow the result of this poll: if it should have stayed up, we'll reopen the source code and bring the service back.
@apps maybe make a post for the most used (mastodon), on witch settings change for people that do not want to allow this.
As they may have missed this or misunderstood what the switch did
And since one of the two is recommemded, it may make them allow thing they actually don't want
some may misunderstand both settings:
- Include public posts in search results
- Feature profile and posts in discovery algorithms -
We were caught off guard by the reactions and acted quickly. But we want to give the community a voice. We'll follow the result of this poll: if it should have stayed up, we'll reopen the source code and bring the service back.
@apps Fediverse search engines are a contentious subject with a bad history, so I undestand you shutting it down.
While I'm fine with it, many people are very against things like that.
-
With #HolosDiscover we checked multiple criteria before indexing: "indexable" enabled, account not locked, no #nobot or #noindex in bio, not in opted-out list, only public posts. Every deletion, edit or block was processed instantly via #ActivityPub.
Google uses that same "indexable" flag but ignores everything else, keeps deleted content cached for weeks.
We shut it down after pushback. Was that the right call? Don't hesitate to share, this concerns the whole Fediverse.@apps@toot.fedilab.app accidentally voted wrong. I think it should stay. Search on small instances suck.
-
With #HolosDiscover we checked multiple criteria before indexing: "indexable" enabled, account not locked, no #nobot or #noindex in bio, not in opted-out list, only public posts. Every deletion, edit or block was processed instantly via #ActivityPub.
Google uses that same "indexable" flag but ignores everything else, keeps deleted content cached for weeks.
We shut it down after pushback. Was that the right call? Don't hesitate to share, this concerns the whole Fediverse.@apps the things that concerned me at the time were, in the initial announcement, 'we follow every signal' but only in this post did we know what signals you were following; and language of 'people may have misunderstood the defaults' which unfortunately rhymes with what less conscientious organisations say to justify hoovering all the things
if i had known the list of things you were looking at, i would have simply checked them and slept well. i didn't, so i blocked the bot, which now proves to have been unnecessary
-
@apps maybe make a post for the most used (mastodon), on witch settings change for people that do not want to allow this.
As they may have missed this or misunderstood what the switch did
And since one of the two is recommemded, it may make them allow thing they actually don't want
some may misunderstand both settings:
- Include public posts in search results
- Feature profile and posts in discovery algorithms@lexinova
We can't change how Mastodon presents those settings, but we had a page explaining how the service works and how to opt out per platform. We'll communicate even more clearly if the service comes back.Worth noting that this opt-in by default setting also allows Google to index fediverse profiles, except they don't check for consent at all. This is a much bigger issue that goes way beyond our project, which actually tries to do things the right way.
-
@lutindiscret@mastodon.libre-entreprise.com @apps i can see a case where someone is fine with other fedi instances indexing known posts, but not bots or external services
-
@lutindiscret
We panicked quickly because things escalated beyond what we expected. But we still believe our approach was far more respectful than what's already happening: the same data is being exploited by others without users even knowing. At worst, we raised awareness.@apps
You're right, and you're good people.However, people posting on social media expecting their postings to be private are Just Wrong.
And I will add that they're the ones making mastodon toxic at times, and I'm sorry you were a victim of them.
@lutindiscret -
@apps the things that concerned me at the time were, in the initial announcement, 'we follow every signal' but only in this post did we know what signals you were following; and language of 'people may have misunderstood the defaults' which unfortunately rhymes with what less conscientious organisations say to justify hoovering all the things
if i had known the list of things you were looking at, i would have simply checked them and slept well. i didn't, so i blocked the bot, which now proves to have been unnecessary
In the initial post, that sparked the discussion and led to the shutdown, there was a link to an article with an even deeper explanation. Maybe you didn't get it 'because federation' but it has been explained in detail from the start.
CC: @apps@toot.fedilab.app
-
@lexinova
We can't change how Mastodon presents those settings, but we had a page explaining how the service works and how to opt out per platform. We'll communicate even more clearly if the service comes back.Worth noting that this opt-in by default setting also allows Google to index fediverse profiles, except they don't check for consent at all. This is a much bigger issue that goes way beyond our project, which actually tries to do things the right way.
The fediverse is built app-centric, where people build their own particular app functionality and use cases and then try to get a reasonable amount of interoperability with other apps (or only with themself in some cases).
I think the general issue is that in building a consent mechanism an app should not depend on consent mechanisms of other apps.
The fact that Mastodon does something with Indexable flag, and provides config settings in the UI is pure app-specific and not protocol functionality, not a native capability of the social network that can be relied upon.
-
With #HolosDiscover we checked multiple criteria before indexing: "indexable" enabled, account not locked, no #nobot or #noindex in bio, not in opted-out list, only public posts. Every deletion, edit or block was processed instantly via #ActivityPub.
Google uses that same "indexable" flag but ignores everything else, keeps deleted content cached for weeks.
We shut it down after pushback. Was that the right call? Don't hesitate to share, this concerns the whole Fediverse.@apps
To be honest, I didn't understand any of what you wrote. Is there a page explaining the issue? -
With #HolosDiscover we checked multiple criteria before indexing: "indexable" enabled, account not locked, no #nobot or #noindex in bio, not in opted-out list, only public posts. Every deletion, edit or block was processed instantly via #ActivityPub.
Google uses that same "indexable" flag but ignores everything else, keeps deleted content cached for weeks.
We shut it down after pushback. Was that the right call? Don't hesitate to share, this concerns the whole Fediverse.So this dead horse flinched again
"With #HolosDiscover we checked multiple criteria before indexing: "indexable" enabled, account not locked, no #nobot or #noindex in bio, not in opted-out list, only public posts."
I'll copy-pasta with only slight edits:
My entire point (all the noise notwithstanding) focused on
Default opt-in versus default opt-out
This is an agent --> recipient transaction
Default opt-in: the recipient is opted into (and receives) the agent's action whether the recipient --> knows of <-- the action or not
Default opt-out: the recipient is opted out of (and cannot receive) the action whether the recipient --> knows of <-- the action or not
Neither default opt-in nor default opt-out have any logical meaning if
--> THE RECIPIENT DOES NOT KNOW OF THE AGENT <--
in advance
There was no mechanism for prior notification *before* indexing
People would have had to stumble on what you're doing, by how, exactly?
How dose the recipient learn of what you've done *before* you do it?
-
So this dead horse flinched again
"With #HolosDiscover we checked multiple criteria before indexing: "indexable" enabled, account not locked, no #nobot or #noindex in bio, not in opted-out list, only public posts."
I'll copy-pasta with only slight edits:
My entire point (all the noise notwithstanding) focused on
Default opt-in versus default opt-out
This is an agent --> recipient transaction
Default opt-in: the recipient is opted into (and receives) the agent's action whether the recipient --> knows of <-- the action or not
Default opt-out: the recipient is opted out of (and cannot receive) the action whether the recipient --> knows of <-- the action or not
Neither default opt-in nor default opt-out have any logical meaning if
--> THE RECIPIENT DOES NOT KNOW OF THE AGENT <--
in advance
There was no mechanism for prior notification *before* indexing
People would have had to stumble on what you're doing, by how, exactly?
How dose the recipient learn of what you've done *before* you do it?
@FinchHaven @apps so you would like to be asked everytime a search engine wants to index your profile? That's like the cookie popups, I will just stop reading them at some point.
-
@FinchHaven @apps so you would like to be asked everytime a search engine wants to index your profile? That's like the cookie popups, I will just stop reading them at some point.
This is the old, worn out Fediverse "Well anybody can search the Internet any time they want to so why do you care?"
Which 1) most people cannot, lacking the technical expertise, and 2) most people don't want to have happen to them anyway
<snip>
cc @apps
-
This is the old, worn out Fediverse "Well anybody can search the Internet any time they want to so why do you care?"
Which 1) most people cannot, lacking the technical expertise, and 2) most people don't want to have happen to them anyway
<snip>
cc @apps
@FinchHaven @apps huh, that's not what I meant
The way I understood you, is that opt-in and opt-out don't work because the user doesn't know what service wants to do what with their profile.
Which to me sounded like you want to get a notification and decide manually everytime a service wants to index your profile. Did I get that wrong?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login