I strong agree with dame.il's statement here, but I don't think it alone is enough. We can improve from here, by introducing a standard lexicon for exceptions to the base follow graph.
[Using Bluesky follow graph for apps] is my preferred pattern for atmosphere apps that are wanting to ”reuse” or “integrate” the bluesky social graph/lexicon
don’t make me automatically follow everyone i follow on bluesky, but make it easy to find/discover/import my bluesky social graph (or other social graphs) on my own terms
https://bsky.app/profile/dame.is/post/3miwdxegsr22z
This generally I think is the excepted baseline and is good for users and good for your app.
I also believe it is not enough. There are people who post endless dog photos that I do not want in my photo app feed. These are, imo, exceptions.
I propose we define a community.lexicon.exception.follow and .unfollow lexicon, that acts as an override atop the base user follow graph, in app specific applications. I could create an community.lexicon.unfollow record for grain.social for that dog user that drives me nuts.
We can give users a good out of box behavior, give them power, and avoid lexicon sprawl (of each app doing everything for themselves) with a lexicon for graph exemptions, defining new layers atop the base layer, for app specific changes. This feels like the best of all worlds.
It would also be incredible to be able to generally visualize what exceptions are out there, to see who is specifically followed only on one app, or to see who we unfollow on the other app, which would offer users incredibly cleaner views of what they are doing, without having to fetch follow lists and diff. In app specific ways. The user visibility to this approach I find also strongly compelling.
I strong agree with dame.il's statement here, but I don't think it alone is enough. We can improve from here, by introducing a standard lexicon for exceptions to the base follow graph.
https://bsky.app/profile/dame.is/post/3miwdxegsr22z
This generally I think is the excepted baseline and is good for users and good for your app.
I also believe it is not enough. There are people who post endless dog photos that I do not want in my photo app feed. These are, imo, exceptions.
I propose we define a
community.lexicon.exception.followand.unfollowlexicon, that acts as an override atop the base user follow graph, in app specific applications. I could create ancommunity.lexicon.unfollowrecord for grain.social for that dog user that drives me nuts.We can give users a good out of box behavior, give them power, and avoid lexicon sprawl (of each app doing everything for themselves) with a lexicon for graph exemptions, defining new layers atop the base layer, for app specific changes. This feels like the best of all worlds.
It would also be incredible to be able to generally visualize what exceptions are out there, to see who is specifically followed only on one app, or to see who we unfollow on the other app, which would offer users incredibly cleaner views of what they are doing, without having to fetch follow lists and diff. In app specific ways. The user visibility to this approach I find also strongly compelling.