This has been a tough year for my InMyPocket #firefox #addon š£
āļø during summer, I faced issues with #pocket API: "add an item" response format suddenly changed for some users, without any warning or doc updates whatsoever. Took me quite some time and energy to understand the issue and handle the old and new formats, but we worked it out.
https://inmypocketaddon.com/changelog.html
[#]indiedev
=> More informations about this toot | More toots from pabuisson@ruby.social
š and now, here we go again: this time, it looks like the sync (fetching items from #pocket API) is affected. Again, just a handful of users suddenly receive some errors during the sync.
I've already published 5 (!!) versions since the end of October to improve error reporting around the sync and understand the problem better. I'm still not there but I'm making progress.
But this is all very annoying to deal with and takes so much time and back-and-forth... š£
=> More informations about this toot | More toots from pabuisson@ruby.social
I guess the conclusion is that I should be monitoring #pocket API much, much closely than what I'm currently doing. Response status, format, headers, performances, etc. š
And also, find ways to push more users to enable "bug reporting" (I won't and can't enable this by default, this should be opt-in) š
Also, if this becomes more common, maybe I should start supporting other backends than #pocket ?!
=> More informations about this toot | More toots from pabuisson@ruby.social
@pabuisson Bug reporting now turned on. Anything I can do to help keep this running. However if you do decide to support other backends that would be good too. The only reason I use pocket is for this addon. Same reason why Iām stuck using firefox too.
=> More informations about this toot | More toots from GavinCampbell@hometech.social This content has been proxied by September (3851b).Proxy Information
text/gemini