Post B5HDIMT0oZx3OAPb9c by tchambers@indieweb.social
 (DIR) More posts by tchambers@indieweb.social
 (DIR) Post #B5C7D8NOCn4uix6fDs by apps@toot.fedilab.app
       0 likes, 0 repeats
       
       #HolosDiscover now has a public federation and moderation policy page. It explains how instance blocks work (trusted denylists, manual blocks, automated bridge detection), how to report illegal content, and how instance admins can appeal a block. The full list of blocked instances is available on the stats page.More: https://discover.holos.social/federation-policy
       
 (DIR) Post #B5C7vwTpHWrkrNU1wG by deutrino@mstdn.io
       0 likes, 0 repeats
       
       @apps love this!
       
 (DIR) Post #B5CBZiEvwgJu8mAn8S by deutrino@mstdn.io
       0 likes, 0 repeats
       
       @apps I took the time to read thru it all and the fediblock policy is implemented & described exactly as I wish such policies were managed on every instance. also read the How It Works page. I'm impressed. this is good stuff.
       
 (DIR) Post #B5CBZiSl7HNYpedpgW by apps@toot.fedilab.app
       0 likes, 0 repeats
       
       @deutrinoThank you for taking the time to read through everything. That means a lot, especially from a person following my work for a long time. Transparency and consent are at the core of how Holos Discover works, so this kind of feedback is really appreciated.
       
 (DIR) Post #B5CBZjC8OZfv6Ns4PY by deutrino@mstdn.io
       0 likes, 0 repeats
       
       @apps 2 things came to mind:1. it'd be cool if a whole instance could set a default opt-out. (it'd also be cool if single users of that instance could still opt in, but that's less important.)2. I can imagine disabling "search engine" indexing but still wanting to opt in to Holos Discover: if I don't want to be on web search engines but do want to be on ActivityPub-native search engines. this is a limit of the profile option granularity, but as an interactive bot, Holos could work around it…
       
 (DIR) Post #B5CCLEjyvTcKYBMBXM by apps@toot.fedilab.app
       0 likes, 0 repeats
       
       @deutrinoHolos Discover already supports explicit opt-in via mention commands. Currently the indexable flag is still required, but since a direct mention is an explicit choice made by the user, it would make sense to allow it even when the indexable is off. That way someone could opt in to a consent-based Fediverse search engine while staying off traditional ones. I will look into it.
       
 (DIR) Post #B5CD5rSDK4BbwGHJiK by deutrino@mstdn.io
       0 likes, 0 repeats
       
       @apps yeah, my thought was maybe it could be double opt-in if their indexable flag is off: the bot could reply "are you sure? your indexable flag is off" or similar.
       
 (DIR) Post #B5CDIdtv1YwLfXKcr2 by deutrino@mstdn.io
       0 likes, 0 repeats
       
       @apps absolutely. I'm *really* hoping to contribute some pull requests in the future, even if it's just documentation. I also chat with your deputy sysadmin just about every day so it's at least plausible!
       
 (DIR) Post #B5CDVOzblQUPCF4q2a by apps@toot.fedilab.app
       0 likes, 0 repeats
       
       @deutrinoGood idea. A confirmation via DM when the indexable flag is off would work well. One challenge is the language: the confirmation message needs to be understandable, otherwise it could confuse users who do not read English.
       
 (DIR) Post #B5HDIMT0oZx3OAPb9c by tchambers@indieweb.social
       0 likes, 0 repeats
       
       @apps Why block Bridgyfed? They have a very similiar policy to your own respecting permission and conscent for briding Bluesky accounts to the Fediverse?
       
 (DIR) Post #B5HDIMg81oRY2qY4bA by apps@toot.fedilab.app
       0 likes, 0 repeats
       
       @tchambersBridgyFed sets indexable to "true" for all bridged Bluesky accounts. AT Protocol has no equivalent setting, so users cannot opt out. Holos Discover relies on this flag to determine consent, so bridged accounts are excluded to respect the indexable opt-out flag.
       
 (DIR) Post #B5HEssWlByDTCZ8q00 by tchambers@indieweb.social
       0 likes, 0 repeats
       
       @apps Hmmm. I thought It is opt-in. You must follow @ap.brid.gy on Bluesky to activate your bridge. So by definition if they are bridged, they opted in, even if ATproto doesn’t have that setting. Did I get that wrong?
       
 (DIR) Post #B5HEsslIJvqHvdwRea by apps@toot.fedilab.app
       0 likes, 0 repeats
       
       @tchambersI think there is a missing step because opting into the bridge means consenting to be federated, not to be indexed. These are two different things. Once bridged, indexable is hardcoded to true and the user has no way to change it.