Hello @snychka. Thanks for the updates thus far.
However, without wanting to sound like a broken record, can you please raise a request internally into fixing this?
As has been mentioned above, given that OpenBadges
a) offer the ability to share badges with other services such as LinkedIn; and
b) is open-source and also backed by a large organisation with many resources at hand
the logical step should be to integrate with such a 3rd-party service as they then do the leg work to maintain interoperability with the other 3rd-parties such as LinkedIn, Facebook et al.
What is the alternative: to integrate with each service individually and face the risk of maintaining interoperability with multiple external APIs and of yet more breaking changes further down the line?
Surely for a a subscription-based organisation such as CodeSchool, your priority should be retaining all of the subscribers listed above (to which I will now add myself) who suggest that A main reason - if not THE main reason - that they chose CodeSchool above other providers is the ability to share their progress with the outside world.
Please can you and the team prioritise resolving this issue.