heaths.dev heaths.dev Looks like standard.site is adding a recommend type to their lexicon: https://pdsls.dev/at://did:plc:re3ebnp5v7ffagz6rb6xfei4/com.atproto.lexicon.schema/site.standard.graph.recommend
We could add a component to add/remove the record. Pckt looks like they are implementing it as a star based on https://bsky.app/profile/standard.site/post/3mkkrqfrq5k2q
Yeah I dig this!! I'm not positive of when I might have time to build this but I like the idea
Given how much overlap there is with the subscribe button, what if we just combine these into the same component like a horizontally stacked flex grid of thumbs up/heart (configurable) followed by "Subscribe with ..."?
The components are already a far bit of JS, or maybe sequoia add component could dump a separate file for shared code.
Which - a separate shared file, or just stack the buttons next to each other?
I figured they could also be configurable, or at least the like button. Seems odd to support disabling the subscribe button when the component is called sequoia-subscribe, but turning off the like button makes sense. I figured leave either on by default to better advertise it's there.
Horizontal stack with some defaults + option to configure sounds like the best approach and follows what we already have. They are getting a little big but I think its better than adding some kind of shared file. Might be something we can think about in regards to future proofing the components and making them scale.
Just got to thinking: being in the same script doesn’t mean they have to be in she same virtual root. In fact, I wonder if there’s enough shared code to justify a single script for all existing components as well.
Just wanted to note that https://standard.site now documents the site.standard.graph.recommend record type:
document: string:at-uricreatedAt: string:datetime
If we did this, it’d be nice to share auth with the subscription component. Maybe we should use cookies as a preferred solution since those usually roam with profiles. We could fall back to isolated storage for compat.
Then, if you end up doing the CDN idea, at least the (remote) cookie option is already in place.