Alex's avatar

Alex

@alex.bsky.team
the passive pasadena thrill | bsky devrel
Alex's avatar
Joel Hill
I am writing a custom lexicon and when it came time to implement the Client and App View this was something I was struggling with. At the moment I’m content with a hybrid approach? I write to the PDS, I read from the App View. The only benefit I would get by writing records through the app view would be to apply stricter validation than I was able to write into the lexicon rules. It seemed pointless though, since I can’t really stop anyone from writing records to their PDS, it would be fighting a losing battle for no rewards. I do have an interesting case where I may actually need some server side processing power and a put method in the App View seems tempting, but I still may avoid it. Instead I’ll probably do quick simple writes of records, then have the app view process those events and prepare indexed data ready to consume through read requests to the App View.
Actually, this "hybrid approach" has a pretty well-established precedent (https://en.wikipedia.org/wiki/Command_Query_Responsibility_Segregation) and addresses the "time between '200 OK' and 'Bluesky servers index the record' is indeterminate" concern -- this might not be a bad thing to recommend.
Alex's avatar
Grace
I believe you mean 40 million users on bluesky :)
Yes, fixed :)
Loading more comments...