Back

@Alwin hmm depends how recent is recently…were boosts passed as an int from pv for this same feed before? Are you able to reproduce the issue with the latest PV version?

@mitch Don’t see any previous ones and cant reproduce in my latest podverse version in the same podcast. But I can send you the boost if you want. Received it via an alby webhook, so potentially it could also be on their end.

@Alwin hmm I just checked the feedID that we send in a post body to Alby, and the feedID is of the number type...but it is passed in as a stringified JSON object, which I believe is necessary for Alby.

I *vaguely* seem to recall seeing a string / number issue with Alby a long time ago.

Here is an example of the keysends body we send to Alby's API.

https://gist.github.com/mitchdowney/a9585178705e70f47661edad1332bbd2

I'm going to ask the Alby Telegram if this is a known issue for them.

@mitch looks all correct to me. Maybe it was some very old podverse version? Would be cool if you set the version field in the boostagram, then we would know for sure next time.

@Alwin ok cool. do you know if there’s a field for app version in the metadata?

@mitch Yes its called “app_version”. Here is an example of what castamatic does. Since podverse is not only ios like castamatic, os/platform would be a great addition for podverse maybe?

@Alwin cool, that is super easy to add to our existing setup. I just made the change, and it will be in our next release.

https://github.com/podverse/podverse-rn/commit/acf652fcaccec7b6656596fc0887ad3055bfdf40

One thing I'm not sure about is if it's acceptable to pass extra info, like a build number (which we use to distinguish Beta builds), to the end of the semver. I just asked the SatoshiStream Telegram for advice. The spec just says to use a string.

thanks so much for your help

@mitch Great Happy to help.
As far as I know there is no restriction as to what you can include in that string.