Bridged Bluesky posts use incorrect canonical URL #9
Labels
No labels
bug
contribution welcome
duplicate
enhancement
good first issue
help wanted
invalid
question
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
tom79/Holos-Discover#9
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
For instance, clicking the "view original" button on this post should link to https://bsky.brid.gy/r/https://bsky.app/profile/did:plc:2mw5ieis5wfyqsblq4z7vvox/post/3mgulttqvs22l, but instead links to https://bsky.brid.gy/convert/ap/at://did:plc:2mw5ieis5wfyqsblq4z7vvox/app.bsky.feed.post/3mgulttqvs22l
The server should not index bridged Bluesky posts because the bridge forces indexable to true, and Bluesky users have no way to opt out from their profile. That is why I started blocking the Bluesky bridges. I still need to automate this process, but the fix will not be necessary for this reason.
If I'm not mistaken, Bluesky itself has an "index my posts" option in settings and the bridge uses that to decide whether to apply the flag. Feel free to reopen if that changes anything :P
Thanks for the input. I checked the bridge source code (granary) and indexable is hardcoded to true regardless of the user's Bluesky settings. The "index my posts" option on Bluesky has no effect on the ActivityPub side.
Got it! Will chat with the owner and see if anything can be done about that. Thanks!
Hey @tom79, Bridgy Fed dev here, sorry for the trouble! I'm guessing the Bluesky setting you all are talking about is for whether people can see your profile and posts if they're not logged in, not for search indexing: https://bsky.app/profile/safety.bsky.app/post/3khhw7s3rtx2s ?
That setting probably does affect indexing in external search engines, but only implicitly. More importantly, if you turn that on, your posts are still full text indexed and searchable in Bluesky's own search engine. That's different from the fediverse
indexablefield on actors, which is why Bridgy Fed currently always sets that to true for bridged Bluesky actors.(Still totally up to you whether you include Bluesky users in Holos Discover, of course!)
Chiming in here: I think that including Bluesky users is a good idea, because the bridge itself is opt-in and it's been very useful in allowing me to search bridged content (Bridgy Fed has no authoritative search function currently, and Holos seems to provide the best search I can find for bridged stuff).
Reopening: Have just realized that even if the main instance does not index these posts, someone else might want to run one that does, and so this bug should probably be fixed regardless.