quick rant - follow friction
#atdev : So I'm making an offprint component so people can follow me on semble, grain, currents, etc. BUT WHY?!?! Didn't we hype up shared social graph? Why are we replicating old friction?
I've heard the arguments for and against app.bsky.graph.follow use and that is not the point of this longform post.
So I'm making plea for better user experience.
1st login experience: let people know if you are using app.bsky.graph.follow, if you are, then no more steps are required
if you are using another schema: Immediately state follows are different here than Bluesky (yes Bluesky) "would you like to sync your follows?"
if yes: provide a selection screen + follow them all button!
offer ongoing sync, Add a keep follows in sync option in settings that users can run anytime. If you AREN'T going to build them an on going automated sync, build an @airglow.run automation and point them to it.
if you are serious about your at://app then you need to steal or remix this UX idea so we don't have Dead Apps
I'm sorry if this is a bit ranty for a sunday, but when an alpha tester like me realizes this is a problem it's already much larger!
Would also love it if @ecosystemaction.com would weigh in on this. They've been tackling this in a working group on 
ATProtocol Community Research Project for ATProto Ecosyste...
things i learned after this post:
@pckt.blog has a manual sync tool that writes blog.pckt.mini.follow for other standard site users
@sifa.id has a manual sync tool that syncs with @bsky.app and @tangled.org
