searchPost functionality is flakey / broken due to Bluesky API changes
#26
Comments
|
Thanks - yeah I had seen this post and hoped that the API would magically fix itself. But it's probably worth documenting the problem better and maybe offering better UX if it doesn't come back... (or just killing that feature entirely) |
searchPostsearchPost functionality is flakey / broken due to Bluesky API changes
|
Trying to get more clarification here, will see if it gets anywhere. |
|
I ran into this issue today. My latest deployment is not rendering the comments component. I will try to take a closer look at the issue over this weekend |
|
@r0hitm did you recently upgrade? I was wondering if this was a regression in the latest release (out yesterday) or whether it just coincided with the team taking the public API down again |
|
@czue nope, I have not upgraded anything. Wrote and published a new post as usual, and I noticed that the this post and none of the previous ones are rendering the comment component anymore. I did some lookup and landed on this issue |
|
Yeah, so my understanding of the latest state is that sometimes they get overloaded and then they disable public access to the API it uses until things settle down again. So I'm not sure there's an easy solution/workaround. |
|
got a message about this https://bsky.app/profile/bnewbold.net/post/3lnvhcghi6s23, sounds like it might be removed? Super unfortunate though since comments is such a good use case. |
|
Oof, well at least it would be nice to have some closure on this. Assuming they disable public access I'll probably just (at least in the short term) remove that feature. Bummer, but understandable! |
|
Just making a note for myself for the future: It might not be too hard to make a proxy app that handles this. You could basically make a public API where people can pass a username and a link and get back the right post. Behind the scenes this would hit the same API but with auth, so it at least goes through. That would still be subject to rate limits, but you could cache / persist the results so that you only ever query each user/link once (after you find a result), so that might be pretty sustainable. This is probably like a day of work to spin up, so not trivial, but potentially worth doing if there's enough demand or I'm feeling bored sometime. |
@czue yeah i was thinking of that too in hzoo/extension-annotation-sidebar#8, tho in my case i would probably cache the all results of the search itself since it's more for all comments vs the one the author made |
From your blog:
The text was updated successfully, but these errors were encountered: